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.
Body
Your Personal API Key, sent as JSON.
application/json · required
apiKeystringrequiredPersonal API Key created in your Datablist account. Do not send an access token here.
1Response
Access token and account information.
200 · application/json
access_tokenstringrequiredJWT access token. Send it in the Authorization header using the Bearer format.
token_typestringrequiredAuthentication scheme to use with the access token.
"Bearer"expires_inintegerrequiredToken lifetime in seconds (86400 seconds, or 24 hours).
expires_atintegerrequiredExpiration time as a Unix timestamp in seconds.
account_idstringrequiredDatablist account identified by the Personal API Key.
user_idstringrequiredUser who created the Personal API Key.
planstringrequiredAccount plan when the token was issued.
scopestring[]requiredAccount permissions granted to the token. Personal API Keys issue admin scope.