Contact's customer service window (24 h)
GET/contacts/:id/window
Whether a free-form (non-template) message still reaches the contact, number by number. The window opens when the contact writes and lasts 24 h from their last message (72 h for a conversation that came from a Click-to-WhatsApp ad). Outside it only an approved template goes out — and that is what reopens the conversation.
With from, the answer is about one of the account's numbers and always has one entry, closed when the contact never wrote to it. Without from, every number the contact talked to is listed, from the one that closes last to the one that closes first, and open/expiresAt sum up the best of them.
With an API key limited to some numbers, only those numbers show up; a from outside them answers 403, and a contact with no conversation on them answers 404, like one that does not exist.
Request
Responses
- 200
- 401
- 402
- 403
- 404
- 422
- 429
The contact's windows.
Missing, malformed, unknown or revoked token (authentication), or a suspended
account (tenant_inactive).
No entitlement (payment_required). The body carries the reason in reason and the
way out in action: what to do (kind) and the dashboard page where it is done (url).
The resource does not belong to your account (forbidden), or the path is on the
mirror's block list (forbidden_endpoint), or your API key is limited to some numbers and
the operation covers the whole account (forbidden).
Resource does not exist (not_found).
Payload failed validation (invalid_request, detailed in issues) or was
rejected by Meta (meta_error, with the original body in meta).
Rate limit exceeded (rate_limit).
Response Headers
Seconds to wait before retrying.
Which rate limit category applied — send, media or default.
Which bucket the other headers describe — key (the API key), session (the dashboard) or account (the account ceiling).
Request ceiling for this category in the current window.
Requests left in the current window.