Overview
The URL Endpoint tab determines where your leads are sent and how they're formatted. This is where you connect LeadExec to your client's systems using their specific technical requirements.
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 Method
Choose the HTTP method matching your client's API requirements, typically POST for lead delivery
Enter the URL
Production: Live environment endpoint
Testing: Sandbox/development endpoint
Pro tip: Always test in sandbox first
Configure Content
Select the Content-Type matching your client's specifications
Common options: application/json, application/xml
Set Timeout
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
Validation First
Try to always test with a testing URL first before switching to the final production URL, if possible
Use test leads to verify the accuracy of your format and data mapping
Timeout Optimization
Start with 30 seconds, increase only if experiencing timeouts
Monitor delivery reports for timeout occurrences
Header Management
Store sensitive tokens in secure password managers
Document all custom headers for future reference
URL Verification
Double-check URLs for typos before saving
If possible, ensure HTTPS for all production endpoints
Troubleshooting
404 Errors:
Verify URL endpoints
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 >