Authentication

Every API request is authenticated with an API token sent as a Bearer token. Tokens are scoped to your workspace and to the roles you assign them.

Create a token

Generate a token under Settings → Developer → API tokens. Give it a name, assign one or more roles, and copy the value when it's shown.

You'll only see it once

The full token value is shown a single time, right after you create it. Copy it somewhere safe — you can't retrieve it again, only revoke it and create a new one. Treat tokens like passwords: never commit them to source control or paste them into shared docs.

A token's permissions are the union of its roles, so it can only do what those roles allow. Scope tokens to the least access an integration needs — for a read-only sync, assign only the read roles. See API tokens for managing them in the app.

Make an authenticated request

Send the token in the Authorization header as Bearer <token>:

curl https://api.dynition.com/admin/graphql \
  -H "Authorization: Bearer lnqat_your_token_here" \
  -H "Content-Type: application/json" \
  -d '{"query": "{ companies { list(first: 1) { approxTotalCount } } }"}'

Token values always start with lnqat_. A request with a missing, malformed, or revoked token is rejected before it reaches your data.

What tokens can't do

For security, API tokens are deliberately limited:

  • They can't create or revoke other tokens. Minting and revoking tokens requires signing in to the app — a leaked token can't escalate by issuing more.
  • Account administration is not part of the documented API. Team members, roles, and invitations are managed in the app.

Regions are handled for you

Your workspace lives in a specific region, but you always call the same endpoint. Requests authenticated with your token are routed to the correct region automatically, so there's nothing region-specific to configure.

Create separate tokens per integration (named for where they're used). That way you can revoke one without disrupting the others, and your audit trail shows which integration did what.

PreviousAPI overviewNextPagination