RouteDesk API
Send leads to RouteDesk
Lead vendors deliver leads straight into an auto transport broker's RouteDesk account with one HTTPS request. No SDK, no login, no polling.
Send your first lead
POST
/api/v1/public/leadsAll requests go to https://api.routedesk.com over HTTPS, with a JSON body.
- Get an Auth Key from the broker. Each lead source in the broker's RouteDesk account has its own key. The broker copies it from their Lead sources settings and sends it to you.
- Send the lead. Put the key in the
Authorizationheader and the lead in the body. - Check the response. A
201with aleadIdmeans the lead is in the broker's account.
Two formats, one endpoint
The endpoint accepts a lead in either of two formats and works out which one you sent.
- Standard format. Use this for a new integration. Field names are camelCase and dates are
YYYY-MM-DD. See Create a lead. - Legacy format. If you already send leads to BATS, keep the payload you send today and change only the URL and the key. See Already on BATS?
Both create exactly the same lead in RouteDesk.
What happens to a lead
The lead appears in the broker's RouteDesk account straight away, tagged with the lead source your key belongs to. The broker's own rules decide which agent gets it.
If the broker received a lead with the same phone number or email in the last 30 days, the new one is still created and is marked as a possible duplicate for the broker to review.
Next: how the Auth Key works, then how to test before going live.