Tarceel API
WhatsApp API gateway (linked-device / QR model). Not affiliated with or endorsed by WhatsApp/Meta. WhatsApp can suspend numbers for policy violations; you are responsible for consent/opt-in on your own contact lists.
Authentication: three credential types gate the routes below — an account token (JWT) and
a personal access token (pat_..., no expiry) are fully interchangeable everywhere, both
granting the exact same account-level access; an instance's own API key (sk_...) is
different and narrower. See the Authentication guide at /docs for
which one a given route needs and exactly where to get each — this file's own
securitySchemes descriptions below carry the short version.
See /docs for the full narrative documentation this spec is a companion to — Quickstart,
Authentication, Sending Messages, Webhooks, Connect, and Billing guides, plus this same
reference rendered as readable pages instead of raw YAML.
Authentication
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
From GET /auth/verify, ~30 days. A personal access token works identically. Full guide: top of /docs.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
From dashboard → API Tokens, or POST /account/tokens. No expiry. Works exactly like AccountToken. Full guide: top of /docs.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Shown at instance creation/rotation. Full guide: top of /docs.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |