Check status

GET /v1/status — verify your API key and see the workspace and WhatsApp connection it belongs to.

Confirms an API key works and reports the workspace and WhatsApp connection behind it. The cheapest way to test an integration before sending anything.

GET https://app.onpad.in/api/v1/status

Example

curl https://app.onpad.in/api/v1/status \
  -H "Authorization: Bearer wh_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Response

{
  "ok": true,
  "workspace": {
    "id": 128,
    "name": "Sunrise Store",
    "slug": "sunrise-store",
    "country": "India",
    "timezone": "Asia/Kolkata"
  },
  "whatsapp": {
    "status": "connected",
    "phone_number": "919876543210",
    "verified_name": "Sunrise Store"
  },
  "server_time": "2026-10-04T09:21:33+05:30"
}

Fields

Field	Description
`workspace.id`	Numeric workspace id
`workspace.name`	The workspace name
`workspace.slug`	URL-safe version of the name
`workspace.country`, `workspace.timezone`	Used for scheduling and formatting
`whatsapp.status`	`connected`, `not_started`, `pending` or `error`
`whatsapp.phone_number`	The connected number, digits only
`whatsapp.verified_name`	The display name Meta approved
`server_time`	Our clock, ISO 8601 — useful for checking clock drift on your side

Status codes

Code	Meaning
`200`	The key is valid
`401`	`invalid_api_key` — bad, revoked, or the plan does not include API access

Use it for

A deploy check. Call it after deploying an integration. A 200 with whatsapp.status: "connected" means sending will work.

Diagnosing a 401. If /status also returns 401, the problem is the key or the plan — not the message you were trying to send.

Checking the connection before a batch. whatsapp.status other than connected means every send will fail. Check once rather than discovering it a thousand failures later.

This endpoint does not send anything and costs nothing.