WhatsApp restrictions

WhatsApp restrictions

Timelock and Capping — your responsibility as the user.

The platform does not enforce Timelock or Capping before send. WhatsApp may limit the account; watch the session and pace your own sending.

Timelock

A temporary time lock — usually on new contacts you have not messaged before. If it appears, pause sending to new numbers until it lifts; existing chats can continue carefully.

Capping

A WhatsApp rate warning or cap (first/second warning or capped). Slow down on warnings; stop new-number sends when capped until it clears.

What you can do

Use delay_profile (normal / cautious / high_protection), enable typing and the send gap on the session page, and avoid blasting many new numbers at once.

Status query

For the developer: GET /instances/{instance_id}/restrictions with Authorization: Bearer tp_ins_… for that session. On the session page after login: the Check restrictions button. timelock.active means the time lock is on now, and timelock.until is its end time in UTC or null. capping.level: none means no cap, first_warning is the first warning, second_warning is the second warning, and capped blocks new chats until the cycle resets. If the status cannot be read, the response is an error, not a clear status. The query does not change sending and is not checked automatically before each message.

GET /instances/{instance_id}/restrictions
Authorization: Bearer tp_ins_…

HTTP 200
{
  "success": true,
  "instance_id": "ins_…",
  "timelock": { "active": true, "until": "2026-07-19 16:08:53 UTC" },
  "capping": { "level": "first_warning" }
}

timelock.active: false means no time lock, and until is null
timelock.until: UTC end time while active, or null
capping.level:
  none            no send cap
  first_warning   first warning
  second_warning  second warning
  capped          new chats blocked until the cycle resets
HTTP 502 { "code": "RESTRICTIONS_UNAVAILABLE" }
HTTP 503 { "code": "ENGINE_UNAVAILABLE" }