---
title: "Get sender"
method: GET
path: "/v1/senders/{senderId}"
---

# Get sender

`GET /v1/senders/{senderId}`

## Path parameters

- `senderId` string, required

## Response `200`

Sender details.

- Sender
  - `id` string, required
  - `name` string, required
  - `phoneNumber` string, required — Phone number in E.164 format.
  - `channels` string[] — Channels this sender can actually send on right now, computed from its configuration. Empty means the sender cannot send or receive anything yet: a phoneNumber alone does not enable SMS or voice. Check this rather than inferring capability from phoneNumber or emailAddress.
  - `isDefault` boolean — Whether this sender is the project's default.
  - `webhook` SenderWebhook — Webhook configuration for the sender.
    - `url` string, uri, required — HTTPS URL that will receive webhook events.
    - `events` WebhookEvent[], required — List of events the webhook is subscribed to.
    - `secret` string — Webhook secret for signature verification. Only returned on create or regenerate.
    - `active` boolean, required — Whether the webhook is active.
    - `signatureVersion` 'v1' | 'v1+v2' | 'v2', required — Which `X-Zavu-Signature` scheme this receiver is sent. - `v1`: `v1=HMAC_SHA256(secret, body)`. The scheme used before this was configurable. Existing webhooks stay on it until you move them. - `v2`: `v2=HMAC_SHA256(secret, "{t}.{body}")`. The current scheme, and the default for new senders. It signs the timestamp together with the body. - `v1+v2`: both signatures, sharing one `t`. The migration setting: a receiver reading either one works, so you can deploy and confirm your new verifier before switching over. Moving from `v1` straight to `v2` returns `400`. Set `v1+v2` first. See https://docs.zavu.dev/guides/receiving-messages/signature-migration
  - `whatsapp` object — WhatsApp Business Account information. Only present if a WABA is connected.
    - `phoneNumberId` string — WhatsApp phone number ID from Meta.
    - `displayPhoneNumber` string — Display phone number.
    - `paymentStatus` object — Payment configuration status from Meta.
      - `setupStatus` string — Payment setup status (COMPLETE, NOT_STARTED, etc.).
      - `methodStatus` string — Payment method status (VALID, NONE, etc.).
      - `canSendTemplates` boolean — Whether template messages can be sent. Requires setupStatus=COMPLETE and methodStatus=VALID.
  - `emailAddress` string — From-address for the email channel, if configured.
  - `emailReceivingEnabled` boolean — Whether inbound email receiving is enabled for this sender.
  - `emailCatchAllEnabled` boolean — Whether catch-all receiving is enabled. When true (and emailReceivingEnabled is true), this sender receives email addressed to any local part at its domain, not just its own address. The original recipient is delivered in the message.inbound webhook's data.to.
  - `createdAt` string, date-time
  - `updatedAt` string, date-time

## Other responses

- `401` — Unauthorized.
- `404` — Sender not found.

---

[API](https://skmtc.net/zavudev/apis/zavu-unified-messaging-layer-api.md) · [All operations](https://skmtc.net/zavudev/apis/zavu-unified-messaging-layer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zavudev/zavu-unified-messaging-layer-api/revisions/eb3dc75cc05b/schema)