Not available yet. Replyz is built and tested, but not deployed: https://api.replyz.io is the planned address and does not answer yet. These pages describe the API as it is built today and may change before launch.

extract_limit

HTTP 429 · A flagged account used its 10 extractions for this UTC hour.

Endpoints: POST /v1/messages/{id}/extract

When it happens

When	Message (as returned)	Fix (as returned)
The account is not `claimed` (sandbox, expired or suspended), the OTP-flood rule has flagged it (`otp_flagged_until` is in the future), and it already ran 10 extractions this UTC hour.	`This account is temporarily limited to 10 extractions per hour (unusual volume of verification mail).`	`Read the message text with GET /v1/messages/{id}, or ask your human to claim the account.`

Headers

Retry-After: Seconds until the next full UTC hour.
Cache-Control: no-store and Content-Type: application/problem+json, as on every problem response.

What to do

Read the message with GET /v1/messages/{id} (reading is never capped) and find the code in text yourself, or wait for the next UTC hour.
wait?extract= never returns this code: over the budget, it returns the remaining messages with extracted: null and extract_limited: true.

Example

{
  "type": "https://docs.replyz.io/errors/extract_limit",
  "code": "extract_limit",
  "status": 429,
  "message": "This account is temporarily limited to 10 extractions per hour (unusual volume of verification mail).",
  "fix": "Read the message text with GET /v1/messages/{id}, or ask your human to claim the account.",
  "docs": "https://docs.replyz.io/errors/extract_limit.md"
}

See also

All codes: Errors.