How to Postback to TrackDrive Using Basic Auth

Overview

TrackDrive accepts two authentication mechanisms on call-update webhooks: an Authorization: Token
value generated by clicking on the blue guy icon at the top right corner and clicking on Developer Access Tokens then clicking on New Developer Access Token and passing that in the header of your request or HTTP Basic Auth in the Authorization request header. Basic Auth in the header is the preferred method.

This guide covers configuring a third-party platform (any postback source) to update a TrackDrive call with Basic Auth credentials.

The Endpoint

Call updates land at:

POST https://<trackdrive_subdomain>.trackdrive.com/api/v1/calls/update_call/<trackdrive_call_uuid>

Replace <trackdrive_subdomain> with the subdomain of the TrackDrive client that owns the call. Replace <trackdrive_call_uuid> with the call UUID that TrackDrive supplied to the buyer during the forward post.

If the posting platform supports token replacement in the subdomain portion of the URL, use [trackdrive_subdomain] and [trackdrive_call_uuid] so a single configured postback works across every TrackDrive traffic source. If it does not, configure one postback per subdomain.

Request Shape

• HTTP Method: POST
• Headers:
  • Content-Type: application/json
  • Authorization: Basic <base64_encoded_credentials>
• Body (minimum payload):

{
  "buyer_converted": "true",
  "revenue": "[Call:ConversionPayout]",
  "offer_converted": "true",
  "post_call_tokens": {}
}

Additional contact fields (for example first_name, last_name) go inside the post_call_tokens hash rather than at the top level of the body.

Getting the Basic Auth Token

Basic Auth credentials are generated on the TrackDrive account which will receive the Postback

On that account:

1. Open Integrations > API & Access Tokens from the sidebar.
2. Click the New button to create a new Access Token.
3. Description: a descriptive label, for example Global Basic Auth for <email>.
4. Under Data Access, set Access Type to Calls. If you're looking to have the Calls updated only.
5. Grant relevant permission to the team you create for the buyer, as in access to update buyer converted, revenue, traffic source converted etc
6. Save. The resulting token is the Basic Auth credential string used in the Authorization header.

Team Permissions on the Receiving Account

The update request will be rejected with a permission error unless the authenticating user is on a Team inside the TrackDrive traffic source account with permission to update calls.

On the traffic source account:

1. Open the buyer's edit page.
2. Scroll to Team Access and add a new team using the email address of the user whose token is being used.
3. Open Account > Teams, edit that team, turn on Enable Developer API Access under Users, and in the Calls section grant Update rights to these attributes:
   • Buyer Converted?
   • Buyer Revenue
   • Contact Fields (only if the postback body includes additional contact data)

Without these permissions, even a valid Basic Auth token returns 403 and the conversion does not record.