Submit a Ping (Legacy)
The deprecated unversioned ping endpoint. Use the v1 endpoint for new integrations.
ping_id, message and bids when the ping went through matching or used a test-mode zip. Vendor sources always get message, price and ping_id, and so does any ping answered before matching (duplicate, quota reached, or rejected).Authorizations
Use your source's API key as the username and API secret as the password. Base64 encode the credentials in the format api_key:api_secret.
Headers
Public ID of the partner you're pinging on behalf of. The ping is recorded against that partner when the partner is linked to the source whose credentials you use. Optional but recommended for any partner-mediated integration.
"prt_01h7x1a3c5e7g9j1k3m5n7q9sv"
Body
Response
Ping evaluated. Check message for the outcome.
- Bids
- Price
Non-vendor sources, when the ping went through matching or used a test-mode zip.
The ping's ID. Send it as ping_id when you post the lead.
"f47ac10b-58cc-4372-a567-0e02b2c3d479"
Result of the ping. Duplicate and Rejected only appear here for test-mode zips.
Match found, No match found, Duplicate, Rejected Bids for this lead. Empty when there's no match.

