Update sender
Authorization
AuthorizationheaderrequiredBearer YOUR_API_KEY. Create a key in the dashboard.
Path parameters
senderIdstringrequired
Body
application/json
namestringenableVoicebooleanTurn the voice channel on or off. The sender must already have a phone number provisioned for calls; enabling it otherwise returns 400 instead of storing a flag that changes nothing. Confirm with the
channelsarray on the response.enableSmsOnewaybooleanTurn the one-way SMS channel on or off. Enabling needs no number or credential and takes effect immediately (US and Canadian destinations still need an approved 10DLC campaign); disabling removes the channel from the sender. Confirm with the
channelsarray on the response.setAsDefaultbooleanwebhookUrlstring<uri>HTTPS URL for webhook events. Set to null to remove webhook.
webhookEventsstring[]Events to subscribe to.
One ofmessage.queuedmessage.sentmessage.deliveredmessage.readmessage.statusmessage.failedmessage.inboundmessage.unsupportedbroadcast.status_changedconversation.newcontact.identity_linkedtemplate.status_changedinvitation.status_changedcall.initiatedcall.answeredcall.completedcall.faileddomain.verifieddomain.failedwebhookActivebooleanWhether the webhook is active.
emailReceivingEnabledbooleanEnable or disable inbound email receiving for this sender. Enabling requires a verified inbound MX record on the domain; the request is ignored otherwise, and
emailReceivingEnabledcomes backfalseon the response. Disabling always applies.emailCatchAllEnabledbooleanEnable or disable domain catch-all. When enabled (with emailReceivingEnabled true), this sender receives email for any address at its domain. Ignored (treated as false) if receiving is not enabled.
emailAddressstring<email>Attach or change the sender's email from-address (e.g. noreply@yourdomain.com). The domain must be a verified email domain in your project.
emailDomainIdstringID of the verified email domain to attach. Optional — resolved from
emailAddress's domain when omitted.emailFromNamestringDisplay name shown in the recipient's inbox for the email channel.
Limitsmax length 100webhookSignatureVersionstringMove this webhook between signature schemes.
v1->v2directly returns400; go throughv1+v2first. See https://www.zavu.dev/docs/guides/receiving-messages/signature-migrationOne ofv1v1+v2v2
Responses
200Sender updated.
idstringrequirednamestringrequiredphoneNumberstringPhone number in E.164 format. Absent on a sender that has none: an email-only sender, or one created with only
enableSmsOneway.channelsstring[]Channels this sender can actually send on right now: configured AND activated. Empty means the sender cannot send or receive anything yet: a phoneNumber alone does not enable SMS or voice, and a connected account that is not activated is left out, because every send on it is refused. Check this rather than inferring capability from phoneNumber or emailAddress, and turn a connected channel on with
POST /v1/senders/{senderId}/channels/{channel}/activate.isDefaultbooleanWhether this sender is the project's default.
DefaultfalsewebhookobjectWebhook configuration for the sender.
5 properties
urlstring<uri>requiredHTTPS URL that will receive webhook events.
eventsstring[]requiredList of events the webhook is subscribed to.
One ofmessage.queuedmessage.sentmessage.deliveredmessage.readmessage.statusmessage.failedmessage.inboundmessage.unsupportedbroadcast.status_changedconversation.newcontact.identity_linkedtemplate.status_changedinvitation.status_changedcall.initiatedcall.answeredcall.completedcall.faileddomain.verifieddomain.failedsecretstringWebhook secret for signature verification. Only returned on create or regenerate.
activebooleanrequiredWhether the webhook is active.
DefaulttruesignatureVersionstringrequiredWhich
X-Zavu-Signaturescheme 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 onet. The migration setting: a receiver reading either one works, so you can deploy and confirm your new verifier before switching over.
Moving from
v1straight tov2returns400. Setv1+v2first. See https://www.zavu.dev/docs/guides/receiving-messages/signature-migrationOne ofv1v1+v2v2
whatsappobjectWhatsApp Business Account information. Only present if a WABA is connected.
3 properties
phoneNumberIdstringWhatsApp phone number ID from Meta.
displayPhoneNumberstringDisplay phone number.
paymentStatusobjectPayment configuration status from Meta.
3 properties
setupStatusstringPayment setup status (COMPLETE, NOT_STARTED, etc.).
methodStatusstringPayment method status (VALID, NONE, etc.).
canSendTemplatesbooleanWhether template messages can be sent. Requires setupStatus=COMPLETE and methodStatus=VALID.
emailAddressstringFrom-address for the email channel, if configured.
emailReceivingEnabledbooleanWhether inbound email receiving is enabled for this sender.
DefaultfalseemailCatchAllEnabledbooleanWhether 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.
DefaultfalsecreatedAtstring<date-time>updatedAtstring<date-time>
400Invalid update.
codestringrequiredmessagestringrequireddetailsobject
401Unauthorized.
codestringrequiredmessagestringrequireddetailsobject
404Sender not found.
codestringrequiredmessagestringrequireddetailsobject