דלג לתוכן הראשי
All requests require a Bearer token in the Authorization header:
curl https://YOUR_PROJECT.texterchat.com/server/api/v2/labels \
  -H "Authorization: Bearer YOUR_API_TOKEN"

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
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.
Scope (as shown in Texter)What it unlocks
Send template messagesSend Template Message
View template messagesList All Templates
Manage WhatsApp templatesCreate / update / delete templates, localizations, submit for approval
Manage all chatsAssign / resolve chats, update chat properties and CRM data, manage labels in chats, template subscribe/unsubscribe
List all chatsSearch Chats, list unsubscribed users
View all chatsGet Messages of a Chat, Generate Public Media URL
Send session messageSend a Message to Chat, Get Chat by Chat ID
Manage labelsCreate / update / delete labels
Manage channelsResolve channel health problems
View all filesGenerate Public Media URL
View scenariosList event subscriptions
Create scenariosImport (create) event subscriptions, create/copy scenarios
Edit scenariosScenario drafts and revisions (advanced)
Delete scenariosDelete event subscriptions
Activate/inactivate scenariosPause / resume event subscriptions
Manage scenarios on behalf of userRequired together with the other scenario scopes for subscription endpoints
View scenarios runsList Scenario Runs (webhook debugging)
View quick repliesList quick replies
Manage quick repliesCreate / update / delete quick replies
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.