Skip to main content
The REST API is in early access and is enabled per account on request. API keys are not yet issued from the dashboard. To request access, contact your account executive.
The DeltaLead REST API gives you programmatic read access to your organization’s leads. Use it to build custom integrations, feed your own reporting, or sync with systems not covered by native integrations — such as a proprietary DMS, an internal data warehouse, or a bespoke CRM. To push a lead into DeltaLead from your own system, use the Custom Webhook, not this API.

​
Base URL

All API requests are made over HTTPS to the following base URL:

​
Quick Example

The following request retrieves your most recent leads using curl. Replace YOUR_API_KEY with your account’s API key, which begins with dl_live_ or dl_sandbox_.

​
Response Format

All responses use JSON. The API is read-only at this stage — every available endpoint is a GET, so you never need to send a Content-Type header. Person details always travel inside the nested contact object, never at the root of the lead.

​
Available Resources

Leads

List leads and retrieve one in full. Filter by status, channel, and last-activity range.

Webhooks

Subscribe to real-time events such as new leads, status changes, and conversation milestones.

​
Rate Limits

Limits apply per API key: 5 requests per second sustained, with a burst of up to 10. If you exceed them, the API returns a 429 Too Many Requests response carrying a Retry-After header that tells you how many seconds to wait before retrying. Retry-After is the only recovery header the API emits — there are no remaining-quota headers. See the Errors reference for full details on 429 handling and the exponential backoff strategy.

​
Next Steps

  • Authentication — learn how to obtain and send your API key
  • Errors — understand status codes, error shapes, and retry strategies