What you can do today
- Create a DNI session —
POST /dni/session. Hand a website visitor a tracking number tied to a campaign, so an inbound call from that visitor can be attributed back to the traffic source that produced it. - Post a buyer report —
POST /dni/campaigns/{campaign_code}/buyer-report. Record a buyer’s disposition (successorrejected) against a call so lead-buying outcomes land back in your reporting. - Execute an outbound touch —
POST /tracking/campaigns/{campaign_code}/outbound. Trigger one governed outbound call, SMS, or voicemail drop under a campaign’s consent, quiet-hours, and frequency rules.
Base URL
Every request goes to:API access is enabled per workspace, alongside your key. If every request returns a
403 with tracking_disabled, access isn’t switched on for your organization yet — contact support. See Authentication.Requests and responses
Every request and response body is JSON. SendContent-Type: application/json on any request with a body, and expect application/json back, including on error responses.
A small, growing surface
This API is intentionally small right now. It covers number tracking, buyer reporting, and cadence execution because those are the integration points firms have asked for first. If you need an endpoint you don’t see here — reading call data, managing campaigns, or something else — contact support and describe what you’re building. More of the platform is coming to this surface over time.Try it
Here’s a minimal call to create a DNI session, using only the required fields:201 with the tracking number to show the visitor: