Limits and logs

What the API allows, and where to see what your integration has been doing.

Rate limit

Each key can make 60 requests a minute. Over that, requests get 429 with a Retry-After header saying how many seconds to wait. If you need to send to many people at once, use Start a campaign: one request, and Wamafy paces the sending.

Monthly allowances

Your plan sets how much you can do in a month. When an allowance runs out the API says so rather than failing quietly:

  • API calls a month: further calls get 403 API_QUOTA_EXCEEDED.
  • Messages and campaigns a month, and the number of contacts: the request that would go over gets 403 CAPACITY_LIMIT_REACHED.

Current usage is under Billing, Account Usage in the dashboard.

Unusual use

A key whose last hour is far above its usual rate (at least 300 calls and ten times normal) is flagged: the workspace owner is emailed and the key shows a warning in API Access, at most once a day. See Authentication for expiry dates and address limits that make a leaked key less useful.

Request log

Every call made with your keys is recorded under Settings, Integrations, API Access, Request log: the endpoint, the status, the message id on success or the reason on failure, and the time. Phone numbers are partly hidden. It is the first place to look when an integration misbehaves.

Sent messages

Sent Messages, in the dashboard's settings, lists every message the workspace sent with its delivery status, and exports to CSV. Use it to reconcile with your own records if your webhook was down for a while.

    Limits and logs - Wamafy API