Overview
The Ping Post URL Endpoint tab configures where complete lead data is sent after a buyer accepts the initial ping. This is the "post" phase where full contact information and lead details are delivered to the winning buyer.
Configuration Settings
Method: Select the HTTP method type outlined in the client’s posting documentation, such as GET, POST, PUT.
Production URL: Input the receiving system’s production endpoint URL.
Testing/ Sandbox URL: Input the receiving system’s testing endpoint URL if applicable.
Content-Type: Select the content type outlined in the client’s posting documentation.
Timeout: Set the desired timeout for the delivery. This tells the system how long to wait for a response from the receiving system before timing out. The default setting is for 30 seconds.
Custom Headers: Here, you can input any custom headers required by the receiving system, such as authorization tokens and custom identifiers.
Step-by-Step Setup
Select POST Method
Choose POST method (which is the standard for lead data transmission)
Confirm with client documentation if unsure
Configure Endpoint URL
Production URL: Client's live reception endpoint
Testing URL: Client's testing environment (always try to validate here first, when available)
Set Content Type
Select the format specified in your client's documentation
Common: application/json or application/xml
Adjust Timeout Settings
30 seconds is set as the default (adequate for most APIs)
You may increase the timeout if your client's system processes requests slowly
Add Custom Headers
Include authentication tokens if applicable
Add client-specific headers as required per their specifications
Best Practices
Always Test First
If available, validate with a testing URL using sample leads
Confirm the data format matches your client's expectations
Security Check
Try to ensure all production endpoints use HTTPS
Verify authentication tokens are correctly formatted
Documentation Alignment
Double-check all settings against your client's API documentation
Maintain setup notes for future reference
Troubleshooting
Posts Not Delivering:
Verify the Production URL and server status with your client
Validate that the ping was accepted by reviewing the response received by LeadExec, and review that the response settings for the ping delivery method align with your client's specifications
Authentication Failures:
Check custom headers for valid tokens
Timeout Errors
Consider increasing the timeout setting, or contact your client about API performance on their end
Format Rejection
Verify the Content-Type matches your client's requirements
Next article: Authentication Tab >