> ## Documentation Index > Fetch the complete documentation index at: https://docs.tawked.com/llms.txt > Use this file to discover all available pages before exploring further. # List verifications > Every code your key sent, newest first, across all your applications. Each row is the shape of `GET /v1/verify/{id}` plus `application_id`, your `external_id`, the key `mode` it was sent under, the `lang` and the `price_halalas` it was charged at. Keyset paging with no totals: keep `next_cursor` and pass it back as `cursor`; `has_more` says whether another page is waiting. An archived application keeps its rows. Guide: [Sending codes for an application](https://docs.tawked.com/partners/sending.md) ## OpenAPI ````yaml https://tawked.com/openapi.json get /v1/partner/verifications openapi: 3.1.0 info: title: Tawked API version: 2026-09 summary: >- Tawked Verify: OTP verification for Saudi mobile numbers over SMS, in two calls. Tawked Notifications: WhatsApp template messages from the application's own number. Tawked Email: transactional e-mail from the application's own verified domain. Tawked Chat: the conversation menus a connected app adds beside the conversations of its connection's application, and the auto-attendant it sets up there. The Partner API for platforms that run Tawked Verify for their merchants. description: >- The public API of Tawked, a Saudi messaging platform: Tawked Verify (one-time codes), Tawked Notifications (WhatsApp templates from the application's own number), Tawked Email (transactional e-mail from the application's own domain) and the Partner API. Tawked Verify is an OTP verification API for Saudi numbers. One call sends a one-time code by SMS to a Saudi mobile number, and a second call checks it. SAR 0.09 per SMS code sent, prepaid; a send the network refuses is refunded. Authenticate with a Bearer API key from the dashboard (tk_live_ for production, tk_test_ for the sandbox, tk_partner_ for partners, tk_partner_test_ for the partner sandbox). Partners (tk_partner_) provision a Verify application per merchant under /v1/partner/applications and name it as application on every Verify call. Both /v1/... and /api/v1/... answer identically. Rate limit: 120 requests per minute per key. termsOfService: https://tawked.com/en/terms license: name: Proprietary (Tawked terms of service) url: https://tawked.com/en/terms contact: name: Tawked support email: support@tawked.com url: https://tawked.com/en/contact servers: - url: https://tawked.com description: Production (the sandbox is a tk_test_ key on the same host) - url: https://tawked.com/api description: The same API under /api/v1/..., kept for older integrations security: - bearerKey: [] - headerKey: [] tags: - name: Verify x-group: Verify description: Send and check one-time codes. - name: WhatsApp x-group: Notifications description: >- Tawked Notifications: send approved WhatsApp templates through the number connected to an application. An application in review or approved connects its own number from the dashboard. - name: Email x-group: Email description: >- Tawked Email: send transactional e-mail from an address on a verified domain of the application, to up to 50 recipients a message, in batches or scheduled, and read and list what was sent. Live keys only. - name: Chat x-group: Chat description: >- Tawked Chat: the conversation menus a connected app adds beside the conversations of its connection's application, and reads, changes and removes, with `chat:menus`; and the application's auto-attendant, which a connected app sets up, publishes and switches on or off, with `chat:attendant`. A connected app's key only; a business adds its own menus and builds its auto-attendant in the console. - name: Partner x-group: Partner API description: >- For platforms that run Tawked Verify for their merchants: provision a Verify application per merchant, keep its brand and verify settings current, switch it off and on, and read usage and the code log. Partner keys (tk_partner_) only; every Verify operation then takes `application` with the partner's own id for the application. - name: Webhooks x-group: Webhooks description: >- The events Tawked sends to your endpoint: an application's verification outcomes and message statuses, and a partner account's lifecycle, balance and opt-in verification events. Every delivery is signed the same way and retried the same way. externalDocs: description: Developer docs, with code samples url: https://docs.tawked.com paths: /v1/partner/verifications: get: tags: - Partner summary: List verifications description: >- Every code your key sent, newest first, across all your applications. Each row is the shape of `GET /v1/verify/{id}` plus `application_id`, your `external_id`, the key `mode` it was sent under, the `lang` and the `price_halalas` it was charged at. Keyset paging with no totals: keep `next_cursor` and pass it back as `cursor`; `has_more` says whether another page is waiting. An archived application keeps its rows. operationId: partner_verifications parameters: - name: application in: query required: false description: >- Your `external_id`: only that application. An id that is not yours answers `404 not_found`. schema: type: string - name: status in: query required: false description: >- One of `pending`, `verified`, `failed`, `expired`, `canceled`; `pending` and `expired` are read by the clock, as `GET /v1/verify/{id}` reads them. schema: type: string - name: mode in: query required: false description: 'The mode of the key that sent the code: `partner` for your key.' schema: type: string - name: reference in: query required: false description: Your own `reference`, exactly. schema: type: string - name: from in: query required: false description: Only rows created at or after this ISO 8601 date or datetime. schema: type: string - name: to in: query required: false description: Only rows created at or before this ISO 8601 date or datetime. schema: type: string - name: cursor in: query required: false description: 'The `next_cursor` of the previous page: the rows after it.' schema: type: string - name: limit in: query required: false description: Page size, 1 to 100; 50 when omitted. schema: type: integer responses: '200': description: A page of verifications content: application/json: schema: type: object properties: data: type: array items: type: object properties: id: type: string application_id: type: string external_id: type: string status: type: string channel: type: string to: type: string reference: type: string attempts_remaining: type: integer resends_remaining: type: integer expires_at: type: string format: date-time verified_at: type: string format: date-time created_at: type: string format: date-time mode: type: string lang: type: string price_halalas: type: integer next_cursor: type: string has_more: type: boolean examples: a_page_of_verifications: summary: A page of verifications value: data: - id: b7e5c2b0-9c1a-4e2f-8f2a-3a6b0e9d1c44 application_id: c2a10f3e-8b7a-4d2e-9c1a-1a2b3c4d5e6f external_id: store_88 status: verified channel: sms to: '+966551234567' reference: order-42 attempts_remaining: 0 resends_remaining: 0 expires_at: '2026-09-26T12:34:56.789Z' verified_at: '2026-09-26T12:31:02.145Z' created_at: '2026-09-26T12:29:56.789Z' mode: partner lang: ar price_halalas: 9 next_cursor: >- eyJ0IjoiMjAyNi0wOS0yNiAxMjoyOTo1Ni4wMDAwMDAiLCJpZCI6ImI3ZTVjMmIwLTljMWEtNGUyZi04ZjJhLTNhNmIwZTlkMWM0NCJ9 has_more: false '400': description: >- Not a status / `invalid_request`: A field is missing or refused. `fields` names them: bare names on the verify-settings endpoint (`verify` alone for an empty or unrecognised patch), `verify.` followed by the field name for a setting refused on provision or a brand update, `metadata.` followed by the key for a refused tag (`metadata` alone for a wrong shape, on a write or on the list filter), `logo` for a missing, oversized or non-image file, `events` for an unknown event name, `url` or `secret` on the webhook (console-only, with `message`), `cursor`, `since`, `event` or `status` on the feeds; on usage, `message` says that `from` and `to` must be ISO dates; a malformed `Idempotency-Key` header is refused with `message` too. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - invalid_request examples: not_a_status: summary: Not a status value: error: invalid_request fields: - status '401': description: >- `unauthorized`: Missing, unknown or revoked key; a key of another mode (`tk_live_` and `tk_test_` keys cannot call the partner API); or a partner account Tawked suspended.; `key_expired`: The key's `expires_at` has passed. Checked right after the key is recognised. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - unauthorized - key_expired '403': description: '`ip_not_allowed`: The caller''s IP is outside the key''s allowlist.' content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - ip_not_allowed '404': description: >- Not your application / `not_found`: No application of yours has this `external_id`. Whether it exists under another partner is never revealed. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - not_found examples: not_your_application: summary: Not your application value: error: not_found '429': description: >- `too_many_requests`: Per-key rate limit exceeded (120 requests per minute, fixed 60-second window). Checked before authentication. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - too_many_requests '500': description: >- `internal_error`: An unhandled server error. Quote the X-Request-Id header if you report it. content: application/json: schema: allOf: - $ref: '#/components/schemas/Error' - properties: error: enum: - internal_error x-codeSamples: - lang: bash label: cURL source: >- curl "https://tawked.com/v1/partner/verifications?application=store_88&status=verified&limit=50" \ -H "Authorization: Bearer tk_partner_xxxxxxxxxxxxxxxxxxxx" - lang: javascript label: Node.js source: >- const res = await fetch("https://tawked.com/v1/partner/verifications?application=store_88&status=verified&limit=50", { headers: { Authorization: "Bearer tk_partner_xxxxxxxxxxxxxxxxxxxx", }, }); const data = await res.json(); - lang: python label: Python source: |- import requests res = requests.get( "https://tawked.com/v1/partner/verifications?application=store_88&status=verified&limit=50", headers={"Authorization": "Bearer tk_partner_xxxxxxxxxxxxxxxxxxxx"}, ) data = res.json() components: schemas: Error: type: object required: - error properties: error: type: string description: A stable machine-readable code; the docs list every one. additionalProperties: true securitySchemes: bearerKey: type: http scheme: bearer description: >- Authorization: Bearer . An application key (tk_live_, tk_test_) has full access, which covers every product and any product added later, or custom access, chosen when the key is created: one or more of the scopes `verify:check`, `verify:send` (includes `verify:check`), `notifications:read`, `notifications:send` (includes `notifications:read`), `email:read`, `email:send` (includes `email:read`), `email:manage` (includes `email:send`), `webhooks:manage`, `email:inbound`, `notifications:templates` (includes `notifications:read`), `chat:menus`, `chat:attendant`. No key made on the API keys page holds `notifications:templates`, full access included: the three template writes answer such a key 403 `insufficient_scope`. A connected app's key holds it. Nor `chat:menus`: the five conversation menu operations answer such a key 403 `insufficient_scope`, and a connected app's key holds it once the client approved it. Nor `chat:attendant`: the five auto-attendant operations answer such a key 403 `insufficient_scope` too, and a connected app's key holds it once the client approved it. `email:manage` and `webhooks:manage` are held only by a key someone chose them for: a full-access key, old or new, never holds them. `email:inbound`, which reads, deletes and forwards received e-mail, is opt-in on every key, full access included: a key holds it only when it was turned on when the key was created. A call outside the key's access answers 403 `insufficient_scope` and names the scope it needs in the `WWW-Authenticate` response header. A partner key (tk_partner_) always has full access. Whatever its access, a key is a server-side secret. headerKey: type: apiKey in: header name: x-api-key description: >- The same API key, with the same access, as a header, for clients that cannot set Authorization. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.