Calls By Third-Party
This resource allows third-party users to update calls using td_secure_token and td_uuid passed in a call's SIP headers. These endpoints do not require authentication with a auth_token
Every resource below is available over HTTPS with your company's access token.
curl -H "Authorization: Basic BASE64_ENCODED_PUBLIC_KEY_AND_PRIVATE_KEY" https://subdomain.trackdrive.com/api/v1/resource echo -n 'tdpub1234:tdprv1234' | base64 curl -H "Authorization: Basic dXNlcjpwYXNz" https://subdomain.trackdrive.com/api/v1/resource This resource allows third-party users to update calls using td_secure_token and td_uuid passed in a call's SIP headers. These endpoints do not require authentication with a auth_token
The phone calls that have been made to and from your account.
A log of inbound calls that were rejected or failed to connect, with the reason why.
The Scheduled Callbacks in your account. Calls will be placed to leads when the callback matches.
Rules that automatically delete call recordings after a set retention period, scoped to an offer, schedule, buyer, or traffic source.
Submit and manage the leads in your Trackdrive account from anywhere with CORS fully whitelisted. These endpoints allow you to submit or opt-out leads using AJAX on behalf of a user visiting your website.
Manage the leads in your Trackdrive account via API.
A CSV upload job that creates or updates leads for an offer or schedule from an uploaded file.
A billable record of each action a lead goes through, such as an email, webhook, or schedule step.
Reprocesses a saved list of past leads through schedule actions again, optionally filtered by outcome or date.
API resource for accessing Lead Retarget Logs.
The set of offers in your account.
Individual rules in an offer's call flow controlling greetings, IVR menus, dialing, hold queues and exception handling.
Groups of keypress choices offered to callers during an IVR menu, with shared response-collection settings.
A single keypress option within an IVR menu, defining what happens when a caller presses that key.
Custom data fields attached to an offer's leads, defining what information is captured and how it's validated.
Predefined picklist options and display labels for a contact field that uses a dropdown or select input.
Groups the individual key press actions a caller can use during a call into one reusable set.
Defines what happens when someone on a call presses a specific key, such as ending the call, moving to the next buyer, or applying a call disposition.
Maps an incoming URL parameter name to a tracking token, so posted data lands in the right field.
Define the unique url parameters that will be tracked when using Dynamic Number Insertion For example google clickIDs can be tracked: gclid
Rules that detect if a call was answered by a machine or a human and change how the call is routed accordingly.
The impressions recorded by the advertising optimizer.
Ping for an available buyer and post a call or lead with the webhook's vanity URI, without an access token.
Endpoints that let traffic sources ping for an available buyer and post calls or leads for delivery.
Records of every ping/post request an offer's inbound webhook received, for troubleshooting lead delivery.
The people or companies who pay for your calls and leads, with hours, caps, and conversion rules that define revenue.
The Buyer Groups in your account.
The Buyer Fleets in your account.
Do-not-call lists of phone numbers that block matching contacts from being sent to associated offers, schedules, or buyers.
A CSV upload job that bulk adds or removes phone numbers from a buyer suppression list.
The traffic sources in your account.
Rules that define when and how much a traffic source is paid when one of its calls converts.
Manage reusable rate limit configurations for traffic sources.
Manage per-traffic-source rate limit entries.
The tracking phone numbers in your Trackdrive account.
A pool of tracking phone numbers assigned to a traffic source; a different number is swapped in per website visitor to attribute their calls.
A SIP-based number that routes calls to an offer without using a real telephone line.
Bulk requests to purchase new tracking numbers from a provider for an offer, pool, traffic source or schedule.
Phone number area codes or prefixes requested within a number order, with how many numbers to buy for each.
Manage spam-tag mitigation and branded caller ID for your phone numbers. Enabling a number registers it with the mobile carriers to remove "Spam Likely" labels; setting a branded name displays your business name as the caller ID on outbound calls. A one-time business compliance profile must be completed before numbers can be enabled; carriers approve the business in 1-3 business days, then approve each submitted number in about 2-3 weeks.
The Phone Providers in your Trackdrive account. One of: Trackdrive, Twilio, and Plivo.
The lead distribution and dialing configuration that controls how leads flow through your account and get called.
The End Of Schedule Triggers in your account. Leads will be moved to "End Of Schedule Actions" when any of the triggers below match.
Manage the actions of a schedule.
A named, reusable bundle of call actions, such as transferring, hanging up, or sending an SMS, that run together when triggered by an agent status change or a matched transcription.
Route incoming leads to different schedules based on predefined filters. Configure filters using attributes such as geographic location, interest, lead score, or custom fields. When a new lead is received, the API evaluates these filters to automatically assign the lead to the appropriate schedule. This feature streamlines the lead distribution process, enabling quicker response times and more targeted engagement.
Assign multiple number pools to a schedule with filters. When placing outbound calls, the system evaluates filters in sort order and uses the first matching number pool. When no filters match, the last number pool in the list is used as the fallback.
A named collection of wait rules that a schedule matches against to calculate how long to pause a lead.
A rule that sets how long to pause a lead in a schedule, based on its recent call outcomes.
A group of agents who share softphone settings and can be assigned to handle calls together.
Creates an agent account, including its contact details and call center, through a simplified setup wizard.
Agent scripts shown during calls, combining contact field inputs with instructions agents read from and fill in live.
Custom outcome codes agents assign to calls that control routing, reporting, and agent workflow behavior.
A customizable button agents can click during a call to trigger routing, tagging, or other in-call actions.
A broadcast message sent to selected agents, buyer groups, or call centers through their agent widget.
A read-only log of when an agent's status changed, used to track availability and timeouts.
Automates a text message conversation for an offer, parsing replies and sending follow-up responses.
Send a text message
Inbound SMS messages received on your tracking numbers, linked to the lead, schedule, and number that received them.
A text transcript of a call's audio, including its duration, per-speaker utterances, and any matched keywords.
Speech-to-text transcripts generated from an audio file you submit directly, independent of any call or lead.
A named group for organizing related transcription flow configurations.
Configures which calls get automatically transcribed, based on the recording type (the full call, the consumer-agent leg, or the consumer-buyer leg) and an optional filter, such as call direction or the caller's location.
A named group of keywords that Trackdrive spots within call transcriptions to flag calls automatically.
Defines keywords or phrases to detect in call transcripts, and which audio channel to scan.
The tokens in your Trackdrive account.
The token values in your Trackdrive account.
A named set of rules that pull data out of SIP call headers and save it to a lead.
A single rule that maps one SIP header to a contact field, extracting its value onto the lead.
Custom SIP headers attached to a buyer, sent on the SIP leg of a call placed to that buyer.
A named bundle of state-level calling rules (hours, frequency caps, holidays) applied company-wide or to specific offers.
A cap on how many times contacts in specified states can be called within a set time interval.
Per-state allowed calling hours for each day of the week, used to block outbound calls outside those windows.
Dates per state on which outbound calling is blocked, such as state-recognized holidays.
A named, reusable list of zip codes used to include or exclude leads by location in filters.
A CSV file of zip codes imported to populate or update a Zip Code List.
The contacts that have dialed your numbers.
API resource for uploading blacklist files.
API resource for removing all numbers from your blacklist.
Webhooks (also known as Postbacks) fire when a triggers occurs, such as a buyer being dialed or a call ending.
Configure the URLs that fire when an Outgoing Webhook is triggered.
A custom key and value pair appended to an outgoing webhook request, often filled with token data.
API resource for viewing Webhook Request Logs.
Subscribe to events and then wait for Trackdrive to deliver the payload when things happen. The gist is: you POST a subscription to /api/v1/subscription/ requesting to receive hooks at some target URL. Every time the event happens, Trackdrive pings you at the target URL with the payload.
A connection to a third-party service or tool that your account uses to send or receive data.
An automated action that syncs lead or call data to Zoho CRM, such as creating or updating a record.
Encrypted key-value secrets stored per account for securely referencing sensitive values like API keys in configurations.
An ordered or shuffled group of audio files played back together, such as hold music or IVR prompts.
An uploaded audio clip used in call flows and playlists, such as a greeting or hold message.
A one-time or recurring export of your account data that runs asynchronously and produces a downloadable file.
A lead & call log of changes to records in your Trackdrive account.
Fetch various collections used in the Trackdrive Interface.
An audit log of system-related changes in your Trackdrive account.
API resource for viewing the Trackdrive Companies you can access.
Defines a team's permission policy, controlling which records, actions, and leads its members can access.
API resource for viewing billing information.