Outgoing Webhook Authentication

No Dedicated Auth Field

Outgoing webhooks do not have a separate "Use Basic Auth"
checkbox or username/password fields. Authentication is
delivered through the same header and body fields that
carry the rest of the request.

Basic Auth via Headers

For HTTP Basic Auth, base64-encode username:password
and place the result in the Headers field: or if the Auth is
already base64-encoded, add that in directly as in the
below example

Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=

The receiver must accept Basic Auth on the configured
endpoint.

Bearer Tokens

For Bearer or other token schemes, use the same header:

Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6...

TrackDrive to TrackDrive Authentication

When posting to another TrackDrive instance, head over
to the Buyers section in Setup System use the template
which says TD-Data Buyer or if it's a Ping/Post TrackDrive
Buyer use the template which says TrackDrive - PING/POST
Sample Buyer. Once the buyer is created, open the buyer
and click on Manage next to Extra Tokens and paste in the
values from your TrackDrive Buyer's Posting instructions

Why the Free-Form Approach

TrackDrive's outgoing webhook engine targets arbitrary
external systems. A structured auth model would constrain
what is reachable. The trade-off is that operators must
know which auth scheme each receiver expects and construct
the headers themselves.