Skip to main content
Authentication

Get an access token

Exchange your Personal API Key for a 24-hour access token. Create a key on the API page in your Datablist account, then send it in the JSON apiKey field. This endpoint needs no Bearer token, path parameters, or query parameters. The body must fit within 4 KiB.

Use the returned access_token as Authorization: Bearer ACCESS_TOKEN on authenticated calls. After 24 hours, exchange your key again. Deleting a key prevents new exchanges but does not revoke tokens already issued. Keep both credentials out of URLs and logs.

In the documentation, Try it → Connect performs this exchange for you. Credentials stay in memory and clear on refresh. See authentication.

post/v1/account/token

Body

Your Personal API Key, sent as JSON.

application/json · required

apiKeystringrequired

Personal API Key created in your Datablist account. Do not send an access token here.

minLength: 1

Response

Access token and account information.

200 · application/json

access_tokenstringrequired

JWT access token. Send it in the Authorization header using the Bearer format.

token_typestringrequired

Authentication scheme to use with the access token.

Allowed values: "Bearer"
expires_inintegerrequired

Token lifetime in seconds (86400 seconds, or 24 hours).

expires_atintegerrequired

Expiration time as a Unix timestamp in seconds.

account_idstringrequired

Datablist account identified by the Personal API Key.

user_idstringrequired

User who created the Personal API Key.

planstringrequired

Account plan when the token was issued.

scopestring[]required

Account permissions granted to the token. Personal API Keys issue admin scope.