Authentication

Learn how you can authenticate API requests that you make to Datman.


Each API request that you make to Datman must be authenticated. To authenticate your requests, you need API credentials: secret values that Datman issues to you. They act as the identity of your integration, and make sure that every request is authorised and linked to the correct account.

Depending on the endpoint, you use one of the following authentication types:

The authentication type for each endpoint is shown on its page in the API Explorer. Each operation's page also shows its sandbox and production URLs.

Keep your credentials on your server. Never put them in a browser, a mobile app, or page source.

API key authentication

Authenticate your request by sending your API key in an api_key HTTP request header. Most endpoints use this type, for example List transactions in a date range and Create, update or patch a merchant.

API key in the request header

api_key: YOUR_API_KEY

API key in the X-API-Key header

A few endpoints read the same API key from an X-API-Key HTTP request header instead of api_key. Send the header name as exactly X-API-Key or x-api-key. The endpoints that use this header are:

  • Sync a legal entity
  • Get a merchant's balance

API key in the X-API-Key header

X-API-Key: YOUR_API_KEY

API token authentication

Authenticate your request by sending your API token in an api_token HTTP request header. The following endpoints use this type:

API token in the request header

api_token: YOUR_API_TOKEN

Document upload API key authentication

Authenticate a request to upload an onboarding document by sending your document upload API key in an api_key HTTP request header. This is a different key from your API key.

Document upload API key in the request header

api_key: YOUR_DOCUMENT_UPLOAD_API_KEY

Next steps

On this page

Need help?

Questions about your integration, credentials or going live?

Contact supportRequest a sandbox