Skip to main content

Webhook URL Endpoint Tab

Configure where and how leads are delivered to your integration

Written by Gabriel Buck

​

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

  1. Select Method

    • Choose the HTTP method matching your client's API requirements, typically POST for lead delivery

  2. Enter the URL

    • Production: Live environment endpoint

    • Testing: Sandbox/development endpoint

      • Pro tip: Always test in sandbox first

  3. Configure Content

    • Select the Content-Type matching your client's specifications

    • Common options: application/json, application/xml

  4. 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

  5. Add Custom Headers

    • Include authentication tokens if applicable

    • Add client-specific headers as required per their specifications

​

Best Practices

  1. 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

  2. Timeout Optimization

    • Start with 30 seconds, increase only if experiencing timeouts

    • Monitor delivery reports for timeout occurrences

  3. Header Management

    • Store sensitive tokens in secure password managers

    • Document all custom headers for future reference

  4. URL Verification

    • Double-check URLs for typos before saving

    • If possible, ensure HTTPS for all production endpoints

​

Troubleshooting

  1. 404 Errors:

    • Verify URL endpoints

  2. Authentication Failures

    • Check custom headers for valid tokens

  3. Timeout Errors

    • Consider increasing the timeout setting, or contact your client about API performance on their end

  4. Format Rejection

    • Verify the Content-Type matches your client's requirements

​

Next article: Authentication Tab >

Did this answer your question?