Secure Calls API and SIP Headers

Why the Secure Calls API Exists

Some external systems, particularly third-party voice bots
and IVR providers, need to update an in-progress call
without holding a long-lived access token. TrackDrive
emits two SIP headers on the outbound INVITE for these
integrations:

• td_uuid: the Trackdrive Call UUID for the leg.
• td_secure_token: the company's secure API token, included so the external system can call back without needing a separate auth header.

Both headers are set automatically when the call is
initiated.

Endpoint

The third party calls
/api/v1/secure/:secure_token/calls/:uuid where
:secure_token is the company's secure API token and
:uuid is the TrackDrive Call UUID. The secure token is
passed as a URL path segment, not as a header or query
parameter. No separate company access token header is
required because the secure token in the URL path
authenticates the request.

Available HTTP methods:

• PUT /api/v1/secure/:secure_token/calls/:uuid - update the call (disposition, conversion, metadata).
• DELETE /api/v1/secure/:secure_token/calls/:uuid - hang up the call.
• GET /api/v1/secure/:secure_token/calls/:uuid/data - read call data.

What the Secure Endpoint Can Do

The secure endpoint can update call disposition, set
conversion fields, attach metadata, and trigger key
presses. It cannot create new calls, modify other calls,
or read company-wide data.