The Datenly API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses.

Each response contains status and description fields, "true" in status and "succeeded" in description means your request is processed successfully, otherwise, the description field describes the error



Each product has its own keys such as:

There are for keys three each product, public key, private key, and secret key .

Public key

You can safely use this key clearly in your code.

Private key

Key to confirm that you are authorized to use your application. It should be kept in a private and secure place

Secret key

Secret key allows you to decrypt sensitive data, such as user data, it's important to protect it well.

You can find your API keys on Api - Flows


To use the API, you must have, private key


To use the API, you must have, public key, private key, and secret key

Generate a token

Datenly Api uses OAuth 2.0 protocol to authorize calls. OAuth is an open standard that many companies use to provide secure access to protected resources.

Authentication, which uses a Bearer Token, is also known as application-only authentication. A Bearer Token is a byte array of unspecified format that you generate using a script like a curl command. More information about this feature can be found on OAuth's official documentation.

Request for all endpoints except commerzdata
curl -X GET "" \
-H "key: <Private_key>"
Request for commerzData
Secret key is only available one time on your portal

Datenly expects for the keys and app ID to be included in a header that looks like the following:

curl -X GET "" \
-H "app: <App_ID>"
-H "key: <Private_key>"
-H "secret: <Secret_key>"


Using Token

All Datenly APIS endpoints need to be identified by token

Datenly expects for the token to be included in Api requests in a header that looks like the following:

curl -X GET "<endpoint>" \
-H "Authorization: <token>"