Ping %2B Post API (CS%2C MC%2C MP)
Note: This tab is available in Custom Source (CS), Media Channel (MC), and Marketing Partner (MP) source types.
The Ping + Post API works similarly to the standard Form API but introduces a two-step process that offers greater control and efficiency over lead distribution.
How Ping + Post API Works
-
Ping Request
- The traffic source first sends a Ping API call with minimal lead information.
- Upon receiving the ping, Pingtree initiates the distribution process and only fires ping calls to the buyers’ or endpoints’ ping APIs.
- If any buyer expresses interest in purchasing the lead, Pingtree responds back to the source indicating which buyer is ready to buy.
-
Post Request
- After being informed that a buyer is interested, the traffic source can then decide whether or not to send a Post API request containing the full lead data.
- If the traffic source proceeds, the lead is fully posted and completed through the system.
Key Differences Compared to Form API
- In a Form API setup, the source directly posts the full lead data without prior verification of buyer interest or pricing.
- Ping + Post API enables the source to verify buyer availability and price before deciding to send the complete lead information.
This process ensures that only leads with confirmed buyer interest are fully submitted, optimizing efficiency for both sources and buyers.
API URL and Authorization Token
The Ping + Post API view in the UI is very similar to the standard Form API tab:
- Users can easily copy the API URL and generate an Authorization Token.
- These credentials are then shared with the traffic source for integration with their tracking and posting setup.