Skip to main content
GET
Get WhatsApp check status
Read a WhatsApp check in the authenticated workspace using the returned operation_id. This read-only lookup has no request body and does not start another check or charge additional credits. There is no endpoint-specific GET throttle.

Reading the result

  • HTTP 200 with status: "completed", whatsapp, and credits_consumed: 1 confirms a definitive result. The phone number is not returned.
  • HTTP 202 with status: "pending" or "unknown" means the outcome is not yet confirmed. Poll with bounded backoff; do not infer a yes/no result or final charge.
  • HTTP 200 with status: "unavailable" or "rejected" reports a terminal operation state without a WhatsApp result or credit amount.
  • A completed state without result fields does not confirm a definitive result.
  • HTTP 404 means the operation was not found in this workspace.

Next step

Return to WhatsApp checker. Keep the original idempotency key when reconciling the same logical check.

Authorizations

Authorization
string
header
required

Use an Airschool workspace API key. Never expose the key in client-side code.

Path Parameters

operation_id
string<uuid>
required

Operation UUID.

Pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-5][0-9a-fA-F]{3}-[89aAbB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$

Response

Completed check or terminal unavailable/rejected operation.

operation_id
string<uuid>
required

Operation UUID.

status
string
required
Allowed value: "completed"
whatsapp
enum<string>
required
Available options:
yes,
no
credits_consumed
integer
required