Skip to main content
All DABAR API requests are authenticated with a token sent in the api-token HTTP header. Tokens are tied to a user and inherit that user’s permissions and sources.

​
Base URL

https://api.dabarai.com/v1
​
api-token
string
required
The API token associated with your DABAR user account.

​
Example

curl https://api.dabarai.com/v1/politics \
  -H "api-token: YOUR_TOKEN"

​
Failure responses

StatusScenario
401Header api-token is missing
401Token does not match any user
403Token lacks access to the resource

​
Keeping tokens safe

  • Store tokens as environment variables or in a secrets manager — never in source control.
  • Rotate tokens periodically and immediately if exposure is suspected.
  • Use separate tokens per integration so you can revoke one without affecting others.