Browse the docsIntroduction

Developers

The Chattil API

Send WhatsApp messages, read what happened to them, and receive events — from your own software. REST over HTTPS, JSON in and out, one key per business, and 16 endpoints.

An API key is another door into the same building, not a way around the walls.Every quota, plan limit, opt-out and warm-up cap that applies in the dashboard applies identically here. A number that replied STOP is refused through the API too.

Your first request

  1. Create a key. In the dashboard, go to Developers and create one. It is shown once — store it somewhere your code can read and a person cannot. Only the account owner can create keys.
  2. Confirm it works. GET /v1/me is the cheapest call and tells you the account, the plan, the quota left today, and whether a WhatsApp number is actually connected.
  3. Send something. POST /v1/messages.
curl https://chattil.com/v1/me \
  -H "X-API-Key: tt_your_key_here"

Authentication

Every request carries your key in the X-API-Key header. There is no OAuth flow and no token exchange: a key is scoped to exactly one account and does not expire until you revoke it.

Keys begin tt_ (keys issued before 2026-09 begin dk_ and keep working). Only a hash is stored, so a lost key cannot be recovered — revoke it and issue another. The dashboard shows the first few characters so you can tell two keys apart in a list.

A key is unrestricted access to the whole account, including sending. Keep it server-side. Anything in a browser, a mobile app or a public repository is compromised the moment it ships.

Errors

One shape for every error, so you can write one handler. The HTTP status carries the category; code is the stable, machine-readable reason, and is the only part you should branch on.

{
  "error": {
    "code": "quota_exceeded",
    "message": "Daily message limit reached for the Starter plan."
  }
}
StatusMeansWhat to do
400The request is malformed or the number is invalidFix and retry. Retrying unchanged will not help.
401Missing, revoked or unknown keyCheck the header name and the key.
402Quota exhausted, or the plan does not include thisWait for the daily reset, or upgrade.
403Recipient is suppressed, or the feature is not on your planDo not retry. An opt-out is permanent.
404No such record on this accountCheck the id belongs to you.
409No WhatsApp number is connectedLink a number in the dashboard, then retry.
422A field failed validationThe message names the field.
429Too many requestsBack off and retry.

Pagination

List endpoints take limit and offset. limit defaults to 50 and caps at 200. Responses carry the total, so you can page without guessing where the end is.

Versioning

The prefix is /v1, and the promise is narrow enough to be worth something: within a version, fields are added — never removed, never repurposed. Write a client that ignores fields it does not recognise and it will keep working. A breaking change becomes /v2, and both run side by side.

Next