Skip to main content
ll requests require a Bearer token in the Authorization header:

Creating a token

In your Texter environment:
  1. Click the gear iconDevelopersAPI Tokens
  2. Click the plus icon, give the token a name, choose the relevant scopes, and save
  3. Click the link icon to copy the token
Gear icon, Developers, API Tokens Plus icon, token name, scopes, save changes Link icon to copy the token
The token is shown once - store it securely. Anyone holding the token can act on your inbox within its scopes.

Scopes

When creating a token you assign it scopes, which define which parts of your inbox the token can access. Every endpoint in this reference lists its required scopes at the top of its description - a token must include all scopes an endpoint lists.
A few read-only endpoints - List All Labels, Get Label Data and List Channel Health Problems - work with any valid token, regardless of scopes.

One token or many?

Both approaches work:
  • One token per integration with all the scopes it needs (simplest).
  • One token per area (templates, chats, events, and so on) following the suggested scope bundle listed on each group’s overview - slightly safer because each token can do less.

What’s next

All status values, type enums and the which-ID-goes-where cheat sheet live on Enums & Common Fields.