---
title: "Return the workspace's WhatsApp channel and provider-backed sender status (sms:read)."
method: GET
path: "/v1/whatsapp-sender"
---

# Return the workspace's WhatsApp channel and provider-backed sender status (sms:read).

`GET /v1/whatsapp-sender`

## Request

- Base URL: `https://www.kaicalls.com/api`
- URL: `https://www.kaicalls.com/api/v1/whatsapp-sender`
- Auth: HTTP bearer

Returns two distinct status surfaces: channel, provisioning and sender_provisioning use the existing tenant-mapped Twilio derivation, where connected requires provider status ONLINE. telnyx.available reports server configuration; telnyx.connections contains saved tenant-scoped connection views. Each connection is connected only when its persisted status is connected, following carrier verification by POST action=sync; GET does not refresh those records. Empty connections can also mean the optional table is unavailable, so do not infer readiness or lack of setup from that alone. Neither signup-link creation nor sender status proves message delivery.

## Query parameters

- `business_id` string, required

## Response `200`

WhatsApp channel status and provisioning state

## Other responses

- `403`: Missing sms:read scope, or no access to this business

---

[API](https://skmtc.dev/kaicalls/apis/kaicalls-public-api.md) · [All operations](https://skmtc.dev/kaicalls/apis/kaicalls-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/kaicalls/apis/kaicalls-public-api/revisions/e607fc6cf36e?raw)