> For the complete documentation index, see [llms.txt](https://docs.triton.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.triton.one/account-and-billing/account-management-api/auth-headers.md). # Auth & headers Authenticate account management API requests by passing your token in the Authorization header. ## **Auth** Pass your token in through the Authorization header to make scoped, authenticated requests against the account management API. You can use the `GET /api/v1/accounts` endpoint to test your token. If you get a 200 status code response, your token is being passed correctly. This token is only used for the account management API (`customers.triton.one/api`). You'll create separate tokens for consuming the RPC API. Account management API tokens start with `trt_`. Send the token on its own or as `Bearer `. A missing or invalid token returns `401`. Tokens are read-only: any request other than `GET` or `HEAD` returns `403`. Only Triton administrators can create tokens. Examples in this account management API guide are demonstrated using curl, but you should use an HTTP library of your choice. ``` $ curl -H "Authorization: secret" -H "Content-Type: application/json" -H "Accept:application/json" https://customers.triton.one/api/v1/accounts ``` ## **Headers** All endpoints accept and return JSON, and you should pass both an Accept and Content-Type header of `application/json` *** :life-ring: Contact support by clicking the chat icon in your [customer dashboard](https://customers.triton.one)\ :briefcase: Sales questions? [Contact us](https://triton.one/contact)\ :sparkles: AI agent? Read [llms.txt](https://docs.triton.one/llms.txt)\ :rss: Follow updates: [Blog](https://blog.triton.one) · [X](https://x.com/triton_one) · [YouTube](https://www.youtube.com/@triton_one_ltd) · [Telegram](https://t.me/tritonone) · [GitHub](https://github.com/rpcpool)