@messagebird/sdk 0.28.0 → 0.30.0

package/dist/index.mjs

@@ -334,9 +334,7 @@ async function setAuthParams(options) {
 			case "cookie":
 				options.headers.append("Cookie", `${name}=${token}`);
 				break;
-			default:
-				options.headers.set(name, token);
-				break;
+			default: options.headers.set(name, token);
 		}
 	}
 }
@@ -493,9 +491,7 @@ const createClient = (config = {}) => {
 						case "stream":
 							emptyData = response.body;
 							break;
-						default:
-							emptyData = {};
-							break;
+						default: emptyData = {};
 					}
 					return opts.responseStyle === "data" ? emptyData : {
 						data: emptyData,
@@ -809,7 +805,6 @@ var BirdAPIError = class extends BirdError {
 	vendorCode;
 	remediation;
 	next;
-	unmetGates;
 	constructor(fields) {
 		super(fields.message);
 		this.name = "BirdAPIError";
@@ -823,7 +818,6 @@ var BirdAPIError = class extends BirdError {
 		this.vendorCode = fields.vendorCode;
 		this.remediation = fields.remediation;
 		this.next = fields.next;
-		this.unmetGates = fields.unmetGates;
 		Object.setPrototypeOf(this, new.target.prototype);
 	}
 };
@@ -993,8 +987,7 @@ function mapResponseToError(status, body, headers) {
 		param: b.param,
 		vendorCode: b.vendor_code,
 		remediation: b.remediation,
-		next: b.next ?? [],
-		unmetGates: b.unmet_gates ?? []
+		next: b.next ?? []
 	};
 	switch (fields.type) {
 		case "auth_error": return new BirdAuthError(fields);
@@ -1294,7 +1287,7 @@ const listRealtimeAppChannels = (options) => (options.client ?? client).get({
 /**
 * Get a Realtime channel
 *
-* Returns a single channel's occupancy and (on request) counts. Channels exist implicitly — a channel appears when the first connection subscribes and vanishes when the last one leaves — so this endpoint reports state, not existence: an unknown or never-used name returns 200 with `occupied: false`, never 404.
+* Returns a single channel's occupancy and optional counts. A channel appears when its first connection subscribes and disappears when its last connection leaves. An unknown or unused name returns `200 OK` with `occupied: false`.
 */
 const getRealtimeAppChannel = (options) => (options.client ?? client).get({
 	security: [
@@ -1322,7 +1315,7 @@ const getRealtimeAppChannel = (options) => (options.client ?? client).get({
 /**
 * List members on a presence channel
 *
-* Lists the member ids currently subscribed to a presence channel. Ids only: `member_info` (the profile data attached by your authorization endpoint) is delivered to subscribed clients over the realtime connection and is not available over REST.
+* Lists the member IDs currently subscribed to a presence channel. IDs only: `member_info` (the profile data attached by your authorization endpoint) is delivered to subscribed clients over the realtime connection and is not available over REST.
 */
 const listRealtimeAppChannelMembers = (options) => (options.client ?? client).get({
 	security: [
@@ -1350,7 +1343,7 @@ const listRealtimeAppChannelMembers = (options) => (options.client ?? client).ge
 /**
 * Disconnect a member
 *
-* Disconnects all of a member's active connections (e.g. on sign-out or ban).
+* Disconnects all of a member's active connections, for example on sign-out or ban.
 */
 const disconnectRealtimeAppMember = (options) => (options.client ?? client).post({
 	security: [
@@ -1378,8 +1371,13 @@ const disconnectRealtimeAppMember = (options) => (options.client ?? client).post
 /**
 * Send an event to a member
 *
-* Delivers an event to one member of a Realtime app, addressing the person rather than a channel. Every connection that member currently holds receives it, across tabs and devices, so there is no need to track their connections or give them a channel of their own.
-* The member must have signed in on the connection for it to be addressable. Delivery is best-effort and not queued: a member holding no connections at the moment of the call simply does not receive the event.
+* Delivers an event to one member of a Realtime app, addressing the person
+* rather than a channel. Every connection that member currently holds receives
+* it across tabs and devices, without requiring a dedicated channel.
+*
+* The member must have signed in on the connection for it to be addressable.
+* Delivery is best-effort and not queued. A member with no active connections
+* at the time of the call does not receive the event.
 */
 const sendRealtimeAppMemberEvent = (options) => (options.client ?? client).post({
 	security: [
@@ -1411,7 +1409,7 @@ const sendRealtimeAppMemberEvent = (options) => (options.client ?? client).post(
 /**
 * List messages
 *
-* Returns the workspace's sent and scheduled messages, newest first, as a cursor page. Each item has the aggregate delivery `status` and per-state recipient counts, not the message body.
+* Returns the workspace's sent and scheduled messages, newest first, as a cursor page. Each item has the aggregate delivery `status` and per-state recipient counts. Message bodies are omitted.
 *
 * Combine filters to narrow the page:
 *
@@ -1435,17 +1433,17 @@ const listEmailMessages = (options) => (options?.client ?? client).get({
 	...options
 });
 /**
-* Send an email message
+* Create an email message
 *
 * Sends an email to the recipients you list explicitly in `to`/`cc`/`bcc`. Use it for
 * transactional sends (receipts, password resets, alerts) and for marketing sends where
 * you have the recipient addresses on hand. To submit many independent messages in one
-* request, use [Send a batch of messages](/docs/api/reference/create-email-message-batch)
+* request, use [Create a batch of email messages](/docs/api/reference/create-email-message-batch)
 * instead. The `category` field controls suppression policy independently of content:
-* set it to `marketing` when sending marketing content from this endpoint.
+* set it to `marketing` when sending marketing content.
 *
-* The `202` response means the message is safely accepted for delivery, not yet
-* delivered. Fetch it by `id` or subscribe to webhook events to follow delivery. The
+* The `202` response means the message is safely accepted and awaiting delivery.
+* Fetch it by `id` or subscribe to webhook events to follow delivery. The
 * request never half-succeeds: an unverified sender domain or any field-level
 * validation failure rejects it immediately with a `422` naming the reason.
 * Suppression is evaluated per recipient after acceptance, so a suppressed recipient
@@ -1472,9 +1470,9 @@ const createEmailMessage = (options) => (options.client ?? client).post({
 	}
 });
 /**
-* Send a batch of messages
+* Create a batch of email messages
 *
-* Accepts up to 100 independent email messages and queues them for delivery. All items are validated before any are queued: if one fails validation, the entire batch is rejected. Field-level validation failures and business-rule failures (such as `domain_not_verified`) both return `422`. Suppression is evaluated per recipient after acceptance, never as a synchronous error. The `202` response returns one entry per message in submission order, each with its own `id` you can use to fetch that message or match it against webhook events. Attachments are allowed per message. Each message must stay within the 20 MB estimated generated message-size cap, and the serialized JSON request body for the whole batch has a hard 20 MB cap.
+* Accepts up to 100 independent email messages and queues them for delivery. All items are validated before any are queued: if one fails validation, the entire batch is rejected. Field-level validation failures and business-rule failures, such as sending from a domain that is not verified, both return `422`. None of the items can set `scheduled_at`; schedule a single message with [Create an email message](/docs/api/reference/create-email-message) instead. Suppression is evaluated per recipient after acceptance, never as a synchronous error. The `202` response returns one entry per message in submission order, each with its own `id` you can use to fetch that message or match it against webhook events. Attachments are allowed per message. Each message must stay within the 20 MB estimated generated message-size cap, and the serialized JSON request body for the whole batch has a hard 20 MB cap.
 *
 */
 const createEmailMessageBatch = (options) => (options.client ?? client).post({
@@ -1532,7 +1530,7 @@ const cancelEmailMessage = (options) => (options.client ?? client).post({
 /**
 * List contacts
 *
-* Returns a paginated list of contacts in the workspace, newest first. Look up a single contact by its exact `email`, `phone_number`, or `external_id`, or search by email, first name, last name, or phone substring with `q`. Pass `include_total=true` to add the total number of matching contacts to the response.
+* Returns a paginated list of contacts in the workspace, newest first. Look up a single contact by its exact `email`, `phone_number`, or `external_id`, or search by email, first name, last name, or phone substring with `q`. Repeat `phone_number` to resolve up to 50 numbers to their contacts in one request, raising `limit` to at least the number of values you pass. Pass `include_total=true` to add the total number of matching contacts to the response.
 *
 */
 const listContacts = (options) => (options?.client ?? client).get({
@@ -1574,7 +1572,7 @@ const createContact = (options) => (options.client ?? client).post({
 /**
 * Create or update contacts in bulk
 *
-* Creates or updates up to 1,000 contacts in one request. Each entry is matched automatically against every identifier it supplies: its email address (trimmed and lowercased before matching), its phone number (normalized to international form), and your own `external_id`. An entry that matches no existing contact creates one; an entry whose identifiers all point at one contact updates it with the fields it supplies, and omitted fields keep their stored values, so a contact's email address can change under a stable `external_id` without creating a second record. An entry whose identifiers belong to more than one contact fails with an error naming each matched contact, since Bird never merges contacts or picks between them. Supplying `match_on` overrides the automatic matching: every entry is matched by that one field only, and must carry it. Optionally adds every contact in the request to up to 10 audiences.
+* Creates or updates up to 1,000 contacts in one request. Each entry is matched automatically against every identifier it supplies: its email address (trimmed and lowercased), its phone number (normalized to international form), and your own `external_id`. An entry with no match creates a contact. An entry whose identifiers all match one contact updates the supplied fields and preserves omitted fields. This lets an email address change under a stable `external_id` without creating a second contact. An entry whose identifiers belong to several contacts fails with an error naming each match; contacts are never merged automatically. Supplying `match_on` makes that field the only matching key, and every entry must include it. You can also add every contact in the request to up to 10 audiences.
 *
 * Each entry succeeds or fails on its own: the response lists one result per contact in submission order (`created`, `updated`, or `failed` with the reason), and a failed entry does not abort the rest. If the request itself is invalid, for example when an entry in `audience_ids` does not exist, the whole request fails with a validation error and no contacts are written.
 *
@@ -1634,9 +1632,9 @@ const getContact = (options) => (options.client ?? client).get({
 /**
 * Update a contact
 *
-* Updates a contact. Supplied fields are changed and omitted fields are left unchanged; set `first_name`, `last_name`, or `external_id` to null to clear them. Custom values in `data` are merged: keys you supply are set, keys set to null are removed, and keys you omit are unchanged.
+* Updates a contact. Supplied fields are changed and omitted fields are left unchanged; set `first_name`, `last_name`, or `external_id` to `null` to clear them. Custom values in `data` are merged: keys you supply are set, keys set to `null` are removed, and keys you omit are unchanged.
 *
-* Changing the email address, phone number, or `external_id` to a value already used by another contact returns a conflict error, and a contact always keeps at least one identifier: clearing both email and phone in the same contact is rejected.
+* Changing the email address, phone number, or `external_id` to a value already used by another contact returns a conflict error. A contact always keeps at least one identifier. Clearing both email and phone in the same contact is rejected.
 *
 */
 const updateContact = (options) => (options.client ?? client).patch({
@@ -1796,7 +1794,7 @@ const listAudiences = (options) => (options?.client ?? client).get({
 /**
 * Create an audience
 *
-* Creates an audience in the workspace. New audiences start empty: add members with [Add contacts to an audience](/docs/api/reference/assign-audience-contacts) or through [Create or update contacts in bulk](/docs/api/reference/create-contact-batch). Only `static` audiences can be created today; requesting `dynamic` or `external` returns a validation error.
+* Creates an audience in the workspace. New audiences start empty: add members with [Add contacts to an audience](/docs/api/reference/assign-audience-contacts) or through [Create or update contacts in bulk](/docs/api/reference/create-contact-batch). The `type` field currently accepts only `static` audiences.
 *
 */
 const createAudience = (options) => (options.client ?? client).post({
@@ -1854,7 +1852,7 @@ const getAudience = (options) => (options.client ?? client).get({
 /**
 * Update an audience
 *
-* Updates an audience's name or description. Omitted fields are left unchanged; set `description` to null to clear it.
+* Updates an audience's name or description. Omitted fields are left unchanged; set `description` to `null` to clear it.
 *
 */
 const updateAudience = (options) => (options.client ?? client).patch({
@@ -1892,9 +1890,9 @@ const listAudienceContacts = (options) => (options.client ?? client).get({
 	...options
 });
 /**
-* Add contacts to an audience
+* Assign contacts to an audience
 *
-* Adds up to 1,000 contacts to an audience. Adding is idempotent: contacts that are already members are left in place and keep their original join time. If any contact ID does not exist in the workspace, the whole request fails with a validation error and no contacts are added.
+* Adds up to 1,000 contacts to an audience. Adding is idempotent: contacts that are already members are left in place and keep their original join time. If any contact ID does not exist in the workspace, the whole request fails with `422 Unprocessable Entity` and no contacts are added.
 *
 */
 const assignAudienceContacts = (options) => (options.client ?? client).post({
@@ -1914,9 +1912,9 @@ const assignAudienceContacts = (options) => (options.client ?? client).post({
 	}
 });
 /**
-* Remove contacts from an audience
+* Unassign contacts from an audience
 *
-* Removes up to 1,000 contacts from an audience. Contacts that are not members are skipped. If any contact ID does not exist in the workspace, the whole request fails with a validation error and no memberships are removed. The contacts themselves are not deleted and remain members of any other audiences.
+* Removes up to 1,000 contacts from an audience. Contacts that are not members are skipped. If any contact ID does not exist in the workspace, the whole request fails with `422 Unprocessable Entity` and no memberships are removed. The contacts themselves are not deleted and remain members of any other audiences.
 *
 */
 const unassignAudienceContacts = (options) => (options.client ?? client).post({
@@ -1936,9 +1934,9 @@ const unassignAudienceContacts = (options) => (options.client ?? client).post({
 	}
 });
 /**
-* Remove a contact from an audience
+* Unassign a contact from an audience
 *
-* Removes a contact's membership in an audience. The contact itself is not deleted and remains a member of any other audiences. Removing a contact that is not a member of the audience succeeds with no effect (204); an unknown audience or contact returns a not-found error.
+* Removes a contact's membership in an audience. The contact itself is not deleted and remains a member of any other audiences. Removing a contact that is not a member of the audience succeeds with no effect (`204 No Content`); an unknown audience or contact returns a not-found error.
 *
 */
 const unassignAudienceContact = (options) => (options.client ?? client).delete({
@@ -1956,9 +1954,17 @@ const unassignAudienceContact = (options) => (options.client ?? client).delete({
 /**
 * List SMS messages
 *
-* Returns the workspace's SMS messages as a cursor-paginated list, newest first. Filter by direction, status, category, recipient, sender, failure reason, tag, or creation time; pass the response's `next_cursor` back as `starting_after` to fetch the next page. To follow a single message's delivery, use [Get an SMS message](/docs/api/reference/get-sms-message) instead.
+* Returns the workspace's SMS messages as a cursor-paginated list, newest
+* first. Filter by direction, status, category, recipient, sender, failure
+* reason, tag, or creation time; pass the response's `next_cursor` back as
+* `starting_after` to fetch the next page. To follow a single message's
+* delivery, use [Get an SMS message](/docs/api/reference/get-sms-message)
+* instead.
 *
-* Messages are retained for **30 days**. A `created_after` earlier than that is accepted and raised to the retention bound rather than rejected, so a wider window returns what is still retained instead of failing. There is no way to read messages older than the window.
+* Messages are retained for **30 days**. A `created_after` earlier than that
+* is accepted and raised to the retention bound rather than rejected, so a
+* wider window returns what is still retained instead of failing. Messages
+* older than the retention window cannot be retrieved.
 *
 */
 const listSmsMessages = (options) => (options?.client ?? client).get({
@@ -1974,24 +1980,22 @@ const listSmsMessages = (options) => (options?.client ?? client).get({
 	...options
 });
 /**
-* Send an SMS message
+* Create an SMS message
 *
-* Sends one SMS message to a single recipient. A send carries exactly one
-* content form: `text` (free text, which also requires `category`) or
-* `template` (a stored template that supplies the body and category). To
-* submit up to 100 independent messages in one request, use
+* Sends one SMS to one recipient with exactly one content form: `text`, which
+* requires `category` and `from`, or a stored `template`, which selects both
+* for you. To submit up to 100 independent messages in one request, use
 * [Send a batch of SMS messages](/docs/api/reference/create-sms-message-batch)
 * instead.
 *
-* The `202` response means Bird durably accepted the message for asynchronous
-* delivery, not that it was delivered. Follow delivery with
+* The `202 Accepted` response means the API durably accepted the message for
+* asynchronous delivery. Delivery remains pending; follow it with
 * [Get an SMS message](/docs/api/reference/get-sms-message) or by subscribing
 * to `sms.*` webhook events.
 *
-* Sends fail with a `422` when a field is invalid, the body exceeds the
-* 12-segment cap, the destination country is not enabled for the workspace,
-* or the sender is not permitted for the destination; a send from a
-* workspace with no wallet balance fails with a `402`.
+* An invalid field, more than 12 segments, a disabled destination country, or
+* a sender not permitted for the destination returns `422`. Insufficient
+* wallet balance returns `402`.
 *
 */
 const createSmsMessage = (options) => (options.client ?? client).post({
@@ -2011,10 +2015,10 @@ const createSmsMessage = (options) => (options.client ?? client).post({
 	}
 });
 /**
-* Send a batch of SMS messages
+* Create a batch of SMS messages
 *
 * Sends up to 100 independent SMS messages in one request. Each item is a
-* complete send request with its own recipient, content, id, status, and
+* complete send request with its own recipient, content, ID, status, and
 * cost. For a single message, use
 * [Send an SMS message](/docs/api/reference/create-sms-message) instead.
 *
@@ -2044,7 +2048,7 @@ const createSmsMessageBatch = (options) => (options.client ?? client).post({
 /**
 * Get an SMS message
 *
-* Returns a single SMS message: its current delivery status, segment breakdown, cost, and failure detail when it failed. The `status` advances asynchronously as delivery progresses, and `cost` is null until the message has been priced, so poll this endpoint (or subscribe to `sms.*` webhook events) after a send to confirm delivery. To scan messages in bulk, use [List SMS messages](/docs/api/reference/list-sms-messages) instead.
+* Returns a single SMS message: its current delivery status, segment breakdown, cost, and failure detail when it failed. The `status` advances asynchronously as delivery progresses, and `cost` is null until the message has been priced, so poll this operation (or subscribe to `sms.*` webhook events) after a send to confirm delivery. To scan messages in bulk, use [List SMS messages](/docs/api/reference/list-sms-messages) instead.
 *
 */
 const getSmsMessage = (options) => (options.client ?? client).get({
@@ -2060,12 +2064,11 @@ const getSmsMessage = (options) => (options.client ?? client).get({
 	...options
 });
 /**
-* List SMS templates
-*
-* Returns the SMS templates you can send from, including Bird's built-in templates. Filter by scope, category, or language; the catalogue is small and returned in full, so this list is not paginated. To read one template's variables before sending with it, use [Get an SMS template](/docs/api/reference/get-sms-template).
+* List events for an SMS message
 *
+* Returns the lifecycle event timeline for a message, in chronological order.
 */
-const listSmsTemplates = (options) => (options?.client ?? client).get({
+const listSmsMessageEvents = (options) => (options.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2074,16 +2077,16 @@ const listSmsTemplates = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/sms/templates",
+	url: "/v1/sms/messages/{message_id}/events",
 	...options
 });
 /**
-* Get an SMS template
+* List SMS templates
 *
-* Returns a single SMS template: its body preview, category, the `variables` it expects (each with its accepted format), and the languages it is available in. Fetch a template before sending with it to see which `parameters` keys are required; an unknown reference returns a `404`. To browse the whole catalogue, use [List SMS templates](/docs/api/reference/list-sms-templates) instead.
+* Returns the SMS templates you can send from, including our built-in templates. Filter by scope, category, or language; the catalog is small and returned in full, so this list is not paginated. To read one template's variables before sending with it, use [Get an SMS template](/docs/api/reference/get-sms-template).
 *
 */
-const getSmsTemplate = (options) => (options.client ?? client).get({
+const listSmsTemplates = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2092,24 +2095,16 @@ const getSmsTemplate = (options) => (options.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/sms/templates/{template_ref}",
+	url: "/v1/sms/templates",
 	...options
 });
 /**
-* Look up a phone number
-*
-* Returns what we know about a phone number: which network serves it, which network issued it, whether it has been ported, its country, and what kind of line it is. That baseline is included with every lookup.
-*
-* Use `type` to buy more. Each value adds a block to the answer: how the number is classified, whether it is live on the network right now, whether it is roaming, when its SIM last changed, its porting record, or a credibility score. Omit `type` and the response is the baseline alone, and no intelligence provider is contacted.
-*
-* Every block you request comes back carrying a `status`, so a partial answer is visible rather than silent, and **you are billed for exactly the blocks whose status is `ok`**.
-*
-* Send the number in the body rather than the URL when you would rather it did not appear in request logs or browser history. [Look up a phone number by URL](/docs/api/reference/get-phone-number-lookup) is the same lookup with the number in the path.
+* Get an SMS template
 *
-* Send an `Idempotency-Key` and a retried request returns the stored answer instead of looking the number up and charging again. Without one, every attempt is a new lookup and is billed.
+* Returns a single SMS template: its body preview, category, the `variables` it expects (each with its accepted format), and the languages it is available in. Fetch a template before sending with it to see which `parameters` keys are required; an unknown reference returns a `404`. To browse the whole catalog, use [List SMS templates](/docs/api/reference/list-sms-templates) instead.
 *
 */
-const createPhoneNumberLookup = (options) => (options.client ?? client).post({
+const getSmsTemplate = (options) => (options.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2118,34 +2113,20 @@ const createPhoneNumberLookup = (options) => (options.client ?? client).post({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/lookup/phone-number",
-	...options,
-	headers: {
-		"Content-Type": "application/json",
-		...options.headers
-	}
+	url: "/v1/sms/templates/{template_ref}",
+	...options
 });
 /**
-* Look up an email address
+* List SMS suppressions
 *
-* Returns whether an email address is worth sending to:
+* Returns the suppressions currently stopping your messages, most recent opt-out first. Pass `destination` to look up one subscriber before sending to them.
 *
-* - Whether it will accept mail.
-* - How confident that is.
-* - Why not, when it will not.
-* - Whether it is a role, disposable, or free-provider address.
-* - What it looks like it was meant to be, when it looks misspelled.
+* A suppression covers one sender and one subscriber, so the same number can appear more than once: opting out of one of your senders does not opt out of the others.
 *
-* One address per call, and one answer: `result` is the field to decide on. Every answer costs the same, including `undeliverable`, which is usually the most valuable one you can get.
-*
-* `result` and `reason` are open vocabularies: the values below are the ones in use today, and further ones may be added. Branch on the values you know and treat anything else as a future value rather than an error. `delivery_confidence` is always present and always comparable, so it is the safe fallback.
-*
-* Send the address in the body rather than the URL when you would rather it did not appear in request logs or browser history. [Look up an email address by URL](/docs/api/reference/get-email-lookup) is the same lookup with the address in the path.
-*
-* Send an `Idempotency-Key` and a retried request returns the stored answer instead of validating the address and charging again. Without one, every attempt is a new lookup and is billed.
+* Ended suppressions are excluded. A subscriber who opted back in is reachable again and does not appear in this list.
 *
 */
-const createEmailLookup = (options) => (options.client ?? client).post({
+const listSmsSuppressions = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2154,24 +2135,18 @@ const createEmailLookup = (options) => (options.client ?? client).post({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/lookup/email",
-	...options,
-	headers: {
-		"Content-Type": "application/json",
-		...options.headers
-	}
+	url: "/v1/sms/suppressions",
+	...options
 });
 /**
-* Create a verification
+* Create an SMS suppression
 *
-* Creates a verification for a recipient and sends them a one-time passcode. Provide the recipient in `to`: an email address (verified over email), a phone number (verified over the phone channels enabled for its destination country), or both. The passcode is sent over one channel at a time and delivery falls over to the next channel in the plan if one fails; it is never sent over two channels at once.
+* Stops a sender's messages to a subscriber, with reason `manual`, blocking every category including transactional. Both ends are required: a suppression covers a sender-and-subscriber pair, so stopping all of your senders means one call per sender.
 *
-* Calling this again for the same recipient resumes the verification in progress rather than starting a second one: within the resend cooldown the request returns the current state without sending, and after it a fresh passcode is sent. Use the same call to send and to resend.
-*
-* The `200` response is the verification's current state; the passcode itself is never returned. Submit the passcode the recipient enters with POST /v1/verify/verifications/check before the verification's `expires_at`. An invalid recipient returns `422`, and requesting passcodes for the same recipient too often returns `429`.
+* Adding is idempotent. A `201` means a new suppression was recorded, and a `200` means a `manual` one for that pair was already in place and is returned unchanged. A pair already stopped for another reason, such as the subscriber having texted a stop keyword, still gets its own `manual` record, and messages stay stopped until every one of them has ended.
 *
 */
-const createVerification = (options) => (options.client ?? client).post({
+const createSmsSuppression = (options) => (options.client ?? client).post({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2180,7 +2155,7 @@ const createVerification = (options) => (options.client ?? client).post({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/verify/verifications",
+	url: "/v1/sms/suppressions",
 	...options,
 	headers: {
 		"Content-Type": "application/json",
@@ -2188,16 +2163,16 @@ const createVerification = (options) => (options.client ?? client).post({
 	}
 });
 /**
-* Check a verification passcode
+* Delete an SMS suppression
 *
-* Checks a passcode for a recipient and returns the outcome together with the verification's current state. Identify the verification by the same `to` used to create it; you do not need to store a verification ID.
+* Ends a suppression, so the sender reaches the subscriber again. The record stays with the ending noted on it. This history helps answer later complaints or carrier audits.
 *
-* A wrong or expired passcode is a normal outcome, not an HTTP error: the response is `200` with `success` set to `false` and a `reason` such as `incorrect_code` or `expired`. `success: true` means the verification is complete. Each verification reports its final outcome exactly once and is no longer checkable afterwards.
+* **Only the `manual` reason can be ended here.** A `keyword_stop` is the subscriber's own statement. It ends only when they text a start keyword to that sender. A `carrier_opted_out` mirrors what the carrier reported, so it ends when the carrier says so. Attempts to end either reason return `422`.
 *
-* An error status is returned only when the check cannot be evaluated: `404` when no verification matches the recipient or the matching one already reached its final state, `422` for an invalid recipient, and `429` when passcodes for a recipient are checked too quickly.
+* Ending a suppression resumes messaging to someone your own records say did not want it, so do it only when you know why the `manual` record exists. An ID that does not exist in the workspace returns `404`, and one that has already ended returns `204`.
 *
 */
-const createVerificationCheck = (options) => (options.client ?? client).post({
+const deleteSmsSuppression = (options) => (options.client ?? client).delete({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2206,24 +2181,18 @@ const createVerificationCheck = (options) => (options.client ?? client).post({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/verify/verifications/check",
-	...options,
-	headers: {
-		"Content-Type": "application/json",
-		...options.headers
-	}
+	url: "/v1/sms/suppressions/{suppression_id}",
+	...options
 });
 /**
-* Advance a verification to its next channel
+* Get an SMS suppression
 *
-* Advances an in-progress verification to the next channel in its plan and sends a fresh passcode there, for a recipient who reports not receiving the code. Identify the verification by the same `to` used to create it; you do not need to store a verification ID.
+* Returns one suppression: the sender and subscriber it covers, why messages are stopped, how the record came to exist, what it blocks, and whether it is still in force.
 *
-* The send bypasses the resend cooldown (a deliberate channel switch is a different act from a same-channel resend), and every passcode already sent stays valid, so a code that arrives late can still be checked. The response is the verification with `last_channel` set to the channel the new passcode went to. Concurrent requests for the same recipient are safe: each advances the plan at most one step. When two race, the request that completes the newer send is the authoritative one; the other returns the verification's committed state, whose `last_channel` still names the most recent send that completed. A later read of the verification always reflects the settled outcome.
-*
-* An error status is returned when the verification cannot be advanced: `404` when no verification is in progress for the recipient, `422` with `NoNextChannel` when the plan has no further channel (fall back to a plain resend), `422` with `NoAvailableChannel` when every remaining channel failed to send, and `429` when sends for the account are requested too quickly.
+* This operation also returns a suppression that has already ended. The `blocking` field is `false`, and the `ended_*` fields say when and why. An ID you kept from a create or delete therefore stays readable. To find one when you only know the number, use `GET /v1/sms/suppressions` with the `destination` parameter. An ID that does not exist in the workspace returns `404`.
 *
 */
-const createVerificationNextChannel = (options) => (options.client ?? client).post({
+const getSmsSuppression = (options) => (options.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2232,31 +2201,20 @@ const createVerificationNextChannel = (options) => (options.client ?? client).po
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/verify/verifications/next-channel",
-	...options,
-	headers: {
-		"Content-Type": "application/json",
-		...options.headers
-	}
+	url: "/v1/sms/suppressions/{suppression_id}",
+	...options
 });
 /**
-* List WhatsApp messages
+* List SMS keyword rules
 *
-* Returns the workspace's WhatsApp messages as a cursor-paginated list,
-* newest first. Filter by direction, status, contact phone number,
-* business-scoped user ID, template category, tag, or creation time; pass the response's `next_cursor` back as
-* `starting_after` to fetch the next page. To follow a single message's
-* delivery, use
-* [Get a WhatsApp message](/docs/api/reference/get-whats-app-message)
-* instead.
+* Returns the default and workspace keyword rules that apply to inbound messages, most specific first. Where the default catalog covers a country, opt-out, opt-in, and help keywords work without setup.
 *
-* Messages are retained for **30 days**. A `created_after` earlier than that
-* is accepted and raised to the retention bound rather than rejected, so a
-* wider window returns what is still retained instead of failing. There is no
-* way to read messages older than the window.
+* Use the filters to narrow the full, unpaginated list. Set `scope=system` for default rules only. Set `number` for rules in evaluation order, and add `from_country` to account for the sender's country.
+*
+* Default coverage varies by country. If a country has no default rules, the service does not recognize keywords, send replies, or record opt-outs there. You can add `custom` keywords for that country. Opt-out, opt-in, and help rules require default coverage.
 *
 */
-const listWhatsAppMessages = (options) => (options?.client ?? client).get({
+const listSmsKeywordRules = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2265,33 +2223,18 @@ const listWhatsAppMessages = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/whatsapp/messages",
+	url: "/v1/sms/keyword-rules",
 	...options
 });
 /**
-* Send a WhatsApp message
-*
-* Sends a WhatsApp message built from a message template to one recipient.
-* Name the template, optionally pick its language variant, and fill its
-* placeholders in `components`; a Bird-managed template selects its sender
-* number from its category, so the request carries no sender field. A request
-* that carries no content is rejected with a `422`. Browse your workspace's
-* templates in the Bird dashboard.
+* Create an SMS keyword rule
 *
-* The `202` response is the accepted message, echoing the resolved template
-* and language; it is not a delivery confirmation. Follow delivery with
-* [Get a WhatsApp message](/docs/api/reference/get-whats-app-message), the
-* per-message timeline from
-* [List events for a WhatsApp message](/docs/api/reference/list-whats-app-message-events),
-* or `whatsapp.*` webhook events.
+* Creates a workspace keyword rule. Use it to replace the default opt-out, opt-in, or help reply for one country, or to add a `custom` keyword.
 *
-* A template slug or language the catalogue does not stock, parameter values
-* that do not match the template's declared placeholders, and a recipient
-* that is not a valid phone number each return a `422`, as does a request
-* that carries no content at all.
+* Your rule takes precedence over the default for the same country and keeps default keywords unless you add more. Opt-out and opt-in keywords cannot be assigned to another operation.
 *
 */
-const createWhatsAppMessage = (options) => (options.client ?? client).post({
+const createSmsKeywordRule = (options) => (options.client ?? client).post({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2300,7 +2243,7 @@ const createWhatsAppMessage = (options) => (options.client ?? client).post({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/whatsapp/messages",
+	url: "/v1/sms/keyword-rules",
 	...options,
 	headers: {
 		"Content-Type": "application/json",
@@ -2308,12 +2251,12 @@ const createWhatsAppMessage = (options) => (options.client ?? client).post({
 	}
 });
 /**
-* Get a WhatsApp message
+* Delete an SMS keyword rule
 *
-* Returns a single WhatsApp message: its current delivery status, per-stage timestamps (`sent_at`, `delivered_at`, `read_at`), the template it was sent from, and failure detail when it failed. The `status` advances asynchronously as delivery progresses, so poll this endpoint (or subscribe to `whatsapp.*` webhook events) after a send to confirm delivery. For the per-event timeline, use [List events for a WhatsApp message](/docs/api/reference/list-whats-app-message-events) instead.
+* Deletes a rule you created. Bird's default for that operation and country applies again straight away, so deleting an opt-out rule restores Bird's reply rather than switching opt-out off. Bird's defaults cannot be deleted.
 *
 */
-const getWhatsAppMessage = (options) => (options.client ?? client).get({
+const deleteSmsKeywordRule = (options) => (options.client ?? client).delete({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2322,16 +2265,17 @@ const getWhatsAppMessage = (options) => (options.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/whatsapp/messages/{message_id}",
+	url: "/v1/sms/keyword-rules/{id}",
 	...options
 });
 /**
-* List events for a WhatsApp message
+* Get an SMS keyword rule
 *
-* Returns a WhatsApp message's lifecycle events in chronological order, one entry per delivery transition (`whatsapp.accepted`, `whatsapp.sent`, `whatsapp.delivered`, `whatsapp.read`, `whatsapp.failed`). The timeline is bounded and returned in full, so this list is not paginated; an unknown message id returns a `404`. For the message's current state in a single field, use [Get a WhatsApp message](/docs/api/reference/get-whats-app-message) instead.
+* Returns one keyword rule, either one of Bird's defaults or one you created, including
+* every keyword that matches it and the reply it sends.
 *
 */
-const listWhatsAppMessageEvents = (options) => (options.client ?? client).get({
+const getSmsKeywordRule = (options) => (options.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2340,20 +2284,21 @@ const listWhatsAppMessageEvents = (options) => (options.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/whatsapp/messages/{message_id}/events",
+	url: "/v1/sms/keyword-rules/{id}",
 	...options
 });
 /**
-* Daily sending statistics
-*
-* Returns one row of aggregate sending statistics per calendar day for the workspace: UTC days by default, or your local days when `timezone` is set. Days with no activity are included with zero counts, so the series charts without client-side gap handling. Suited to charts and trend lines; for per-message exact accounting use the message detail endpoints.
+* Update an SMS keyword rule
 *
-* Rows are bucketed by event time, not send time: a complaint received on Wednesday for a message sent the prior Monday is counted in Wednesday's row.
+* Changes the reply or the added keywords of a rule you created. Bird's defaults cannot be
+* changed. To replace one, create a rule with the same operation and country and yours
+* takes precedence.
 *
-* The maximum window is 365 days; requesting a longer range returns 422.
+* What the rule applies to is fixed once created, so this changes the reply and the keywords
+* only.
 *
 */
-const getEmailStatsDaily = (options) => (options?.client ?? client).get({
+const updateSmsKeywordRule = (options) => (options.client ?? client).patch({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2362,20 +2307,24 @@ const getEmailStatsDaily = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/daily",
-	...options
+	url: "/v1/sms/keyword-rules/{id}",
+	...options,
+	headers: {
+		"Content-Type": "application/json",
+		...options.headers
+	}
 });
 /**
-* Hourly sending statistics
+* Get aggregate SMS statistics
 *
-* Returns one row of aggregate sending statistics per hour for the workspace: UTC hours by default, or your local hours when `timezone` is set (a timezone with a sub-hour offset gets correctly aligned hours). Useful for inspecting send rate, deliverability, and engagement inside a single day or a recent window; hours with no activity are included with zero counts.
+* Returns one aggregate row for the requested period. It includes SMS lifecycle counts, delivery and failure rates, and processing, delivery, and total latency percentiles (`p50`, `p95`, and `p99`). Rows use send-time attribution, so recent periods can under-report `delivered` while delivery reports arrive.
 *
-* Rows are bucketed by event time, not send time: a click recorded at 14:07 for a message sent at 09:00 lands in the 14:00 row.
+* Rate fields are `null` when their denominator is zero. For example, `delivery_rate` is `null` when no message was accepted.
 *
-* A single request may span at most 30 days (720 hourly rows); for longer ranges use the daily endpoint, which has a 365-day window. An hourly window longer than 30 days, or a `from` after `to`, returns 422.
+* `from` and `to` must both be days or RFC 3339 instants. Day windows cover up to 365 days. Instant bounds round down to the hour and may span up to 720 hours. Mixing the forms returns `422`. Set `timezone` for local boundaries, one dimension filter at most, or `compare=previous_period` for the preceding equal-length window.
 *
 */
-const getEmailStatsHourly = (options) => (options?.client ?? client).get({
+const getSmsStatsSummary = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2384,20 +2333,20 @@ const getEmailStatsHourly = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/hourly",
+	url: "/v1/sms/stats/summary",
 	...options
 });
 /**
-* Stats by tag
+* Get daily SMS statistics
 *
-* Returns delivery and engagement counts for the requested period, grouped by tag. Use it to compare performance across the tags you set at send time. Rows are ranked by the `sort` metric, `processed` by default, and capped at the requested `limit` (50 by default, 200 at most).
+* Returns one row of SMS lifecycle counts per calendar day. Rows use send-time attribution, so a delivery confirmation is counted on the day when its message was accepted. Recent rows can under-report `delivered` while delivery reports arrive. Days without activity contain zero counts.
 *
-* Rows are computed against event time rather than send time, so engagement received during the period counts even for messages that were sent earlier.
+* Rates and latency are whole-window aggregates available from the summary endpoint. Use the message detail endpoints for individual message status.
 *
-* The window can span at most 365 days. Ask for more and you get a 422.
+* A request may span up to 365 days; a longer window returns `422`. Set `timezone` for local calendar days instead of UTC.
 *
 */
-const getEmailStatsByTag = (options) => (options?.client ?? client).get({
+const getSmsStatsDaily = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2406,20 +2355,20 @@ const getEmailStatsByTag = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/tags",
+	url: "/v1/sms/stats/daily",
 	...options
 });
 /**
-* Aggregate stats summary
+* Get hourly SMS statistics
 *
-* Returns a single-row aggregate across the requested period covering delivery, bounce, complaint, open, and click counts plus the derived rates, along with processing, delivery, and total latency percentiles (p50/p95/p99). Suitable for KPI tiles, campaign reports, and email digests; the daily and hourly endpoints have the same metrics per time bucket.
+* Returns one row of SMS lifecycle counts per hour. Rows use send-time attribution, so a delivery confirmation is counted in the hour when its message was accepted. Recent rows can under-report `delivered` while delivery reports arrive.
 *
-* The aggregate is computed against event time (not send time), so engagement received during the period for messages sent earlier is included. Rate fields are null when their denominator is zero.
+* Rates and latency are whole-window aggregates available from the summary endpoint. Set `timezone` for local hours instead of UTC, including zones with sub-hour offsets.
 *
-* The window grain follows the form of `from` and `to`: calendar days (`YYYY-MM-DD`, up to 365 days) or RFC 3339 instants (hour grain, up to 720 hours, 30 days), so a rolling window such as the last 24 hours is a single request. Mixing the two forms returns 422. Set `timezone` to compute day and hour boundaries in a local zone instead of UTC, and `compare=previous_period` to include the preceding equal-length window in the same response.
+* A request may span up to 30 days (720 rows). `from` and `to` are ISO 8601 instants; each bound rounds down to the hour and remains inclusive. An excessive or reversed window returns `422`. Use the daily endpoint for longer ranges.
 *
 */
-const getEmailStatsSummary = (options) => (options?.client ?? client).get({
+const getSmsStatsHourly = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2428,20 +2377,20 @@ const getEmailStatsSummary = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/summary",
+	url: "/v1/sms/stats/hourly",
 	...options
 });
 /**
-* Stats by sending IP
+* Get SMS statistics by originator
 *
-* Returns delivery and deliverability counts for the requested period, grouped by the specific IP address used to send each message. Use it to spot a reputation problem on one IP. Block bounces concentrated on a single IP usually mean that IP's reputation has taken a hit, and sorting by `bounces.block` puts those IPs first.
+* Returns aggregate delivery and latency stats grouped by originator (the sender address messages were sent from) for the requested period. Rows are ranked by the `sort` metric (default `accepted`) descending and capped at the requested `limit` (default 50, hard maximum 200). Use this to compare sending performance across the senders you dispatch from.
 *
-* A sending IP is only known once the receiving mail server reports an outcome: a delivery, a bounce, a deferral, or a late bounce. So this breakdown starts from the delivery stage onward. Accepted, processed, and rejected counts aren't included at all, and neither are engagement counts or processing latency. Complaints and out-of-band bounces aren't attributed to a sending IP either, so `complained` and `oob_bounces` are included but always read 0 here. Bounced, deferred, delivery latency, and total latency are the ones that have real numbers. For workspace-wide figures, use `GET /v1/email/stats/daily`. Rows are computed against event time rather than send time.
+* Rows use send-time attribution. A delivery confirmed during the period for a message accepted earlier counts against the earlier period. A recent period therefore under-reports `delivered` while delivery reports are still arriving, and its counts grow as reports arrive.
 *
-* Rows are ranked by the `sort` field, `delivered` by default, and capped at the requested `limit` (50 by default, 200 at most). The window can span at most 365 days. Ask for more and you get a 422.
+* The maximum window is 365 days; requesting a longer range returns 422.
 *
 */
-const getEmailStatsBySendingIp = (options) => (options?.client ?? client).get({
+const getSmsStatsByOriginator = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2450,20 +2399,20 @@ const getEmailStatsBySendingIp = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/sending-ips",
+	url: "/v1/sms/stats/originators",
 	...options
 });
 /**
-* Stats by sending domain
+* Get SMS statistics by country
 *
-* Returns delivery, engagement, and deliverability counts for the requested period, grouped by sending domain: the portion of the `From` address after the `@`. Use it to compare deliverability across multiple verified domains in your workspace, for example transactional versus marketing domains, or sub-domain segregation during IP warming.
+* Returns aggregate delivery and latency stats grouped by destination country for the requested period. Rows are ranked by the `sort` metric (default `accepted`) descending and capped at the requested `limit` (default 50, hard maximum 200). Use this to compare sending performance across the countries you send to.
 *
-* Rows are computed against event time rather than send time, so engagement and bounces received during the period count even for messages that were sent earlier.
+* Rows use send-time attribution. A delivery confirmed during the period for a message accepted earlier counts against the earlier period. A recent period therefore under-reports `delivered` while delivery reports are still arriving, and its counts grow as reports arrive.
 *
-* Rows are ranked by the `sort` metric, `processed` by default, and capped at the requested `limit` (50 by default, 200 at most). The window can span at most 365 days. Ask for more and you get a 422.
+* The maximum window is 365 days; requesting a longer range returns 422.
 *
 */
-const getEmailStatsBySendingDomain = (options) => (options?.client ?? client).get({
+const getSmsStatsByCountry = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2472,20 +2421,20 @@ const getEmailStatsBySendingDomain = (options) => (options?.client ?? client).ge
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/sending-domains",
+	url: "/v1/sms/stats/countries",
 	...options
 });
 /**
-* Stats by category
+* Get SMS statistics by category
 *
-* Returns delivery and engagement counts for the requested period, grouped by category, so you can compare deliverability and engagement between your transactional and marketing traffic. Rows are ranked by the `sort` metric, `processed` by default, and capped at the requested `limit` (50 by default, 200 at most).
+* Returns aggregate delivery and latency stats grouped by message category for the requested period. Rows are ranked by the `sort` metric (default `accepted`) descending and capped at the requested `limit` (default 50, hard maximum 200). Use this to compare sending performance across the categories you send under.
 *
-* Rows are computed against event time rather than send time, so engagement received during the period counts even for messages that were sent earlier.
+* Rows use send-time attribution. A delivery confirmed during the period for a message accepted earlier counts against the earlier period. A recent period therefore under-reports `delivered` while delivery reports are still arriving, and its counts grow as reports arrive.
 *
-* The window can span at most 365 days. Ask for more and you get a 422.
+* The maximum window is 365 days; requesting a longer range returns 422.
 *
 */
-const getEmailStatsByCategory = (options) => (options?.client ?? client).get({
+const getSmsStatsByCategory = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2494,20 +2443,18 @@ const getEmailStatsByCategory = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/categories",
+	url: "/v1/sms/stats/categories",
 	...options
 });
 /**
-* Stats by mailbox provider
-*
-* Returns delivery, engagement, and deliverability counts for the requested period, grouped by recipient mailbox provider, for example `gmail`, `yahoo`, `microsoft`, or `apple`. Use it to compare how each major inbox provider treats your mail, for example to spot a delivered-rate dip or a complaint spike at one provider before it spreads. For a per-region split within a provider, use the mailbox-provider-region breakdown.
+* Get SMS statistics by error code
 *
-* A recipient's mailbox provider is only known once the receiving mail system reports an outcome, so this breakdown covers the delivery stage onward. Accepted, processed, and rejected counts and processing latency are not included. Rows are computed against event time rather than send time.
+* Returns aggregate delivery and latency statistics grouped by normalized failure reason for the requested period. The grouping key matches the `error_code` filter on the message list, so each row maps directly to the affected messages rather than a raw carrier code. Rows are ranked by the `sort` metric (default `failed`) descending and capped at the requested `limit` (default 50, hard maximum 200).
 *
-* Rows are ranked by the `sort` metric, `delivered` by default, and capped at the requested `limit` (50 by default, 200 at most). The window can span at most 365 days. Ask for more and you get a 422.
+* Rows use send-time attribution. A delivery confirmed during the period for a message accepted earlier counts against the earlier period. A recent period therefore under-reports `delivered` while delivery reports are still arriving, and its counts grow as reports arrive. The maximum window is 365 days; requesting a longer range returns 422.
 *
 */
-const getEmailStatsByMailboxProvider = (options) => (options?.client ?? client).get({
+const getSmsStatsByErrorCode = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2516,20 +2463,20 @@ const getEmailStatsByMailboxProvider = (options) => (options?.client ?? client).
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/mailbox-providers",
+	url: "/v1/sms/stats/error-codes",
 	...options
 });
 /**
-* Stats by mailbox provider region
+* Get SMS statistics by carrier
 *
-* Returns delivery, engagement, and deliverability counts for the requested period, grouped by mailbox provider and provider region pair, for example `gmail` in `NA` or `microsoft` in `EU`. The provider region is the regional grouping the receiving mail system reports for the recipient's provider. Pairing it with the provider tells apart a region label that several providers share. Use it to spot a deliverability problem isolated to one provider in one region. For a per-provider view without the region split, use the mailbox-provider breakdown.
+* Returns aggregate delivery and latency stats grouped by delivery carrier for the requested period. Rows are ranked by the `sort` metric (default `accepted`) descending and capped at the requested `limit` (default 50, hard maximum 200). Use this to compare delivery performance across the carriers that handled your messages.
 *
-* A provider region is only known once the receiving mail system reports an outcome, so this breakdown covers the delivery stage onward. Accepted, processed, and rejected counts and processing latency are not included. Rows are computed against event time rather than send time.
+* Rows use send-time attribution. A delivery confirmed during the period for a message accepted earlier counts against the earlier period. A recent period therefore under-reports `delivered` while delivery reports are still arriving, and its counts grow as reports arrive.
 *
-* Rows are ranked by the `sort` metric, `delivered` by default, and capped at the requested `limit` (50 by default, 200 at most). The window can span at most 365 days. Ask for more and you get a 422.
+* The maximum window is 365 days; requesting a longer range returns 422.
 *
 */
-const getEmailStatsByMailboxProviderRegion = (options) => (options?.client ?? client).get({
+const getSmsStatsByCarrier = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2538,20 +2485,20 @@ const getEmailStatsByMailboxProviderRegion = (options) => (options?.client ?? cl
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/mailbox-provider-regions",
+	url: "/v1/sms/stats/carriers",
 	...options
 });
 /**
-* Stats by recipient domain
+* Get SMS statistics by tag
 *
-* Returns delivery and engagement counts for the requested period, grouped by recipient mailbox domain: the part of each recipient address after the `@`, for example `gmail.com`, `yahoo.com`, or `outlook.com`. This is the finest-grained deliverability view. Where the mailbox-provider breakdown groups recipients into provider buckets such as `gmail` or `microsoft`, this keys on the exact destination domain. Use it to spot a delivery-rate dip or a complaint spike at a specific domain.
+* Returns delivery and latency statistics grouped by tag (`name:value`). Rows sort by the selected metric in descending order and are capped by `limit`. The default sort is `accepted`; the default limit is 50 and the maximum is 200.
 *
-* Rows are ranked by the `sort` metric, `processed` by default, and capped at the requested `limit` (50 by default, 200 at most). Rows are computed against event time rather than send time, so engagement received during the period counts even for messages that were sent earlier.
+* Only tagged messages appear. A message with several tags is counted once under each, so rows do not sum to the period total.
 *
-* The window can span at most 365 days. Ask for more and you get a 422.
+* Rows use send-time attribution, so recent periods can under-report `delivered` while delivery reports arrive. A request may span up to 365 days; a longer window returns `422`.
 *
 */
-const getEmailStatsByRecipientDomain = (options) => (options?.client ?? client).get({
+const getSmsStatsByTag = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2560,20 +2507,20 @@ const getEmailStatsByRecipientDomain = (options) => (options?.client ?? client).
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/recipient-domains",
+	url: "/v1/sms/stats/tags",
 	...options
 });
 /**
-* Stats by template
+* Get SMS statistics by status
 *
-* Returns aggregate delivery and engagement counts grouped by the template each message was sent with, so a template's deliverability and engagement can be compared side by side. Attribution is by the template used at send time; only messages sent with a template appear here, so a workspace that has sent none returns an empty list rather than an error. Each row is keyed by the template ID (`emt_…`); a template deleted after sending still appears by its ID.
+* Returns one row per lifecycle status with activity in the requested period, ordered by count descending. The statuses are `accepted`, `sent`, `delivered`, `undelivered`, `failed`, `rejected`, and `expired`.
 *
-* Rows are ranked by the `sort` metric (default `processed`) descending and capped at the requested `limit` (default 50, hard maximum 200). Rows are computed against event time (not send time), so engagement received during the period for messages sent earlier is included.
+* Rows use send-time attribution. A delivery confirmed during the period for a message accepted earlier counts against the earlier period. A recent period therefore under-reports `delivered` while delivery reports are still arriving. With at most seven statuses, this breakdown has no cap, ranking, limit, or trend parameters.
 *
 * The maximum window is 365 days; requesting a longer range returns 422.
 *
 */
-const getEmailStatsByTemplate = (options) => (options?.client ?? client).get({
+const getSmsStatsByStatus = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2582,20 +2529,20 @@ const getEmailStatsByTemplate = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/templates",
+	url: "/v1/sms/stats/statuses",
 	...options
 });
 /**
-* Engagement by location
+* Get a received-message summary
 *
-* Returns engagement counts (opens and clicks) for the requested period, grouped by the location they were recorded from. Use it to see where your audience engages, for example the top countries by unique opens. The reading location is only known from open and click events, so rows have engagement counts but no delivery counts or rates.
+* Returns the total number of messages your numbers received over the period, using the time the carrier received each message.
 *
-* Use `group_by` to choose the granularity: `country` (the default), `region`, or `city`. Each row has the location hierarchy down to the requested level, so a `city` grouping also reports that row's region and country. Rows are ranked by the `sort` metric, `unique_opens` by default, and capped at the requested `limit` (50 by default, 200 at most).
+* The response contains only a count because a received message has one state. Use the send statistics endpoints for delivery rates and latency data about messages you send.
 *
-* Rows are computed against event time rather than send time. The window can span at most 365 days. Ask for more and you get a 422.
+* The maximum window is 365 days; a longer range returns 422. Set `timezone` to resolve the period against your local calendar instead of UTC.
 *
 */
-const getEmailStatsByLocation = (options) => (options?.client ?? client).get({
+const getSmsInboundStatsSummary = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2604,20 +2551,20 @@ const getEmailStatsByLocation = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/locations",
+	url: "/v1/sms/stats/inbound/summary",
 	...options
 });
 /**
-* Engagement by email client
+* Get daily received-message counts
 *
-* Returns engagement counts (opens and clicks) for the requested period, grouped by the email client, operating system, or device type they were recorded from. Use it for the classic view of opens by mail client, for example the share of opens from Apple Mail compared with Gmail and Outlook. The reading environment is only known from open and click events, so rows have engagement counts but no delivery counts or rates.
+* Returns the number of messages your numbers received, one row per calendar day. Rows use the time the carrier received each message, and days with no messages contain a zero count.
 *
-* Use `group_by` to choose the facet: `email_client` (the default), `os`, or `device_type`. Each row fills in the facet you chose and leaves the other two null. Rows are ranked by the `sort` metric, `unique_opens` by default, and capped at the requested `limit` (50 by default, 200 at most).
+* Each row contains only a count because a received message has one state. Use the send statistics endpoints for lifecycle and delivery-latency data about messages you send.
 *
-* Rows are computed against event time rather than send time. The window can span at most 365 days. Ask for more and you get a 422.
+* The maximum window is 365 days; a longer range returns 422. Set `timezone` to bucket rows by your local calendar day instead of UTC.
 *
 */
-const getEmailStatsByClient = (options) => (options?.client ?? client).get({
+const getSmsInboundStatsDaily = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2626,20 +2573,20 @@ const getEmailStatsByClient = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/clients",
+	url: "/v1/sms/stats/inbound/daily",
 	...options
 });
 /**
-* Bounces by SMTP error code
+* Get hourly received-message counts
 *
-* Returns bounce counts for the requested period, grouped by the SMTP error code the receiving mail server returned. It answers the question of which SMTP responses are driving your bounces. Each row reports how many recipients bounced with that code, plus the hard, soft, admin, block, and undetermined split for that code.
+* Returns the number of messages your numbers received, one row per hour. Rows use the time the carrier received each message, and hours with no messages contain a zero count.
 *
-* This breakdown only covers the failure side. There are no delivered, open, click, or rate fields, because a bounce code is only ever recorded on a bounce event.
+* Each row contains only a count because a received message has one state. Use the send statistics endpoints for lifecycle and delivery-latency data about messages you send.
 *
-* Rows are ranked by the `sort` metric, `bounced` by default, and capped at the requested `limit` (50 by default, 200 at most). They are computed against event time rather than send time. The window can span at most 365 days. Ask for more and you get a 422.
+* The maximum window is 720 hours; a longer range returns 422. Set `timezone` to bucket rows by your local hour instead of UTC.
 *
 */
-const getEmailStatsByBounceCode = (options) => (options?.client ?? client).get({
+const getSmsInboundStatsHourly = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2648,20 +2595,18 @@ const getEmailStatsByBounceCode = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/bounce-codes",
+	url: "/v1/sms/stats/inbound/hourly",
 	...options
 });
 /**
-* Complaints by type
-*
-* Returns spam-complaint counts for the requested period, grouped by the feedback-loop complaint type the mailbox provider reported, for example `abuse`, `fraud`, or `virus`. Use it to see what kind of complaints your mail attracts.
+* Get received messages by country
 *
-* This breakdown only covers the complaint side. Each row has the complained count for one type and nothing else, because a complaint type is only ever recorded on a spam-complaint event.
+* Returns the number of messages your numbers received, grouped by the receiving number's country. Rows are ranked by volume, highest first, and use the time the carrier received each message.
 *
-* Rows are ranked by `complained` descending, and capped at the requested `limit` (default 50, hard maximum 200). They are computed against event time rather than send time. The window can span at most 365 days. Ask for more and you get a 422.
+* Each row contains only a count because a received message has one state. The maximum window is 365 days; a longer range returns `422`. Set `timezone` to resolve the period against your local calendar.
 *
 */
-const getEmailStatsByComplaintType = (options) => (options?.client ?? client).get({
+const getSmsInboundStatsByCountry = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2670,20 +2615,20 @@ const getEmailStatsByComplaintType = (options) => (options?.client ?? client).ge
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/complaint-types",
+	url: "/v1/sms/stats/inbound/countries",
 	...options
 });
 /**
-* Stats by broadcast
+* Get received messages by operator
 *
-* Returns aggregate delivery and engagement counts grouped by broadcast for the requested period, so each broadcast's deliverability and engagement can be compared side by side. Only messages sent as part of a broadcast appear here. One-off and transactional sends are not included, so a workspace that has not sent broadcasts returns an empty list rather than an error.
+* Returns the number of messages your numbers received, grouped by the sender's mobile operator. Rows are ranked by volume, highest first, and use the time the carrier received each message. Operators are identified by MCC-MNC when the carrier reports it.
 *
-* Rows are ranked by the `sort` metric (default `processed`) descending and capped at the requested `limit` (default 50, hard maximum 200). Rows are computed against event time (not send time), so engagement received during the period for messages sent earlier is included.
+* Each row contains only a count because a received message has one state. Messages without a reported sending operator are excluded, so the rows can sum to less than the summary total.
 *
-* The maximum window is 365 days. Requesting a longer range returns a 422. This breakdown is computed from per-message activity retained for 30 days, so it reflects roughly the last 30 days of activity even when the requested window reaches further back.
+* The maximum window is 365 days; a longer range returns `422`. Set `timezone` to resolve the period against your local calendar.
 *
 */
-const getEmailStatsByBroadcast = (options) => (options?.client ?? client).get({
+const getSmsInboundStatsByOperator = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2692,16 +2637,18 @@ const getEmailStatsByBroadcast = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/stats/broadcasts",
+	url: "/v1/sms/stats/inbound/operators",
 	...options
 });
 /**
-* List sending domains
+* Get received messages by number
 *
-* Returns all sending domains for the current workspace, newest first by default. Each item is the full domain object, including capability statuses and `dns_records`, so no per-domain follow-up read is needed. Filter with `name` to find a specific domain.
+* Returns how many messages each of your numbers received. Rows are ranked by volume, highest first, and use the time the carrier received each message.
+*
+* Each row contains only a count because a received message has one state. The maximum window is 365 days; a longer range returns `422`. Set `timezone` to resolve the period against your local calendar.
 *
 */
-const listDomains = (options) => (options?.client ?? client).get({
+const getSmsInboundStatsByNumber = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2710,29 +2657,18 @@ const listDomains = (options) => (options?.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/domains",
+	url: "/v1/sms/stats/inbound/numbers",
 	...options
 });
 /**
-* Add a sending domain
+* Create a phone number lookup
 *
-* Registers a new sending domain and returns the DNS records to publish
-* for it. The DKIM TXT record proves ownership, and together with the
-* return-path CNAME (which also covers SPF, so no separate SPF record is
-* needed) and a DMARC policy it gates sending. The tracking CNAME is
-* optional and gates branded link tracking only. Publish the records at
-* your DNS provider, then check progress with
-* [Trigger domain verification](/docs/api/reference/verify-domain). Published
-* records are also re-checked for you automatically. Setup walkthrough:
-* [Sending domains](/docs/guides/email/sending-domains).
+* Returns the number's serving and issuing networks, porting state, country, and line type. The baseline fields are included in each lookup. Request additional `type` blocks for classification, presence, roaming, SIM-swap, porting-history, or credibility data. Each block reports its own `status`; only blocks with an `ok` status incur an additional charge.
 *
-* The domain starts in `pending` status. A domain already registered in
-* this workspace returns `409`, and creation beyond your organization's
-* domain quota returns `422` `E10000`. A domain that never verifies
-* ownership is removed after about 14 days, with a reminder email first.
+* This form keeps the number out of the URL. The [URL form](/docs/api/reference/get-phone-number-lookup) performs the same lookup but cannot use an idempotency key. With this form, reuse an `Idempotency-Key` to return the stored result without another lookup or charge.
 *
 */
-const createDomain = (options) => (options.client ?? client).post({
+const createPhoneNumberLookup = (options) => (options.client ?? client).post({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2741,7 +2677,7 @@ const createDomain = (options) => (options.client ?? client).post({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/domains",
+	url: "/v1/lookup/phone-number",
 	...options,
 	headers: {
 		"Content-Type": "application/json",
@@ -2749,12 +2685,14 @@ const createDomain = (options) => (options.client ?? client).post({
 	}
 });
 /**
-* Delete a sending domain
+* Create an email address lookup
 *
-* Removes the domain and revokes its sender authorization. New sends from a deleted domain are rejected. Historical statistics and events for past sends from this domain are preserved.
+* Returns a deliverability `result`, a `delivery_confidence` score, address characteristics, an undeliverable `reason`, and a suggested correction when available. `result` and `reason` are open vocabularies. Handle unknown values and use `delivery_confidence` as the stable fallback. Each completed lookup incurs the same charge regardless of its result.
+*
+* This form keeps the address out of the URL. The [URL form](/docs/api/reference/get-email-lookup) performs the same lookup but cannot use an idempotency key. With this form, reuse an `Idempotency-Key` to return the stored result without another lookup or charge.
 *
 */
-const deleteDomain = (options) => (options.client ?? client).delete({
+const createEmailLookup = (options) => (options.client ?? client).post({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2763,16 +2701,24 @@ const deleteDomain = (options) => (options.client ?? client).delete({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/domains/{domain_id}",
-	...options
+	url: "/v1/lookup/email",
+	...options,
+	headers: {
+		"Content-Type": "application/json",
+		...options.headers
+	}
 });
 /**
-* Get a sending domain
+* Create a verification
 *
-* Returns the domain with its capability statuses and every DNS record's current verification state. This read reports the stored result of the last check. To run a fresh DNS check, use [Trigger domain verification](/docs/api/reference/verify-domain).
+* Creates a verification and sends the recipient a one-time passcode. Provide an email address, a phone number, or both in `to`. The service sends over one channel at a time and moves to the next planned channel if delivery fails.
+*
+* Calling this again for the same recipient reuses the verification in progress. During the resend cooldown, it returns the current state without sending. After the cooldown, it sends a fresh passcode.
+*
+* The `200` response contains the current state, never the passcode. Submit the recipient's passcode with [Check a verification](/docs/api/reference/create-verification-check) before `expires_at`. An invalid recipient returns `422`; exceeding the send rate limit returns `429`.
 *
 */
-const getDomain = (options) => (options.client ?? client).get({
+const createVerification = (options) => (options.client ?? client).post({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2781,27 +2727,27 @@ const getDomain = (options) => (options.client ?? client).get({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/domains/{domain_id}",
-	...options
+	url: "/v1/verify/verifications",
+	...options,
+	headers: {
+		"Content-Type": "application/json",
+		...options.headers
+	}
 });
 /**
-* Update a sending domain
+* Create a verification passcode check
 *
-* Updates settings and configuration on a sending domain. `settings`
-* changes apply immediately. Changes to `return_path`, `tracking`, or
-* `dkim` on a verified capability are staged: the current configuration
-* keeps serving until the new one's DNS records verify, then the change
-* is promoted automatically. Staged values are visible under
-* `capabilities.*.pending`. The records to publish appear in
-* `dns_records` with `state: pending`.
+* Checks a passcode for a recipient and returns the outcome together with the verification's current state. Identify the verification by the same `to` used to create it; you do not need to store a verification ID.
 *
-* Invalid combinations are rejected. Enabling tracking toggles without a
-* tracking domain, or removing the tracking domain while a toggle is on,
-* returns `409`. Enabling inbound receiving has verification
-* prerequisites that return `422`. Each rule is detailed on its field.
+* A wrong or expired passcode returns `200 OK` with `success: false` and a `reason` such as `incorrect_code` or `expired`. `success: true` means the verification is complete. Each verification reports its final outcome once and cannot be checked again.
+*
+* An error status is returned only when the check cannot be evaluated. A `404`
+* means no verification matches the recipient or the matching one already
+* reached its final state. A `422` indicates an invalid recipient. A `429`
+* means passcodes for a recipient are being checked too quickly.
 *
 */
-const updateDomain = (options) => (options.client ?? client).patch({
+const createVerificationCheck = (options) => (options.client ?? client).post({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2810,7 +2756,7 @@ const updateDomain = (options) => (options.client ?? client).patch({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/domains/{domain_id}",
+	url: "/v1/verify/verifications/check",
 	...options,
 	headers: {
 		"Content-Type": "application/json",
@@ -2818,22 +2764,16 @@ const updateDomain = (options) => (options.client ?? client).patch({
 	}
 });
 /**
-* Trigger domain verification
+* Create the next verification channel attempt
 *
-* Runs a fresh DNS check across the domain's records (DKIM, return path,
-* DMARC, tracking, inbound MX, and any staged changes) and returns the
-* updated domain. Use it for an immediate result after publishing or
-* correcting records. [Get a sending domain](/docs/api/reference/get-domain)
-* only reports the last stored result. Published records are also re-checked
-* for you automatically in the background.
+* Advances an in-progress verification to the next channel in its plan and sends a fresh passcode there. Identify the verification by the same `to` recipient used to create it; no verification ID is required.
 *
-* A `200` with records still `pending` is not a failure: the records were
-* not found yet, which is normal while DNS propagates (minutes to hours).
-* Recently verified records are not re-queried, so the call is safe to
-* repeat while you wait.
+* The send bypasses the resend cooldown, and passcodes sent earlier remain valid. The response sets `last_channel` to the most recent completed send. Concurrent requests each advance the plan by at most one channel and return committed state.
+*
+* A missing in-progress verification returns `404`. A plan with no further channel returns `422 NoNextChannel`; create the verification again to resend on the current channel. If every remaining channel fails, the operation returns `422 NoAvailableChannel`. Requests that exceed the send rate limit return `429`.
 *
 */
-const verifyDomain = (options) => (options.client ?? client).post({
+const createVerificationNextChannel = (options) => (options.client ?? client).post({
 	security: [{
 		scheme: "bearer",
 		type: "http"
@@ -2842,15 +2782,644 @@ const verifyDomain = (options) => (options.client ?? client).post({
 		name: "bird_session",
 		type: "apiKey"
 	}],
-	url: "/v1/email/domains/{domain_id}/verify",
-	...options
+	url: "/v1/verify/verifications/next-channel",
+	...options,
+	headers: {
+		"Content-Type": "application/json",
+		...options.headers
+	}
 });
 /**
-* List mailboxes
-*
-* Returns a paginated list of the workspace's mailboxes, newest first. Search across addresses and display names with `q`, look a mailbox up by its exact address, or filter by lifecycle state or domain.
+* List WhatsApp messages
 *
-*/
+* Returns the workspace's WhatsApp messages as a cursor-paginated list,
+* newest first, outbound and inbound alike. Each message carries the one
+* content object it was built from: `template`, or free-form `text`,
+* `image`, `video`, `audio`, `sticker`, `document` or `location`. An inbound
+* message whose content WhatsApp models and we do not carries `unsupported`
+* instead, naming the type rather than reading back empty.
+* Filter by direction, status, contact phone number,
+* business-scoped user ID, template category, tag, or creation time; pass the response's `next_cursor` back as
+* `starting_after` to fetch the next page. To follow a single message's
+* delivery, use
+* [Get a WhatsApp message](/docs/api/reference/get-whatsapp-message)
+* instead.
+*
+* Messages are retained for **30 days**. A `created_after` earlier than that
+* is accepted and raised to the retention bound rather than rejected, so a
+* wider window returns what is still retained instead of failing. There is no
+* way to read messages older than the window.
+*
+*/
+const listWhatsAppMessages = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/whatsapp/messages",
+	...options
+});
+/**
+* Send a WhatsApp message
+*
+* Sends one WhatsApp message to one recipient. The request carries exactly one
+* kind of content: a message template, or free-form `text`, `image`, `video`,
+* `audio`, `sticker`, `document` or `location`. A request carrying none is
+* rejected with a `422`, and one carrying more than one is too.
+*
+* A **template** is the only content WhatsApp delivers outside an open
+* customer service window, so it is what starts a conversation. Name the
+* template, optionally pick its language variant, and fill its placeholders in
+* `components`. A Bird-managed template selects its sender number from its
+* category, so the request carries no `from`; a template your workspace
+* authored requires one. Browse your workspace's templates in the Bird
+* dashboard.
+*
+* **Free-form content** is deliverable only inside an open 24-hour customer
+* service window, which the contact opens by messaging or calling you and
+* resets each time they do it again. We do not track the window, so a send
+* outside one is accepted and then fails, carrying `service_window_expired` on
+* the message's `last_error`. Every free-form send requires `from`.
+*
+* The `202` response is the accepted message, echoing the resolved content; it
+* is not a delivery confirmation. Follow delivery with
+* [Get a WhatsApp message](/docs/api/reference/get-whatsapp-message), the
+* per-message timeline from
+* [List events for a WhatsApp message](/docs/api/reference/list-whatsapp-message-events),
+* or `whatsapp.*` webhook events.
+*
+* Each of these returns a `422`:
+*
+* - A template slug or language the catalogue does not stock.
+* - Parameter values that do not match the template's declared placeholders.
+* - A `from` this workspace cannot send from.
+* - A recipient that is neither a valid phone number nor a business-scoped user ID.
+*
+*/
+const createWhatsAppMessage = (options) => (options.client ?? client).post({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/whatsapp/messages",
+	...options,
+	headers: {
+		"Content-Type": "application/json",
+		...options.headers
+	}
+});
+/**
+* Get a WhatsApp message
+*
+* Returns a single WhatsApp message: its current delivery status, per-stage timestamps (`sent_at`, `delivered_at`, `read_at`), and failure detail when it failed. It carries the one content object it was built from: `template`, or free-form `text`, `image`, `video`, `audio`, `sticker`, `document` or `location`. An inbound message whose content WhatsApp models and we do not carries `unsupported` instead, naming the type rather than reading back empty. The `status` advances asynchronously as delivery progresses, so poll this endpoint (or subscribe to `whatsapp.*` webhook events) after a send to confirm delivery. For the per-event timeline, use [List events for a WhatsApp message](/docs/api/reference/list-whatsapp-message-events) instead.
+*
+*/
+const getWhatsAppMessage = (options) => (options.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/whatsapp/messages/{message_id}",
+	...options
+});
+/**
+* List events for a WhatsApp message
+*
+* Returns a WhatsApp message's lifecycle events in chronological order, one entry per delivery transition (`whatsapp.accepted`, `whatsapp.sent`, `whatsapp.delivered`, `whatsapp.read`, `whatsapp.failed`). The timeline is bounded and returned in full, so this list is not paginated; an unknown message ID returns `404`. For the message's current state in a single field, use [Get a WhatsApp message](/docs/api/reference/get-whatsapp-message) instead.
+*
+*/
+const listWhatsAppMessageEvents = (options) => (options.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/whatsapp/messages/{message_id}/events",
+	...options
+});
+/**
+* Get daily sending statistics
+*
+* Returns one row of aggregate sending statistics per calendar day for the workspace: UTC days by default, or your local days when `timezone` is set. Days with no activity are included with zero counts, so the series charts without client-side gap handling. Suited to charts and trend lines; for per-message exact accounting use the message detail endpoints.
+*
+* Rows use event time. For example, a complaint received on Wednesday for a message sent the prior Monday is counted in Wednesday's row.
+*
+* The maximum window is 365 days; requesting a longer range returns `422`.
+*
+*/
+const getEmailStatsDaily = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/daily",
+	...options
+});
+/**
+* Get hourly sending statistics
+*
+* Returns one row of aggregate sending statistics per hour for the workspace: UTC hours by default, or your local hours when `timezone` is set (a timezone with a sub-hour offset gets correctly aligned hours). Useful for inspecting send rate, deliverability, and engagement inside a single day or a recent window; hours with no activity are included with zero counts.
+*
+* Rows use event time. For example, a click recorded at 14:07 for a message sent at 09:00 lands in the 14:00 row.
+*
+* A single request may span at most 30 days (720 hourly rows); for longer ranges use the daily endpoint, which has a 365-day window. An hourly window longer than 30 days, or a `from` after `to`, returns `422`.
+*
+*/
+const getEmailStatsHourly = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/hourly",
+	...options
+});
+/**
+* Get statistics by tag
+*
+* Returns delivery and engagement counts for the requested period, grouped by tag. Use it to compare performance across the tags you set at send time. Rows are ranked by the `sort` metric, `processed` by default, and capped at the requested `limit` (50 by default, 200 at most).
+*
+* Rows are computed against event time rather than send time, so engagement received during the period counts even for messages that were sent earlier.
+*
+* The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsByTag = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/tags",
+	...options
+});
+/**
+* Get aggregate email statistics
+*
+* Returns a single-row aggregate across the requested period covering delivery, bounce, complaint, open, and click counts plus the derived rates, along with processing, delivery, and total latency percentiles (p50/p95/p99). Suitable for KPI tiles, campaign reports, and email digests; the daily and hourly endpoints have the same metrics per time bucket.
+*
+* The aggregate is computed against event time (not send time), so engagement received during the period for messages sent earlier is included. Rate fields are `null` when their denominator is zero.
+*
+* The window grain follows the form of `from` and `to`: calendar days (`YYYY-MM-DD`, up to 365 days) or RFC 3339 instants (hour grain, up to 720 hours, 30 days). A rolling window such as the last 24 hours is a single request. Mixing the two forms returns `422`. Set `timezone` to compute day and hour boundaries in a local zone instead of UTC, and `compare=previous_period` to include the preceding equal-length window in the same response.
+*
+*/
+const getEmailStatsSummary = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/summary",
+	...options
+});
+/**
+* Get statistics by sending IP
+*
+* Returns delivery and deliverability counts for the requested period, grouped by the specific IP address used to send each message. Use it to spot a reputation problem on one IP. Block bounces concentrated on a single IP usually mean that IP's reputation has taken a hit, and sorting by `bounces.block` puts those IPs first.
+*
+* A sending IP is only known once the receiving mail server reports an outcome: a delivery, a bounce, a deferral, or a late bounce. So this breakdown starts from the delivery stage onward. Accepted, processed, and rejected counts aren't included at all, and neither are engagement counts or processing latency. Complaints and out-of-band bounces aren't attributed to a sending IP either, so `complained` and `oob_bounces` are included but always read `0` here. Bounced, deferred, delivery latency, and total latency are the ones that have real numbers. For workspace-wide figures, use `GET /v1/email/stats/daily`. Rows are computed against event time rather than send time.
+*
+* Rows are ranked by the `sort` field, `delivered` by default, and capped at the requested `limit` (50 by default, 200 at most). The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsBySendingIp = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/sending-ips",
+	...options
+});
+/**
+* Get statistics by sending domain
+*
+* Returns delivery, engagement, and deliverability counts for the requested period, grouped by sending domain: the portion of the `From` address after the `@`. Use it to compare deliverability across multiple verified domains in your workspace, for example transactional versus marketing domains, or sub-domain segregation during IP warming.
+*
+* Rows are computed against event time rather than send time, so engagement and bounces received during the period count even for messages that were sent earlier.
+*
+* Rows are ranked by the `sort` metric, `processed` by default, and capped at the requested `limit` (50 by default, 200 at most). The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsBySendingDomain = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/sending-domains",
+	...options
+});
+/**
+* Get statistics by category
+*
+* Returns delivery and engagement counts for the requested period, grouped by category, so you can compare deliverability and engagement between your transactional and marketing traffic. Rows are ranked by the `sort` metric, `processed` by default, and capped at the requested `limit` (50 by default, 200 at most).
+*
+* Rows are computed against event time rather than send time, so engagement received during the period counts even for messages that were sent earlier.
+*
+* The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsByCategory = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/categories",
+	...options
+});
+/**
+* Get statistics by mailbox provider
+*
+* Returns delivery, engagement, and deliverability counts for the requested period, grouped by recipient mailbox provider, for example `gmail`, `yahoo`, `microsoft`, or `apple`. Use it to compare how each major inbox provider treats your mail, for example to spot a delivered-rate dip or a complaint spike at one provider before it spreads. For a per-region split within a provider, use the mailbox-provider-region breakdown.
+*
+* A recipient's mailbox provider is only known once the receiving mail system reports an outcome, so this breakdown covers the delivery stage onward. Accepted, processed, and rejected counts and processing latency are not included. Rows are computed against event time rather than send time.
+*
+* Rows are ranked by the `sort` metric, `delivered` by default, and capped at the requested `limit` (50 by default, 200 at most). The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsByMailboxProvider = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/mailbox-providers",
+	...options
+});
+/**
+* Get statistics by mailbox provider region
+*
+* Returns delivery, engagement, and deliverability counts for the requested period, grouped by mailbox provider and provider region pair, for example `gmail` in `NA` or `microsoft` in `EU`. The provider region is the regional grouping the receiving mail system reports for the recipient's provider. Pairing it with the provider tells apart a region label that several providers share. Use it to spot a deliverability problem isolated to one provider in one region. For a per-provider view without the region split, use the mailbox-provider breakdown.
+*
+* A provider region is only known once the receiving mail system reports an outcome, so this breakdown covers the delivery stage onward. Accepted, processed, and rejected counts and processing latency are not included. Rows are computed against event time rather than send time.
+*
+* Rows are ranked by the `sort` metric, `delivered` by default, and capped at the requested `limit` (50 by default, 200 at most). The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsByMailboxProviderRegion = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/mailbox-provider-regions",
+	...options
+});
+/**
+* Get statistics by recipient domain
+*
+* Returns delivery and engagement counts for the requested period, grouped by recipient mailbox domain: the part of each recipient address after the `@`, for example `gmail.com`, `yahoo.com`, or `outlook.com`. This is the finest-grained deliverability view. Where the mailbox-provider breakdown groups recipients into provider buckets such as `gmail` or `microsoft`, this keys on the exact destination domain. Use it to spot a delivery-rate dip or a complaint spike at a specific domain.
+*
+* Rows are ranked by the `sort` metric, `processed` by default, and capped at the requested `limit` (50 by default, 200 at most). Rows are computed against event time rather than send time, so engagement received during the period counts even for messages that were sent earlier.
+*
+* The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsByRecipientDomain = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/recipient-domains",
+	...options
+});
+/**
+* Get statistics by template
+*
+* Returns aggregate delivery and engagement counts grouped by the template each message was sent with, so a template's deliverability and engagement can be compared side by side. Attribution is by the template used at send time; only messages sent with a template appear here, so a workspace that has sent none returns an empty list rather than an error. Each row is keyed by the template ID (`emt_…`); a template deleted after sending still appears by its ID.
+*
+* Rows are ranked by the `sort` metric (default `processed`) descending and capped at the requested `limit` (default 50, hard maximum 200). Rows are computed against event time (not send time), so engagement received during the period for messages sent earlier is included.
+*
+* The maximum window is 365 days; requesting a longer range returns `422`.
+*
+*/
+const getEmailStatsByTemplate = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/templates",
+	...options
+});
+/**
+* Get engagement by location
+*
+* Returns engagement counts (opens and clicks) for the requested period, grouped by the location they were recorded from. Use it to see where your audience engages, for example the top countries by unique opens. The reading location is only known from open and click events, so rows have engagement counts but no delivery counts or rates.
+*
+* Use `group_by` to choose the granularity: `country` (the default), `region`, or `city`. Each row has the location hierarchy down to the requested level, so a `city` grouping also reports that row's region and country. Rows are ranked by the `sort` metric, `unique_opens` by default, and capped at the requested `limit` (50 by default, 200 at most).
+*
+* Rows are computed against event time rather than send time. The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsByLocation = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/locations",
+	...options
+});
+/**
+* Get engagement by email client
+*
+* Returns engagement counts (opens and clicks) for the requested period, grouped by the email client, operating system, or device type they were recorded from. Use it for the classic view of opens by mail client, for example the share of opens from Apple Mail compared with Gmail and Outlook. The reading environment is only known from open and click events, so rows have engagement counts but no delivery counts or rates.
+*
+* Use `group_by` to choose the facet: `email_client` (the default), `os`, or `device_type`. Each row fills in the facet you chose and leaves the other two `null`. Rows are ranked by the `sort` metric, `unique_opens` by default, and capped at the requested `limit` (50 by default, 200 at most).
+*
+* Rows are computed against event time rather than send time. The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsByClient = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/clients",
+	...options
+});
+/**
+* Get bounces by SMTP error code
+*
+* Returns bounce counts for the requested period, grouped by the SMTP error code the receiving mail server returned. It answers the question of which SMTP responses are driving your bounces. Each row reports how many recipients bounced with that code, plus the hard, soft, admin, block, and undetermined split for that code.
+*
+* This failure-only breakdown omits delivered, open, click, and rate fields because bounce codes occur only on bounce events.
+*
+* Rows are ranked by the `sort` metric, `bounced` by default, and capped at the requested `limit` (50 by default, 200 at most). They are computed against event time rather than send time. The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsByBounceCode = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/bounce-codes",
+	...options
+});
+/**
+* Get complaints by type
+*
+* Returns spam-complaint counts for the requested period, grouped by the feedback-loop complaint type the mailbox provider reported, for example `abuse`, `fraud`, or `virus`. Use it to see what kind of complaints your mail attracts.
+*
+* This breakdown only covers the complaint side. Each row has the complained count for one type and nothing else, because a complaint type is only ever recorded on a spam-complaint event.
+*
+* Rows are ranked by `complained` descending, and capped at the requested `limit` (default 50, hard maximum 200). They are computed against event time rather than send time. The window can span at most 365 days. Ask for more and you get a `422`.
+*
+*/
+const getEmailStatsByComplaintType = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/complaint-types",
+	...options
+});
+/**
+* Get statistics by broadcast
+*
+* Returns aggregate delivery and engagement counts grouped by broadcast for the requested period, so each broadcast's deliverability and engagement can be compared side by side. Only messages sent as part of a broadcast appear here. One-off and transactional sends are not included, so a workspace that has not sent broadcasts returns an empty list rather than an error.
+*
+* Rows are ranked by the `sort` metric (default `processed`) descending and capped at the requested `limit` (default 50, hard maximum 200). Rows are computed against event time (not send time), so engagement received during the period for messages sent earlier is included.
+*
+* The maximum window is 365 days. Requesting a longer range returns a `422`. This breakdown is computed from per-message activity retained for 30 days, so it reflects roughly the last 30 days of activity even when the requested window reaches further back.
+*
+*/
+const getEmailStatsByBroadcast = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/stats/broadcasts",
+	...options
+});
+/**
+* List sending domains
+*
+* Returns all sending domains for the current workspace, newest first by default. Each item is the full domain object, including capability statuses and `dns_records`, so no per-domain follow-up read is needed. Filter with `name` to find a specific domain.
+*
+*/
+const listDomains = (options) => (options?.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/domains",
+	...options
+});
+/**
+* Create a sending domain
+*
+* Registers a new sending domain and returns the DNS records to publish
+* for it. The DKIM TXT record proves ownership, and together with the
+* return-path CNAME (which also covers SPF, so no separate SPF record is
+* needed) and a DMARC policy it gates sending. The tracking CNAME is
+* optional and gates branded link tracking only. Publish the records at
+* your DNS provider, then check progress with
+* [Trigger domain verification](/docs/api/reference/verify-domain). Published
+* records are also re-checked for you automatically. Setup walkthrough:
+* [Sending domains](/docs/guides/email/sending-domains).
+*
+* The domain starts in `pending` status. A domain already registered in
+* this workspace returns `409`, and creation beyond your organization's
+* domain quota returns `422` `E10000`. A domain that never verifies
+* ownership is removed after about 14 days, with a reminder email first.
+*
+*/
+const createDomain = (options) => (options.client ?? client).post({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/domains",
+	...options,
+	headers: {
+		"Content-Type": "application/json",
+		...options.headers
+	}
+});
+/**
+* Delete a sending domain
+*
+* Removes the domain and revokes its sender authorization. New sends from a deleted domain are rejected. Historical statistics and events for past sends from this domain are preserved.
+*
+*/
+const deleteDomain = (options) => (options.client ?? client).delete({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/domains/{domain_id}",
+	...options
+});
+/**
+* Get a sending domain
+*
+* Returns the domain with its capability statuses and every DNS record's current verification state. This read reports the stored result of the last check. To run a fresh DNS check, use [Trigger domain verification](/docs/api/reference/verify-domain).
+*
+*/
+const getDomain = (options) => (options.client ?? client).get({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/domains/{domain_id}",
+	...options
+});
+/**
+* Update a sending domain
+*
+* Updates settings and configuration on a sending domain. `settings`
+* changes apply immediately. Changes to `return_path`, `tracking`, or
+* `dkim` on a verified capability are staged: the current configuration
+* keeps serving until the new one's DNS records verify, then the change
+* is promoted automatically. Staged values are visible under
+* `capabilities.*.pending`. The records to publish appear in
+* `dns_records` with `state: pending`.
+*
+* Invalid combinations are rejected. Enabling tracking toggles without a
+* tracking domain, or removing the tracking domain while a toggle is on,
+* returns `409`. Enabling inbound receiving has verification
+* prerequisites that return `422`. Each rule is detailed on its field.
+*
+*/
+const updateDomain = (options) => (options.client ?? client).patch({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/domains/{domain_id}",
+	...options,
+	headers: {
+		"Content-Type": "application/json",
+		...options.headers
+	}
+});
+/**
+* Verify a domain
+*
+* Runs a fresh DNS check across the domain's records (DKIM, return path,
+* DMARC, tracking, inbound MX, and any staged changes) and returns the
+* updated domain. Use it for an immediate result after publishing or
+* correcting records. [Get a sending domain](/docs/api/reference/get-domain)
+* only reports the last stored result. Published records are also re-checked
+* for you automatically in the background.
+*
+* A `200` with records still `pending` is not a failure: the records were
+* not found yet, which is normal while DNS propagates (minutes to hours).
+* Recently verified records are not re-queried, so the call is safe to
+* repeat while you wait.
+*
+*/
+const verifyDomain = (options) => (options.client ?? client).post({
+	security: [{
+		scheme: "bearer",
+		type: "http"
+	}, {
+		in: "cookie",
+		name: "bird_session",
+		type: "apiKey"
+	}],
+	url: "/v1/email/domains/{domain_id}/verify",
+	...options
+});
+/**
+* List mailboxes
+*
+* Returns a paginated list of the workspace's mailboxes, newest first. Search across addresses and display names with `q`, look a mailbox up by its exact address, or filter by lifecycle state or domain.
+*
+*/
 const listMailboxes = (options) => (options?.client ?? client).get({
 	security: [{
 		scheme: "bearer",
@@ -2866,7 +3435,7 @@ const listMailboxes = (options) => (options?.client ?? client).get({
 /**
 * Create a mailbox
 *
-* Creates a mailbox. The address is `local_part@domain`. The domain defaults to `inbox.ai`, our shared mailbox domain, where creating the mailbox claims the address for your organization. It is first come, first served, and reserved to your organization even after the mailbox is deleted. You may instead name one of your own domains that is enabled for receiving email. An omitted local part is generated. On a custom domain, addresses of deleted mailboxes are quarantined. The same workspace can rebind one 30 days after deletion, but other workspaces never can.
+* Creates a mailbox. The address is `local_part@domain`. The domain defaults to `inbox.ai`, Bird's shared mailbox domain, where creating the mailbox claims the address for your organization. It is first come, first served, and reserved to your organization even after the mailbox is deleted. You may instead name one of your own domains that is enabled for receiving email. An omitted local part is generated. On a custom domain, addresses of deleted mailboxes are quarantined. The same workspace can rebind one 30 days after deletion, but other workspaces never can.
 *
 */
 const createMailbox = (options) => (options.client ?? client).post({
@@ -2906,7 +3475,7 @@ const deleteMailbox = (options) => (options.client ?? client).delete({
 /**
 * Get a mailbox
 *
-* Returns a single mailbox by ID. A mailbox deleted within its 30-day restore window is still returned, with a non-null `deleted_at`. Once the window closes it is permanently removed and returns 404.
+* Returns a single mailbox by ID. A mailbox deleted within its 30-day restore window is still returned, with `deleted_at` set. Once the window closes it is permanently removed and returns `404`.
 *
 */
 const getMailbox = (options) => (options.client ?? client).get({
@@ -2924,7 +3493,7 @@ const getMailbox = (options) => (options.client ?? client).get({
 /**
 * Update a mailbox
 *
-* Updates a mailbox. The address and domain are immutable. Lowering the retention tier deletes any remembered message older than the new cutoff, so that request needs `confirm=true` before it will run.
+* Updates a mailbox. The address and domain are immutable. Lowering the retention tier deletes any remembered message older than the new cutoff, so the request requires `confirm=true`.
 *
 */
 const updateMailbox = (options) => (options.client ?? client).patch({
@@ -2946,7 +3515,7 @@ const updateMailbox = (options) => (options.client ?? client).patch({
 /**
 * Restore a deleted mailbox
 *
-* Restores a mailbox deleted less than 30 days ago. The address is bound back to the mailbox and starts receiving again, and the remembered messages and conversations are available as before the delete. Once the 30-day window has passed the mailbox and its messages are permanently deleted and can no longer be restored (404). Restoring a mailbox that is not deleted returns a conflict, as does an address that is no longer available.
+* Restores a mailbox deleted less than 30 days ago. The address is bound back to the mailbox and starts receiving again, and the remembered messages and conversations are available as before the delete. Once the 30-day window has passed the mailbox and its messages are permanently deleted and can no longer be restored (`404`). Restoring a mailbox that is not deleted returns a conflict, as does an address that is no longer available.
 *
 */
 const restoreMailbox = (options) => (options.client ?? client).post({
@@ -2962,13 +3531,13 @@ const restoreMailbox = (options) => (options.client ?? client).post({
 	...options
 });
 /**
-* Mailbox email statistics
+* Get mailbox email statistics
 *
 * Returns the mailbox's sent and received email statistics over a time window: a period-wide summary plus a bucketed series. Sent-mail metrics have the same delivery, engagement, and latency breakdowns as the email stats endpoints. `received` counts mail that arrived at the mailbox.
 *
 * Rows are bucketed by the time the event happened rather than the time the message was sent, so engagement that arrived during the period for a message sent earlier is counted here. Statistics start when the mailbox starts sending and receiving; the mailbox's all-time `message_count` and `thread_count` live on the mailbox resource itself.
 *
-* `from` and `to` accept either calendar days (YYYY-MM-DD, `day` granularity only) or RFC 3339 instants (`hour` granularity only). Both bounds must use the same form. Window caps depend on `granularity`: 365 days at `day`, 30 days at `hour`. Set `timezone` to report in a local zone instead of UTC.
+* `from` and `to` accept either calendar days (`YYYY-MM-DD`, `day` granularity only) or RFC 3339 instants (`hour` granularity only). Both bounds must use the same form. Window caps depend on `granularity`: 365 days at `day`, 30 days at `hour`. Set `timezone` to report in a local zone instead of UTC.
 *
 */
 const getMailboxStats = (options) => (options.client ?? client).get({
@@ -3020,7 +3589,7 @@ const listMailboxReceiveRules = (options) => (options.client ?? client).get({
 	...options
 });
 /**
-* Add a receive rule
+* Create a receive rule
 *
 * Adds an allow or block rule to the mailbox. Rules match the message's envelope sender. Domain entries also match subdomains. Block rules always win, both over allow rules and over the reply admission on allowlist mailboxes. An entry is either allow or block. Rules have no update operation, so a rule that needs the other action is a new rule and the old one is removed. A mailbox holds up to 200 rules.
 *
@@ -3044,7 +3613,7 @@ const createMailboxReceiveRule = (options) => (options.client ?? client).post({
 /**
 * Delete a receive rule
 *
-* Removes a receive rule from the mailbox. There is no update operation for rules, so a rule's allow or block action cannot be changed after it is created.
+* Removes a receive rule from the mailbox. A rule's allow or block action cannot be changed after creation; delete it and create a replacement.
 *
 */
 const deleteMailboxReceiveRule = (options) => (options.client ?? client).delete({
@@ -3064,9 +3633,9 @@ const deleteMailboxReceiveRule = (options) => (options.client ?? client).delete(
 *
 * Returns a paginated list of conversations across the workspace's mailboxes, most recently active first. `label` selects the view: the inbox (the default when omitted), `archive`, `spam`, `blocked`, or any custom label. You can also filter by mailbox, by linked contact, by participant address, or by a subject substring.
 *
-* To search conversations by their messages' subject and text instead of listing them, use `GET /v1/email/threads/search`.
-*
-* Conversations whose every message has been trashed are left out of the list, and restoring a message brings the conversation back.
+* This listing filters; it does not search message content.
+* Conversations whose every message is trashed are excluded; restoring a message
+* returns the conversation to the list.
 *
 * `before` and `after` filter by time. To page through the results, pass the response cursors back as `starting_after` or `ending_before`.
 *
@@ -3086,7 +3655,7 @@ const listEmailThreads = (options) => (options?.client ?? client).get({
 /**
 * Delete a thread
 *
-* Moves the conversation and all of its messages to the trash. Trashed messages are permanently deleted after 30 days. Pass `permanent=true` to permanently delete the conversation and its messages immediately.
+* Moves the conversation and all of its messages to the trash. Trashed messages are permanently deleted after 30 days, or sooner if the mailbox's retention period ends first. Pass `permanent=true` to permanently delete the conversation and its messages immediately.
 *
 */
 const deleteEmailThread = (options) => (options.client ?? client).delete({
@@ -3104,7 +3673,7 @@ const deleteEmailThread = (options) => (options.client ?? client).delete({
 /**
 * Get a thread
 *
-* Returns a single conversation. Fetch the messages in the conversation with `GET /v1/email/threads/{thread_id}/messages`. A thread whose retention tier has ended returns `410 Gone`.
+* Returns a single conversation. Fetch the messages in the conversation with [List messages in a thread](/docs/api/reference/list-email-thread-messages). A thread whose retention tier has ended returns `410 Gone`.
 *
 */
 const getEmailThread = (options) => (options.client ?? client).get({
@@ -3122,7 +3691,7 @@ const getEmailThread = (options) => (options.client ?? client).get({
 /**
 * Update a thread
 *
-* Applies label changes to a conversation, and links or unlinks a contact. Adding `spam` files the conversation, and its received messages, as spam. Adding `archive` files it away without deleting it. Adding `inbox`, or removing `spam`, `blocked`, or `archive`, returns it to the inbox, and its unread count recomputes to match. An archived conversation returns to the inbox by itself when a new message arrives. To block a sender going forward, add a receive rule instead. Any field you leave out stays unchanged.
+* Applies label changes to a conversation, and links or unlinks a contact. Adding `spam` files the conversation, and its received messages, as spam. Adding `archive` files it away without deleting it. Adding `inbox`, or removing `spam`, `blocked`, or `archive`, returns it to the inbox, and its unread count recomputes to match. An archived conversation returns to the inbox by itself when a new message arrives that isn't spam or blocked; a junk reply or an outbound send leaves it archived. To block a sender going forward, add a receive rule instead. Any field you leave out stays unchanged.
 *
 */
 const updateEmailThread = (options) => (options.client ?? client).patch({
@@ -3184,7 +3753,7 @@ const getEmailThreadMessage = (options) => (options.client ?? client).get({
 /**
 * Get a thread message's original body
 *
-* Returns the original rendered HTML and plain-text body of a message in a conversation. The original body is available for 30 days after the message occurred. After that, this endpoint returns `410 Gone`, but the message's extracted text stays readable on the message itself.
+* Returns the original rendered HTML and plain-text body of a message in a conversation. The original body is available for 30 days after the message occurred. Later requests return `410 Gone`, while the message's extracted text stays readable on the message itself.
 *
 */
 const getEmailThreadMessageBody = (options) => (options.client ?? client).get({
@@ -3202,7 +3771,7 @@ const getEmailThreadMessageBody = (options) => (options.client ?? client).get({
 /**
 * List a thread message's attachments
 *
-* Returns the attachments on a message in a conversation. Attachment bytes are downloadable for 30 days after the message occurred. After that, this endpoint returns `410 Gone`, but the attachment metadata stays readable on the message's `attachment_manifest`.
+* Returns the attachments on a message in a conversation. Attachment bytes are downloadable for 30 days after the message occurred. Later requests return `410 Gone`, while the attachment metadata stays readable on the message's `attachment_manifest`.
 *
 */
 const listEmailThreadMessageAttachments = (options) => (options.client ?? client).get({
@@ -3220,7 +3789,7 @@ const listEmailThreadMessageAttachments = (options) => (options.client ?? client
 /**
 * Reply to a thread message
 *
-* Sends a reply to a specific message in a conversation, from the mailbox's own address. Recipients are derived from the message being replied to: its Reply-To address when present, otherwise its From address. Set `reply_all` to also include the original To and Cc recipients. The subject and the threading headers that keep the reply in this conversation are set automatically, and the reply is recorded in the conversation. To reply to a conversation as a whole, target its newest received message.
+* Sends a reply to a specific message in a conversation, from the mailbox's own address. Recipients are derived from the message being replied to: for a received message, its Reply-To address when present, otherwise its From address; for a message the mailbox sent, its original To recipients. Set `reply_all` to copy the original To and Cc recipients in as `Cc`, leaving out the mailbox's own address. The subject and the threading headers that keep the reply in this conversation are set automatically, and the reply is recorded in the conversation. To reply to a conversation as a whole, target its newest received message.
 *
 */
 const replyEmailThreadMessage = (options) => (options.client ?? client).post({
@@ -3240,9 +3809,9 @@ const replyEmailThreadMessage = (options) => (options.client ?? client).post({
 	}
 });
 /**
-* Send a message from a mailbox
+* Create a message from a mailbox
 *
-* Sends a new message from the mailbox's own address and starts a new conversation with it. The request mirrors the plain send request minus `from`, because the mailbox is who the message comes from. We set the RFC 5322 Message-ID, so later replies from the recipients thread back into the conversation automatically. The send is added to the mailbox's remembered messages and returned as the conversation's first message. A mailbox always sends immediately, so this endpoint does not accept a scheduled send. A suspended mailbox cannot send and returns `403`.
+* Sends a new message from the mailbox's own address and starts a new conversation with it. The request mirrors the plain send request minus `from`, because the mailbox is who the message comes from. We set the RFC 5322 Message-ID, so later replies from the recipients thread back into the conversation automatically. The send is added to the mailbox's remembered messages and returned as the conversation's first message. A mailbox always sends immediately; scheduled sends are unavailable. A suspended mailbox cannot send and returns `403`.
 *
 */
 const createMailboxMessage = (options) => (options.client ?? client).post({
@@ -3272,10 +3841,9 @@ const createMailboxMessage = (options) => (options.client ?? client).post({
 * - `unread`.
 *
 * Then, every custom label currently in use on its conversations and
-* messages. You apply and remove labels through the conversation and
-* message update endpoints, and that is also what creates or removes a
-* custom label: it exists for as long as at least one message or
-* conversation has it applied.
+* messages. Apply and remove labels through the conversation and message
+* update endpoints. These actions also create and remove custom labels. A
+* custom label exists while at least one message or conversation uses it.
 *
 */
 const listMailboxLabels = (options) => (options.client ?? client).get({
@@ -3293,11 +3861,18 @@ const listMailboxLabels = (options) => (options.client ?? client).get({
 /**
 * List calls
 *
-* Returns a paginated list of the workspace's calls, ordered by start time descending.
+* Returns a paginated list of the workspace's calls, ordered by start time
+* descending.
 *
-* The `status` filter selects where in the lifecycle you look, and any combination is a single page: in-flight statuses (`ringing`, `in_progress`), final ones, or both together. Omit it and you get completed calls, which is what this list has always returned.
+* The `status` filter selects where in the lifecycle you look, and any
+* combination is a single page: in-flight statuses (`ringing`,
+* `in_progress`), final ones, or both together. Omit it and you get
+* completed calls, which is what this list has always returned.
 *
-* A call in flight carries no economics yet: `duration_ms`, `billable_ms`, `ended_at`, and `cost` are null until it ends. It keeps the same `id` throughout, so the same call answers under one identity from the first ring to settlement.
+* A call in flight carries no economics yet: `duration_ms`, `billable_ms`,
+* `ended_at`, and `cost` are null until it ends. It keeps the same `id`
+* throughout, so the same call answers under one identity from the first
+* ring to settlement.
 *
 */
 const listVoiceCalls = (options) => (options?.client ?? client).get({
@@ -3430,10 +4005,33 @@ var EmailResourceBase = class extends Resource {
 	}
 };
 //#endregion
+//#region src/resources/emailDefaults.ts
+/**
+* Merge configured channel defaults under one set of per-call params.
+*
+* A field handed no value (`undefined`, or a `null` from a JSON-shaped input)
+* reads as unset, so its default still fills it. Spreading the params over the
+* defaults instead would let that no-value win and drop the field off the wire,
+* which the field-by-field merges in the other SDKs cannot do.
+*
+* `accepts` narrows the merge to the fields one body declares, for a request
+* that rejects a field the send body allows.
+*/
+function withDefaults(defaults, params, accepts) {
+	if (defaults === void 0) return params;
+	const fill = accepts === void 0 ? { ...defaults } : Object.fromEntries(Object.entries(defaults).filter(([key]) => accepts.includes(key)));
+	const merged = {
+		...fill,
+		...params
+	};
+	for (const [key, value] of Object.entries(fill)) if (merged[key] === void 0 || merged[key] === null) merged[key] = value;
+	return merged;
+}
+//#endregion
 //#region src/resources/emailStats.gen.ts
 var EmailStatsResource = class extends Resource {
 	/**
-	* Aggregate email KPIs for one period: sends, delivered, bounces, complaints, opens, clicks, their rates, and latency percentiles. `from`/`to` are both YYYY-MM-DD days or both RFC 3339 instants (hour grain); add `compare=previous_period` for deltas versus the prior window. For a per-day or per-hour series use `email.stats.daily` or `email.stats.hourly`.
+	* Aggregate email KPIs for one period: sends, delivered, bounces, complaints, opens, clicks, their rates, and latency percentiles. The `from` and `to` values are both `YYYY-MM-DD` days or both RFC 3339 instants (hour grain). Add `compare=previous_period` for deltas versus the prior window. For a per-day or per-hour series use `email.stats.daily` or `email.stats.hourly`.
 	*
 	* @example Summary for a month
 	* const s = await bird.email.stats.summary({ from: "2026-05-01", to: "2026-05-31" });
@@ -3513,7 +4111,7 @@ var EmailStatsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Delivery and bounce stats grouped by sending IP, with deferral counts alongside them. `sort=bounces.block` surfaces reputation-damaged IPs first. Engagement, accepted, and processed counts aren't available per IP, and complaint and out-of-band bounce counts always read 0 here. For workspace-wide figures, use `email.stats.daily`.
+	* Delivery and bounce stats grouped by sending IP, with deferral counts alongside them. `sort=bounces.block` surfaces reputation-damaged IPs first. Engagement, accepted, and processed counts aren't available per IP, and complaint and out-of-band bounce counts always read `0` here. For workspace-wide figures, use `email.stats.daily`.
 	*
 	* @example 
 	* const { data } = await bird.email.stats.bySendingIp({
@@ -3573,7 +4171,7 @@ var EmailStatsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Email delivery and engagement stats grouped by recipient mailbox provider, for example `gmail`, `microsoft`, or `yahoo`. It covers the delivery stage onward, so there are no accepted or processed counts. For a per-region split within a provider, use `email.stats.by_mailbox_provider_region`; for exact destination domains instead, use `email.stats.by_recipient_domain`.
+	* Email delivery and engagement stats grouped by recipient mailbox provider, for example `gmail`, `microsoft`, or `yahoo`. It covers the delivery stage onward and omits accepted or processed counts. For a per-region split within a provider, use `email.stats.by_mailbox_provider_region`; for exact destination domains instead, use `email.stats.by_recipient_domain`.
 	*
 	* @example 
 	* const { data } = await bird.email.stats.byMailboxProvider({
@@ -3592,7 +4190,7 @@ var EmailStatsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Email delivery and engagement stats grouped by a mailbox provider and provider region pair, for example `gmail` in `NA`. It covers the delivery stage onward, so there are no accepted or processed counts. For the provider-level view without the region split, use `email.stats.by_mailbox_provider`.
+	* Email delivery and engagement stats grouped by a mailbox provider and provider region pair, for example `gmail` in `NA`. It covers the delivery stage onward and omits accepted or processed counts. For the provider-level view without the region split, use `email.stats.by_mailbox_provider`.
 	*
 	* @example 
 	* const { data } = await bird.email.stats.byMailboxProviderRegion({
@@ -3669,7 +4267,7 @@ var EmailStatsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Bounce counts grouped by the SMTP error code the receiving mail server returned. Each row also breaks the bounce down into its hard, soft, admin, block, and undetermined split. There are no delivered, open, or click counts here, because a bounce code only appears on a bounce event. For bounces broken down by destination instead, use `email.stats.by_recipient_domain` or `email.stats.by_mailbox_provider`.
+	* Bounce counts grouped by the SMTP error code the receiving mail server returned. Each row also breaks the bounce down into its hard, soft, admin, block, and undetermined split. It omits delivered, open, and click counts because a bounce code only appears on a bounce event. For bounces broken down by destination instead, use `email.stats.by_recipient_domain` or `email.stats.by_mailbox_provider`.
 	*
 	* @example 
 	* const { data } = await bird.email.stats.byBounceCode({
@@ -3689,7 +4287,7 @@ var EmailStatsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Spam-complaint counts grouped by the feedback-loop complaint type, for example `abuse`, `fraud`, or `virus`. Complaint side only, so there are no delivery or engagement counts. For complaints broken down by destination instead, use `email.stats.by_mailbox_provider` or `email.stats.by_recipient_domain`.
+	* Spam-complaint counts grouped by the feedback-loop complaint type, for example `abuse`, `fraud`, or `virus`. This complaint-only breakdown omits delivery and engagement counts. For complaints broken down by destination instead, use `email.stats.by_mailbox_provider` or `email.stats.by_recipient_domain`.
 	*
 	* @example 
 	* const { data } = await bird.email.stats.byComplaintType({ from: "2026-05-01", to: "2026-05-31" });
@@ -3762,7 +4360,7 @@ var EmailMailboxesResourceBase = class extends Resource {
 		}));
 	}
 	/**
-	* Read one mailbox by ID. A mailbox deleted within its 30-day restore window is still returned, with a non-null `deleted_at`. Once that window closes it is gone and this returns 404.
+	* Read one mailbox by ID. A mailbox deleted within its 30-day restore window is still returned, with `deleted_at` set. Once that window closes it is gone and this returns `404`.
 	*
 	* @example Get a mailbox
 	* const mailbox = await bird.email.mailboxes.get("mbx_01abc");
@@ -3810,7 +4408,7 @@ var EmailMailboxesResourceBase = class extends Resource {
 		}));
 	}
 	/**
-	* Restore a mailbox deleted less than 30 days ago: the address starts receiving again and the remembered messages are back. Past the window the mailbox is permanently deleted and returns 404. A mailbox that is not deleted returns 409.
+	* Restore a mailbox deleted less than 30 days ago: the address starts receiving again and the remembered messages are back. Past the window the mailbox is permanently deleted and returns `404`. A mailbox that is not deleted returns `409`.
 	*
 	* @example Restore a deleted mailbox
 	* const mailbox = await bird.email.mailboxes.restore("mbx_01abc");
@@ -3825,7 +4423,7 @@ var EmailMailboxesResourceBase = class extends Resource {
 		}));
 	}
 	/**
-	* Resume a suspended mailbox so it can send and receive again and its conversations become visible. Fails if your plan does not have room for another active mailbox (or another custom inbox.ai handle). Delete an active mailbox or upgrade first. A mailbox that is not suspended returns 409.
+	* Resume a suspended mailbox so it can send and receive again and its conversations become visible. Fails if your plan does not have room for another active mailbox (or another custom inbox.ai handle). Delete an active mailbox or upgrade first. A mailbox that is not suspended returns `409`.
 	*
 	* @example Resume a suspended mailbox
 	* const mailbox = await bird.email.mailboxes.resume("mbx_01abc");
@@ -3873,7 +4471,18 @@ var EmailMailboxesResourceBase = class extends Resource {
 };
 //#endregion
 //#region src/resources/emailMailboxesMessages.ts
+const COMPOSE_FIELDS = [
+	"reply_to",
+	"category",
+	"tags",
+	"metadata"
+];
 var EmailMailboxesMessagesResource = class extends Resource {
+	#defaults;
+	constructor(core, client, defaults) {
+		super(core, client);
+		this.#defaults = defaults;
+	}
 	/**
 	* Send a new email from this mailbox, starting a new conversation.
 	*
@@ -3885,10 +4494,11 @@ var EmailMailboxesMessagesResource = class extends Resource {
 	* });
 	*/
 	create(mailboxId, params, options) {
+		const body = withDefaults(this.#defaults, params, COMPOSE_FIELDS);
 		return this.call("POST", options, ({ signal, headers }) => createMailboxMessage({
 			client: this.client,
 			path: { mailbox_id: mailboxId },
-			body: params,
+			body,
 			headers,
 			signal
 		}));
@@ -3961,10 +4571,10 @@ var EmailMailboxesResource = class extends EmailMailboxesResourceBase {
 	messages;
 	/** Per-sender allow/block rules — `bird.email.mailboxes.receiveRules.create(...)`, `.list(...)`, `.delete(...)`. */
 	receiveRules;
-	constructor(...args) {
-		super(...args);
-		this.messages = new EmailMailboxesMessagesResource(...args);
-		this.receiveRules = new EmailMailboxesReceiveRulesResource(...args);
+	constructor(core, client, defaults) {
+		super(core, client);
+		this.messages = new EmailMailboxesMessagesResource(core, client, defaults);
+		this.receiveRules = new EmailMailboxesReceiveRulesResource(core, client);
 	}
 };
 //#endregion
@@ -4023,7 +4633,7 @@ var EmailThreadsResourceBase = class extends Resource {
 		}));
 	}
 	/**
-	* Move a conversation and all its messages to trash (purged after 30 days), or delete permanently with ?permanent=true.
+	* Move a conversation and all its messages to trash (purged after 30 days), or delete permanently with `?permanent=true`.
 	*
 	* @example Delete a thread
 	* await bird.email.threads.delete("thr_01abc", { permanent: true });
@@ -4042,7 +4652,7 @@ var EmailThreadsResourceBase = class extends Resource {
 //#region src/resources/emailThreadsMessages.gen.ts
 var EmailThreadsMessagesResource = class extends Resource {
 	/**
-	* List the messages in a conversation newest first, both directions. Page older messages with starting_after, and pass include=extracted_text to inline each message's extracted plain text.
+	* List the messages in a conversation newest first, both directions. Page older messages with `starting_after`, and pass `include=extracted_text` to inline each message's extracted plain text.
 	*
 	* @example List a thread's messages
 	* for await (const msg of bird.email.threads.messages.list("thr_01abc")) {
@@ -4161,7 +4771,7 @@ var EmailResource = class extends EmailResourceBase {
 		super(core, client);
 		this.#defaults = defaults;
 		this.stats = new EmailStatsResource(core, client);
-		this.mailboxes = new EmailMailboxesResource(core, client);
+		this.mailboxes = new EmailMailboxesResource(core, client, defaults);
 		this.threads = new EmailThreadsResource(core, client);
 	}
 	/**
@@ -4179,6 +4789,29 @@ var EmailResource = class extends EmailResourceBase {
 	* });
 	* console.log(msg.id, msg.status); // "em_…", "accepted"
 	*
+	* @example Send a published template instead of inline content
+	* const msg = await bird.email.send({
+	*   from: { email: "onboarding@messagebird.dev", name: "Bird" },
+	*   to: ["delivered@messagebird.dev"],
+	*   category: "transactional",
+	*   template: {
+	*     slug: "welcome-email",
+	*     parameters: { first_name: "Jane" },
+	*   },
+	* });
+	* console.log(msg.id, msg.status);
+	*
+	* @example Sending to the sandbox bounce address, which hard-bounces every time
+	* const msg = await bird.email.send({
+	*   from: { email: "onboarding@messagebird.dev", name: "Bird" },
+	*   to: ["bounce+signup-flow@messagebird.dev"],
+	*   subject: "Sandbox bounce test",
+	*   html: "<p>This message will hard-bounce.</p>",
+	*   tags: [{ name: "flow", value: "signup" }],
+	*   metadata: { test_run: "docs-capture-1" },
+	* });
+	* console.log(msg.id, msg.status); // "em_…", "accepted"
+	*
 	* @example A richer send — cc/bcc, reply-to, tags, metadata, click-tracking off, and an idempotency key (safe to retry; the server dedupes)
 	* await bird.email.send(
 	*   {
@@ -4206,7 +4839,7 @@ var EmailResource = class extends EmailResourceBase {
 	*     html: "<p>My first Bird email.</p>",
 	*   });
 	* } catch (err) {
-	*   if (err instanceof BirdRateLimitError) console.log(`rate limited — retry in ${err.retryAfter}s`);
+	*   if (err instanceof BirdRateLimitError) console.log(`rate limited; retry in ${err.retryAfter}s`);
 	*   else if (err instanceof BirdValidationError) console.error(err.details);
 	*   else if (err instanceof BirdAPIError) console.error(err.code, err.requestId);
 	*   else throw err;
@@ -4225,10 +4858,7 @@ var EmailResource = class extends EmailResourceBase {
 	* else console.log(data.id);
 	*/
 	send(params, options) {
-		const body = {
-			...this.#defaults,
-			...params
-		};
+		const body = withDefaults(this.#defaults, params);
 		return this.call("POST", options, ({ signal, headers }) => createEmailMessage({
 			client: this.client,
 			body,
@@ -4242,7 +4872,8 @@ var EmailResource = class extends EmailResourceBase {
 	* sender, all recipients suppressed, field-level errors) the whole batch is
 	* rejected with a `BirdValidationError` and nothing is queued. Resolves with
 	* one accepted item per submitted message, in submission order, once the batch
-	* is accepted (the API's 202). Channel defaults are applied per item.
+	* is accepted (the API's 202). Channel defaults are applied per item, so a
+	* field set as a default may be omitted from every item (per-item value wins).
 	*
 	* @example Send a batch of messages
 	* const batch = await bird.email.sendBatch([
@@ -4262,10 +4893,7 @@ var EmailResource = class extends EmailResourceBase {
 	* for (const item of batch.data) console.log(item.id, item.status);
 	*/
 	sendBatch(params, options) {
-		const body = params.map((item) => ({
-			...this.#defaults,
-			...item
-		}));
+		const body = params.map((item) => withDefaults(this.#defaults, item));
 		return this.call("POST", options, ({ signal, headers }) => createEmailMessageBatch({
 			client: this.client,
 			body,
@@ -4327,7 +4955,7 @@ var AudiencesResource = class extends Resource {
 		}));
 	}
 	/**
-	* Update an audience's name or description. Omitted fields are unchanged; a null description clears it.
+	* Update an audience's name or description. Omitted fields are unchanged; a `null` description clears it.
 	*
 	* @example Rename an audience
 	* await bird.audiences.update("adn_01krdgeqcxet5s7t44vh8rt9mg", { name: "Renamed" });
@@ -4516,7 +5144,7 @@ var DomainsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Delete a sending domain by id. Revokes its sender authorization: new sends from the domain are rejected afterward, while historical statistics and events for past sends are preserved. Destructive.
+	* Delete a sending domain by ID. Revokes its sender authorization: new sends from the domain are rejected afterward, while historical statistics and events for past sends are preserved. Destructive.
 	*
 	* @example Delete a sending domain by id
 	* await bird.domains.delete("dom_01krdgeqcxet5s7t44vh8rt9mg");
@@ -4632,7 +5260,7 @@ var ContactPropertiesResource = class extends Resource {
 //#region src/resources/contacts.gen.ts
 var ContactsResource = class extends Resource {
 	/**
-	* List the workspace's contacts as a cursor page, newest first. Look one up by exact email, phone_number, or external_id, or search by email, name, or phone substring. Pass include_total for a total count.
+	* List the workspace's contacts as a cursor page, newest first. Look one up by exact email, phone_number, or external_id, repeating phone_number to resolve up to 50 numbers in one call (raise limit to match), or search by email, name, or phone substring. Pass include_total for a total count.
 	*
 	* @example Iterate every contact, or take one page
 	* for await (const contact of bird.contacts.list({ q: "acme.com" })) {
@@ -4652,7 +5280,7 @@ var ContactsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Get a single contact by ID (`con_`-prefixed). Look up an ID by exact email, phone_number, or external_id with `contacts.list`.
+	* Get a single contact by ID. Look up an ID by exact email, phone_number, or external_id with `contacts.list`.
 	*
 	* @example Fetch a contact by id
 	* const contact = await bird.contacts.get("con_01krdgeqcxet5s7t44vh8rt9mg");
@@ -4667,125 +5295,453 @@ var ContactsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Create a contact identified by an email address, an E.164 phone number, or both. Fails with a conflict if the email, phone_number, or external_id is already used by another contact. For bulk import or create-or-update semantics use `contacts.batch`.
+	* Create a contact identified by an email address, an E.164 phone number, or both. Fails with a conflict if the email, phone_number, or external_id is already used by another contact. For bulk import or create-or-update semantics use `contacts.batch`.
+	*
+	* @example Create a contact
+	* const contact = await bird.contacts.create({
+	*   email: "jane@acme.com",
+	*   first_name: "Jane",
+	* });
+	* console.log(contact.id); // "con_…"
+	*/
+	create(params = {}, options) {
+		return this.call("POST", options, ({ signal, headers }) => createContact({
+			client: this.client,
+			body: params,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* Update a contact's name, `external_id`, email, `phone_number`, or custom data. Only supplied fields change; custom data keys are merged, with `null` removing a key. A contact keeps at least one identifier: clearing both email and `phone_number` is rejected.
+	*
+	* @example Change a contact's fields
+	* const contact = await bird.contacts.update("con_01krdgeqcxet5s7t44vh8rt9mg", {
+	*   first_name: "Jane",
+	* });
+	* console.log(contact.first_name);
+	*/
+	update(contactId, params = {}, options) {
+		return this.call("PATCH", options, ({ signal, headers }) => updateContact({
+			client: this.client,
+			path: { contact_id: contactId },
+			body: params,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* Delete a contact and remove it from every audience it belongs to. Suppression records for the address are unaffected.
+	*
+	* @example Delete a contact by id
+	* await bird.contacts.delete("con_01krdgeqcxet5s7t44vh8rt9mg");
+	*/
+	delete(contactId, options) {
+		return this.call("DELETE", options, ({ signal, headers }) => deleteContact({
+			client: this.client,
+			path: { contact_id: contactId },
+			headers,
+			signal
+		}));
+	}
+	/**
+	* Create or update up to 1,000 contacts in one request. Match each entry against every supplied identifier (`email`, `phone_number`, and `external_id`), or set `match_on` to use one identifier. Optionally add all successful contacts to up to 10 audiences. Results follow submission order.
+	*
+	* @example Create or update many contacts at once, matched by the identifiers each entry carries
+	* const result = await bird.contacts.batch({
+	*   contacts: [{ email: "jane@acme.com", first_name: "Jane" }],
+	* });
+	* for (const item of result.data) {
+	*   console.log(item.entry.email, item.status);
+	* }
+	*/
+	batch(params, options) {
+		return this.call("POST", options, ({ signal, headers }) => createContactBatch({
+			client: this.client,
+			body: params,
+			headers,
+			signal
+		}));
+	}
+};
+//#endregion
+//#region src/resources/sms.gen.ts
+var SmsResourceBase = class extends Resource {
+	/**
+	* Get one SMS message by ID: its current delivery status, segment breakdown, cost, and failure detail if it failed.
+	*
+	* @example Read a message back
+	* const msg = await bird.sms.get("sms_abc123");
+	* msg.status; // "accepted" | "delivered" | …
+	*/
+	get(messageId, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsMessage({
+			client: this.client,
+			path: { message_id: messageId },
+			headers,
+			signal
+		}));
+	}
+	/**
+	* List SMS messages, newest first, as a cursor page (`data`, `next_cursor`). Pass `next_cursor` back as `starting_after` to fetch the next page. Filter by direction, status, category, recipient, sender, or tag.
+	*
+	* @example Iterate outbound messages
+	* for await (const msg of bird.sms.list({ direction: "outbound" })) {
+	*   console.log(msg.id, msg.status);
+	* }
+	*/
+	list(query, options) {
+		return this.paginated("GET", options, ({ signal, headers }, cursor) => listSmsMessages({
+			client: this.client,
+			query: {
+				...query,
+				starting_after: cursor ?? query?.starting_after
+			},
+			headers,
+			signal
+		}));
+	}
+	/**
+	* The lifecycle event timeline for one SMS, oldest first: what happened to it and when. Filter with `type` (for example `sms.delivered`) to keep one kind of event. Use `sms.get` for the message's current state and `sms.list` to find its ID.
+	*
+	* @example Read one message's lifecycle timeline
+	* const events = await bird.sms.listEvents("sms_abc123");
+	* for (const event of events.data ?? []) {
+	*   console.log(event.type, event.occurred_at);
+	* }
+	*/
+	listEvents(messageId, query, options) {
+		return this.call("GET", options, ({ signal, headers }) => listSmsMessageEvents({
+			client: this.client,
+			path: { message_id: messageId },
+			query,
+			headers,
+			signal
+		}));
+	}
+};
+//#endregion
+//#region src/resources/smsStats.gen.ts
+var SmsStatsResourceBase = class extends Resource {
+	/**
+	* Aggregate SMS KPIs for one period: accepted, sent, delivered, undelivered, failed, rejected and expired counts, the derived delivery and failure rates, and latency percentiles. The `from` and `to` values are both YYYY-MM-DD days or both RFC 3339 instants (hour grain). Add `compare=previous_period` for deltas against the preceding window. For a per-day or per-hour series use `sms.stats.daily` or `sms.stats.hourly`.
+	*
+	* @example Aggregate KPIs for a window
+	* const summary = await bird.sms.stats.summary({
+	*   from: "2026-05-01", // both calendar days for a day window, or
+	*   to: "2026-05-31", //   both RFC 3339 instants for an hour window
+	* });
+	* console.log(summary.delivery, summary.latency);
+	*/
+	summary(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsSummary({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* One row of SMS lifecycle counts per calendar day, for charts and trend lines. The window is at most 365 days; set `timezone` to get local calendar days instead of UTC. Rates and latency percentiles are whole-window figures, so read those from `sms.stats.summary`.
+	*
+	* @example One row per calendar day
+	* const stats = await bird.sms.stats.daily({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const point of stats.data ?? []) {
+	*   console.log(point.bucket, point.delivery);
+	* }
+	*/
+	daily(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsDaily({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* One row of SMS lifecycle counts per hour, for inspecting send rate and deliverability inside a single day. The window is at most 30 days (720 rows) and both bounds round down to the hour. For longer ranges use `sms.stats.daily`.
+	*
+	* @example One row per hour, up to 30 days
+	* const stats = await bird.sms.stats.hourly({
+	*   from: "2026-05-30T00:00:00Z",
+	*   to: "2026-05-31T00:00:00Z",
+	* });
+	* for (const point of stats.data ?? []) {
+	*   console.log(point.bucket, point.delivery);
+	* }
+	*/
+	hourly(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsHourly({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* SMS delivery and latency stats grouped by destination country, ranked by the `sort` metric (default `accepted`) and capped by `limit` (default 50, maximum 200). Use it to find where delivery is worst before drilling into `sms.stats.by_error_code`.
+	*
+	* @example Find where delivery is worst
+	* const stats = await bird.sms.stats.byCountry({
+	*   from: "2026-05-01",
+	*   to: "2026-05-31",
+	*   sort: "delivery_rate",
+	* });
+	* for (const row of stats.data ?? []) {
+	*   console.log(row.country, row.delivery);
+	* }
+	*/
+	byCountry(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsByCountry({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* SMS delivery and latency stats grouped by the carrier that handled the message, ranked by the `sort` metric (default `accepted`) and capped by `limit` (default 50, maximum 200). Use it to compare delivery performance across carriers.
+	*
+	* @example Compare delivery across carriers
+	* const stats = await bird.sms.stats.byCarrier({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const row of stats.data ?? []) {
+	*   console.log(row.carrier, row.delivery);
+	* }
+	*/
+	byCarrier(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsByCarrier({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* SMS delivery and latency stats grouped by the category you sent under, ranked by the `sort` metric (default `accepted`) and capped by `limit` (default 50, maximum 200).
+	*
+	* @example Split a window by category
+	* const stats = await bird.sms.stats.byCategory({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const row of stats.data ?? []) {
+	*   console.log(row.category, row.delivery);
+	* }
+	*/
+	byCategory(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsByCategory({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* SMS delivery and latency stats grouped by originator, the sender address messages went out from, ranked by the `sort` metric (default `accepted`) and capped by `limit` (default 50, maximum 200). Use it to compare how your senders perform.
+	*
+	* @example Compare how each sender performs
+	* const stats = await bird.sms.stats.byOriginator({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const row of stats.data ?? []) {
+	*   console.log(row.originator, row.delivery);
+	* }
+	*/
+	byOriginator(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsByOriginator({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* How many messages ended the period in each lifecycle status: accepted, sent, delivered, undelivered, failed, rejected, expired, ordered by count. The "where did my messages end up" view, suitable for a status-distribution chart.
+	*
+	* @example Where the window's messages ended up
+	* const stats = await bird.sms.stats.byStatus({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const row of stats.data ?? []) {
+	*   console.log(row.status, row.count);
+	* }
+	*/
+	byStatus(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsByStatus({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* SMS stats grouped by our normalized failure reason, which answers which reasons are driving your failures. The grouping key is the same value as the `error_code` filter on `sms.list`, so a row joins straight to the messages behind it. Ranked by the `sort` metric (default `failed`) and capped by `limit`.
+	*
+	* @example Which reasons drive failures
+	* const stats = await bird.sms.stats.byErrorCode({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const row of stats.data ?? []) {
+	*   // The same value as the error_code filter on bird.sms.list.
+	*   console.log(row.error_code, row.delivery);
+	* }
+	*/
+	byErrorCode(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsByErrorCode({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* SMS delivery and latency stats grouped by tag (`name:value`), ranked by the `sort` metric (default `accepted`) and capped by `limit` (default 50, maximum 200). Only tagged messages appear, and one carrying several tags counts once under each, so rows do not sum to the period total.
+	*
+	* @example Compare campaigns and segments
+	* const stats = await bird.sms.stats.byTag({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const row of stats.data ?? []) {
+	*   // A message carrying several tags counts once under each, so rows do not sum
+	*   // to the period total.
+	*   console.log(row.tag, row.delivery);
+	* }
+	*/
+	byTag(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsStatsByTag({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+};
+//#endregion
+//#region src/resources/smsStatsInbound.gen.ts
+var SmsStatsInboundResource = class extends Resource {
+	/**
+	* Total messages your numbers received over a period. For a breakdown use `sms.stats.inbound.by_country`, `sms.stats.inbound.by_operator`, or `sms.stats.inbound.by_number`.
 	*
-	* @example Create a contact
-	* const contact = await bird.contacts.create({
-	*   email: "jane@acme.com",
-	*   first_name: "Jane",
-	* });
-	* console.log(contact.id); // "con_…"
+	* @example Total messages received
+	* const summary = await bird.sms.stats.inbound.summary({ from: "2026-05-01", to: "2026-05-31" });
+	* console.log(summary.received);
 	*/
-	create(params = {}, options) {
-		return this.call("POST", options, ({ signal, headers }) => createContact({
+	summary(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsInboundStatsSummary({
 			client: this.client,
-			body: params,
+			query,
 			headers,
 			signal
 		}));
 	}
 	/**
-	* Update a contact's name, external_id, email, phone_number, or custom data. Only supplied fields change; custom data keys are merged, with null removing a key. A contact keeps at least one identifier: clearing both email and phone_number is rejected.
+	* Messages your numbers received, one row per calendar day. Set `timezone` to get local calendar days instead of UTC.
 	*
-	* @example Change a contact's fields
-	* const contact = await bird.contacts.update("con_01krdgeqcxet5s7t44vh8rt9mg", {
-	*   first_name: "Jane",
-	* });
-	* console.log(contact.first_name);
+	* @example Received messages per day
+	* const stats = await bird.sms.stats.inbound.daily({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const point of stats.data ?? []) {
+	*   console.log(point.bucket, point.received);
+	* }
 	*/
-	update(contactId, params = {}, options) {
-		return this.call("PATCH", options, ({ signal, headers }) => updateContact({
+	daily(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsInboundStatsDaily({
 			client: this.client,
-			path: { contact_id: contactId },
-			body: params,
+			query,
 			headers,
 			signal
 		}));
 	}
 	/**
-	* Delete a contact and remove it from every audience it belongs to. Suppression records for the address are unaffected.
+	* Messages your numbers received, one row per hour, for inspecting inbound volume inside a single day.
 	*
-	* @example Delete a contact by id
-	* await bird.contacts.delete("con_01krdgeqcxet5s7t44vh8rt9mg");
+	* @example Received messages per hour
+	* const stats = await bird.sms.stats.inbound.hourly({
+	*   from: "2026-05-30T00:00:00Z",
+	*   to: "2026-05-31T00:00:00Z",
+	* });
+	* for (const point of stats.data ?? []) {
+	*   console.log(point.bucket, point.received);
+	* }
 	*/
-	delete(contactId, options) {
-		return this.call("DELETE", options, ({ signal, headers }) => deleteContact({
+	hourly(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsInboundStatsHourly({
 			client: this.client,
-			path: { contact_id: contactId },
+			query,
 			headers,
 			signal
 		}));
 	}
 	/**
-	* Create or update up to 1,000 contacts in one request, each entry matched automatically against every identifier it supplies (email, phone_number, external_id) or, with match_on, by that one field only, and optionally add them all to one or more audiences. Per-contact results are returned in submission order.
+	* Messages your numbers received, grouped by the country of the receiving number.
 	*
-	* @example Create or update many contacts at once, matched by the identifiers each entry carries
-	* const result = await bird.contacts.batch({
-	*   contacts: [{ email: "jane@acme.com", first_name: "Jane" }],
-	* });
-	* for (const item of result.data) {
-	*   console.log(item.entry.email, item.status);
+	* @example Where senders messaged from
+	* const stats = await bird.sms.stats.inbound.byCountry({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const row of stats.data ?? []) {
+	*   console.log(row.country, row.received);
 	* }
 	*/
-	batch(params, options) {
-		return this.call("POST", options, ({ signal, headers }) => createContactBatch({
+	byCountry(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsInboundStatsByCountry({
 			client: this.client,
-			body: params,
+			query,
 			headers,
 			signal
 		}));
 	}
-};
-//#endregion
-//#region src/resources/sms.gen.ts
-var SmsResourceBase = class extends Resource {
 	/**
-	* Get one SMS message by id: its current delivery status, segment breakdown, cost, and failure detail if it failed.
+	* Messages your numbers received, grouped by the sender's mobile operator. Messages whose operator the carrier did not report are excluded, so these rows can sum to less than `sms.stats.inbound.summary` for the same period.
 	*
-	* @example Read a message back
-	* const msg = await bird.sms.get("sms_abc123");
-	* msg.status; // "accepted" | "delivered" | …
+	* @example Received messages per operator
+	* const stats = await bird.sms.stats.inbound.byOperator({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const row of stats.data ?? []) {
+	*   // Messages whose operator the carrier did not report are excluded, so these
+	*   // rows can sum to less than the inbound summary for the same period.
+	*   console.log(row.mcc_mnc, row.received);
+	* }
 	*/
-	get(messageId, options) {
-		return this.call("GET", options, ({ signal, headers }) => getSmsMessage({
+	byOperator(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsInboundStatsByOperator({
 			client: this.client,
-			path: { message_id: messageId },
+			query,
 			headers,
 			signal
 		}));
 	}
 	/**
-	* List SMS messages, newest first, as a cursor page ({data, next_cursor, …}). Pass next_cursor back as starting_after to fetch the next page. Filter by direction, status, category, recipient, sender, or tag.
+	* How many messages each of your numbers received, which is the view that shows whether a campaign's reply traffic is landing on the number you expect.
 	*
-	* @example Iterate outbound messages
-	* for await (const msg of bird.sms.list({ direction: "outbound" })) {
-	*   console.log(msg.id, msg.status);
+	* @example Which number took the traffic
+	* const stats = await bird.sms.stats.inbound.byNumber({ from: "2026-05-01", to: "2026-05-31" });
+	* for (const row of stats.data ?? []) {
+	*   console.log(row.number, row.received);
 	* }
 	*/
-	list(query, options) {
-		return this.paginated("GET", options, ({ signal, headers }, cursor) => listSmsMessages({
+	byNumber(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsInboundStatsByNumber({
 			client: this.client,
-			query: {
-				...query,
-				starting_after: cursor ?? query?.starting_after
-			},
+			query,
 			headers,
 			signal
 		}));
 	}
 };
 //#endregion
+//#region src/resources/smsStats.ts
+var SmsStatsResource = class extends SmsStatsResourceBase {
+	/** Received-message statistics — `bird.sms.stats.inbound.summary(...)`, `.byNumber(...)`, … */
+	inbound;
+	constructor(core, client) {
+		super(core, client);
+		this.inbound = new SmsStatsInboundResource(core, client);
+	}
+};
+//#endregion
 //#region src/resources/sms.ts
 /** Filters and cursor params for `bird.sms.list`. */
 var SmsResource = class extends SmsResourceBase {
+	/** SMS statistics: `bird.sms.stats.summary(...)`, `.daily(...)`, `.inbound.byNumber(...)`, … */
+	stats;
+	constructor(core, client) {
+		super(core, client);
+		this.stats = new SmsStatsResource(core, client);
+	}
 	/**
-	* Send one SMS to a single recipient. Supply either `text` (with a `category`)
-	* or a stored `template` (by `id` or `name`, with its `parameters`). The
-	* result is `accepted`, not yet delivered — read it back with `get` to confirm.
+	* Send one SMS to a single recipient. Supply either `text` (with a `category` and `from`)
+	* or a stored `template` (by `id` or `slug`, with its `parameters`). The API
+	* accepts the message for delivery. Read it back with `get` for the latest status.
 	*
 	* @example Send free text
 	* const msg = await bird.sms.send({
-	*   from: "MyBrand",
+	*   from: "+15557654321",
 	*   to: "+14155550100",
 	*   text: "Your verification code is 123456.",
 	*   category: "authentication",
@@ -4795,7 +5751,7 @@ var SmsResource = class extends SmsResourceBase {
 	* @example Send by template
 	* await bird.sms.send({
 	*   to: "+14155550100",
-	*   template: { name: "bird_otp_verification", parameters: { code: "123456" } },
+	*   template: { slug: "bird_otp_verification", parameters: { code: "123456" } },
 	* });
 	*/
 	send(params, options) {
@@ -4812,8 +5768,18 @@ var SmsResource = class extends SmsResourceBase {
 	*
 	* @example
 	* const result = await bird.sms.sendBatch([
-	*   { to: "+15551111111", text: "Hi Alice!", category: "marketing" },
-	*   { to: "+15552222222", text: "Hi Bob!", category: "marketing" },
+	*   {
+	*     from: "+15557654321",
+	*     to: "+15551111111",
+	*     text: "Hi Alice!",
+	*     category: "marketing",
+	*   },
+	*   {
+	*     from: "+15557654321",
+	*     to: "+15552222222",
+	*     text: "Hi Bob!",
+	*     category: "marketing",
+	*   },
 	* ]);
 	*/
 	sendBatch(params, options) {
@@ -4826,14 +5792,125 @@ var SmsResource = class extends SmsResourceBase {
 	}
 };
 //#endregion
+//#region src/resources/smsKeywordRules.gen.ts
+var SmsKeywordRulesResource = class extends Resource {
+	/**
+	* List the default and workspace keyword rules that apply to inbound messages, most specific first. Filter by `country`, `number`, `operation`, or `scope`. Pass `number` to see one number's rules in evaluation order. Default coverage varies by country.
+	*/
+	list(query, options) {
+		return this.call("GET", options, ({ signal, headers }) => listSmsKeywordRules({
+			client: this.client,
+			query,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* Read one default or workspace keyword rule. Its ID prefix identifies which kind: a workspace rule can be changed with `sms_keyword_rules.update`, a Bird default cannot.
+	*/
+	get(id, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsKeywordRule({
+			client: this.client,
+			path: { id },
+			headers,
+			signal
+		}));
+	}
+	/**
+	* Replace the default opt-out, opt-in, or help reply for one country, or add a `custom` keyword. A workspace rule takes precedence over the default for that country. Opt-out and opt-in keywords cannot be assigned to another operation.
+	*/
+	create(params, options) {
+		return this.call("POST", options, ({ signal, headers }) => createSmsKeywordRule({
+			client: this.client,
+			body: params,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* Change one of your own keyword rules: its reply, its extra keywords, or its self-managed attestation. Bird's default rules cannot be updated; create your own for that country instead with `sms_keyword_rules.create`. Omitting `keywords` leaves the set alone, while sending an empty list clears your additions back to Bird's.
+	*/
+	update(id, params = {}, options) {
+		return this.call("PATCH", options, ({ signal, headers }) => updateSmsKeywordRule({
+			client: this.client,
+			path: { id },
+			body: params,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* Delete one of your own keyword rules, which restores Bird's default for that country and operation. Bird's own rules cannot be deleted.
+	*/
+	delete(id, options) {
+		return this.call("DELETE", options, ({ signal, headers }) => deleteSmsKeywordRule({
+			client: this.client,
+			path: { id },
+			headers,
+			signal
+		}));
+	}
+};
+//#endregion
+//#region src/resources/smsSuppressions.gen.ts
+var SmsSuppressionsResource = class extends Resource {
+	/**
+	* List the workspace's SMS suppressions (sender-and-subscriber pairs blocked from delivery) as a cursor page.
+	*/
+	list(query, options) {
+		return this.paginated("GET", options, ({ signal, headers }, cursor) => listSmsSuppressions({
+			client: this.client,
+			query: {
+				...query,
+				starting_after: cursor ?? query?.starting_after
+			},
+			headers,
+			signal
+		}));
+	}
+	/**
+	* Read one SMS suppression: the sender and subscriber it covers, why messages are stopped, what it blocks, and whether it is still in force. To check whether you may message someone, filter `sms_suppressions.list` by their number instead.
+	*/
+	get(suppressionId, options) {
+		return this.call("GET", options, ({ signal, headers }) => getSmsSuppression({
+			client: this.client,
+			path: { suppression_id: suppressionId },
+			headers,
+			signal
+		}));
+	}
+	/**
+	* Stop one of your senders from messaging one subscriber. Covers that sender only; your other senders keep reaching them.
+	*/
+	add(params, options) {
+		return this.call("POST", options, ({ signal, headers }) => createSmsSuppression({
+			client: this.client,
+			body: params,
+			headers,
+			signal
+		}));
+	}
+	/**
+	* End a manual SMS suppression, letting that sender message that subscriber again. Only reason `manual` can be ended this way: a subscriber's own stop keyword and a carrier's opt-out are refused.
+	*/
+	remove(suppressionId, options) {
+		return this.call("DELETE", options, ({ signal, headers }) => deleteSmsSuppression({
+			client: this.client,
+			path: { suppression_id: suppressionId },
+			headers,
+			signal
+		}));
+	}
+};
+//#endregion
 //#region src/resources/smsTemplates.gen.ts
 var SmsTemplatesResource = class extends Resource {
 	/**
-	* List the SMS templates available to your workspace, including Bird's built-in templates. Filter by scope, category, or language. The catalogue is small and returned in full; this list is not paginated. Use sms_templates_get to read one template's variables before sending with it.
+	* List the SMS templates available to your workspace, including our built-in templates. Filter by scope, category, or language. The catalog is small and returned in full; this list is not paginated. Use `sms_templates.get` to read one template's variables before sending with it.
 	*
 	* @example List the built-in templates
 	* const { data } = await bird.smsTemplates.list({ scope: "system" });
-	* for (const tpl of data) console.log(tpl.id, tpl.name);
+	* for (const tpl of data) console.log(tpl.id, tpl.slug);
 	*/
 	list(query, options) {
 		return this.call("GET", options, ({ signal, headers }) => listSmsTemplates({
@@ -4844,9 +5921,9 @@ var SmsTemplatesResource = class extends Resource {
 		}));
 	}
 	/**
-	* Get one SMS template by its name or id, including its body and the variables it expects. Fetch it before sms_send to see which parameter keys a template send requires.
+	* Get one SMS template by its slug or ID, including its body and the variables it expects. Fetch it before `sms.send` to see which parameter keys a template send requires.
 	*
-	* @example Read one template by name or id
+	* @example Read one template by slug or id
 	* const tpl = await bird.smsTemplates.get("bird_otp_verification");
 	* console.log(tpl.body, tpl.variables);
 	*/
@@ -4863,7 +5940,7 @@ var SmsTemplatesResource = class extends Resource {
 //#region src/resources/whatsapp.gen.ts
 var WhatsappResourceBase = class extends Resource {
 	/**
-	* Get one WhatsApp message by id: current delivery status, sent/delivered/read timestamps, the template it was sent from, and failure detail if it failed. For the per-event timeline use whatsapp_list_events.
+	* Get one WhatsApp message by id: current delivery status, sent/delivered/read timestamps, the one content it was built from (a template, or free-form text, image, video, audio, sticker, document or location), and failure detail if it failed. For the per-event timeline use whatsapp_list_events.
 	*
 	* @example Read a message back
 	* const msg = await bird.whatsapp.get("wa_abc123");
@@ -4878,7 +5955,7 @@ var WhatsappResourceBase = class extends Resource {
 		}));
 	}
 	/**
-	* List WhatsApp messages, newest first, as a cursor page ({data, next_cursor, …}). Pass next_cursor back as starting_after to fetch the next page. Filter by direction, status, contact phone number, bsuid, template category, or tag. Use whatsapp_get for one message's current state.
+	* List WhatsApp messages, newest first, as a cursor page ({data, next_cursor, …}). Each message carries the one content it was built from: a template, or free-form text, image, video, audio, sticker, document or location. Pass next_cursor back as starting_after to fetch the next page. Filter by direction, status, contact phone number, bsuid, template category, or tag. Use whatsapp_get for one message's current state.
 	*
 	* @example Iterate delivered messages
 	* for await (const msg of bird.whatsapp.list({ status: ["delivered"] })) {
@@ -4897,7 +5974,7 @@ var WhatsappResourceBase = class extends Resource {
 		}));
 	}
 	/**
-	* Get one WhatsApp message's delivery timeline, oldest first: whatsapp.accepted, whatsapp.sent, whatsapp.delivered, whatsapp.read, and whatsapp.failed events, with failure detail on failed events. Not paginated; an unknown message id is a 404. Use whatsapp_get for the condensed current status.
+	* Get one WhatsApp message's delivery timeline, oldest first: whatsapp.accepted, whatsapp.sent, whatsapp.delivered, whatsapp.read, and whatsapp.failed events, with failure detail on failed events. Not paginated; an unknown message ID returns `404`. Use `whatsapp.get` for the condensed current status.
 	*
 	* @example Read one message's delivery timeline
 	* const { data } = await bird.whatsapp.listEvents("wa_abc123");
@@ -4917,19 +5994,18 @@ var WhatsappResourceBase = class extends Resource {
 //#region src/resources/whatsapp.ts
 var WhatsappResource = class extends WhatsappResourceBase {
 	/**
-	* Send a template message. Bird selects the sender number from the
-	* template's category, so there is no sender field on the request. The
-	* result is `accepted`, not yet delivered — read it back with `get` to
-	* confirm.
+	* Send one message, carrying exactly one kind of content: a template, or
+	* free-form `text`, `image`, `video`, `audio`, `sticker`, `document` or
+	* `location`. Every send but a Bird-managed template needs `from`, a number
+	* this workspace owns. The result is `accepted`, not yet delivered — read it
+	* back with `get` to confirm.
 	*
 	* @example
 	* const msg = await bird.whatsapp.send({
 	*   to: "+15551234567",
 	*   template: {
 	*     slug: "bird_otp",
-	*     components: [
-	*       { type: "body", parameters: [{ type: "text", text: "123456" }] },
-	*     ],
+	*     components: [{ type: "body", parameters: [{ type: "text", text: "123456" }] }],
 	*   },
 	* });
 	* console.log(msg.id, msg.status);
@@ -4947,7 +6023,7 @@ var WhatsappResource = class extends WhatsappResourceBase {
 //#region src/resources/voice.gen.ts
 var VoiceResource = class extends Resource {
 	/**
-	* List the workspace's calls, newest first. Filter to `ringing`/`in_progress` for the calls in progress right now, to final statuses for completed records, or to any mix of the two. Use `from`/`to` for one known party number in international form, and `number` to search either side by fragment. These are per-call records: for rates and totals over a period use voice_stats_summary rather than summing them here, and voice_get to follow one call to settlement.
+	* List the workspace's calls, newest first. Filter to `ringing`/`in_progress` for the calls in progress right now, to final statuses for completed records, or to any mix of the two. Use `from`/`to` for one known party number in international form, and `number` to search either side by fragment. These are per-call records and do not include aggregate rates or totals. Use `voice.get` to follow one call to settlement.
 	*
 	* @example Iterate the calls happening right now
 	* for await (const call of bird.voice.list({ status: ["ringing", "in_progress"] })) {
@@ -4966,7 +6042,7 @@ var VoiceResource = class extends Resource {
 		}));
 	}
 	/**
-	* Fetch one call by id, at any point in its lifecycle. A call still ringing or connected carries no economics yet: `duration_ms`, `billable_ms`, `ended_at`, and `cost` are null until it ends, and this same id then answers with the settled record. Poll here to watch one known call; use voice_list to find calls in the first place. When a call was refused, `rejection_reason` names the gate that turned it away.
+	* Fetch one call by ID, at any point in its lifecycle. A call still ringing or connected carries no economics yet: `duration_ms`, `billable_ms`, `ended_at`, and `cost` are null until it ends, and the same ID then returns the settled record. Poll here to watch one known call; use `voice.list` to find calls in the first place. When a call was refused, `rejection_reason` names the gate that turned it away.
 	*
 	* @example Read one call back
 	* const call = await bird.voice.get("vcl_01k0p3v9wera3v6q6xw3e9y2mh");
@@ -4986,7 +6062,7 @@ var VoiceResource = class extends Resource {
 //#region src/resources/verifyVerifications.gen.ts
 var VerifyVerificationsResource = class extends Resource {
 	/**
-	* Start a verification: generate a one-time passcode and send it to the recipient in `to` (a phone number over the phone channels enabled for its destination country; an email address over email; or both). It is sent over one channel at a time and fails over to the next in the plan, never over two at once. Calling again for the same recipient reuses the in-progress verification and sends a fresh code after the resend cooldown; it does not start a second one, so use this both to send and to resend. The passcode is never returned; submit what the recipient enters with verify_verifications_check. SMS delivery draws on the workspace's SMS balance.
+	* Start a verification and send a one-time passcode to the email address, phone number, or both in `to`. Delivery uses one planned channel at a time and fails over when necessary. Calling again for the same recipient reuses the verification in progress and sends after the resend cooldown. The passcode is never returned; submit the recipient's code with `verify.verifications.check`. SMS, WhatsApp, and Telegram delivery draw on the workspace's balance.
 	*
 	* @example Start a verification over SMS
 	* const verification = await bird.verify.verifications.create({
@@ -5003,7 +6079,7 @@ var VerifyVerificationsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Check a passcode a recipient submitted. Identify the verification by the same `to` recipient used to start it; no verification id needed. A wrong or expired code returns HTTP 200 with `success: false` and a `reason` (for example `incorrect_code` or `expired`), not an error. A verification that has already reached a final state is no longer checkable and returns 404, as does a missing verification; malformed input or rate limiting is also an error status.
+	* Check a passcode a recipient submitted. Identify the verification by the same `to` recipient used to start it; no verification ID is needed. A wrong or expired code returns HTTP 200 with `success: false` and a `reason` (for example `incorrect_code` or `expired`). A verification that has already reached a final state is no longer checkable and returns 404, as does a missing verification; malformed input or rate limiting is also an error status.
 	*
 	* @example Check a submitted passcode
 	* const result = await bird.verify.verifications.check({
@@ -5021,7 +6097,7 @@ var VerifyVerificationsResource = class extends Resource {
 		}));
 	}
 	/**
-	* Advance an in-progress verification to the next channel in its plan and send a fresh passcode there: the "I didn't receive my code" action. The verification is identified by the same `to` recipient used to start it, with no verification id needed. The send bypasses the resend cooldown, and earlier passcodes stay valid. Returns the verification with `last_channel` set to the channel the new code went to; when concurrent advances race for the same recipient, the response reflects committed state: `last_channel` names the most recent completed send, and the racing call that completed the newer send is authoritative. A plan with no further channel returns a 422 named NoNextChannel, after which only re-creating the verification will resend.
+	* Advance an in-progress verification to its next channel and send a fresh passcode. Identify it with the same `to` recipient used to create it; no verification ID is required. This bypasses the resend cooldown, and earlier passcodes remain valid. `last_channel` identifies the most recent completed send. `422 NoNextChannel` means the plan is exhausted; create the verification again to resend on the current channel.
 	*
 	* @example Send the code again on the next channel
 	* const verification = await bird.verify.verifications.nextChannel({
@@ -5243,6 +6319,242 @@ var RealtimeMembersResource = class extends Resource {
 	}
 };
 //#endregion
+//#region src/core/secretbox.gen.ts
+const SIGMA = new Uint8Array([
+	101,
+	120,
+	112,
+	97,
+	110,
+	100,
+	32,
+	51,
+	50,
+	45,
+	98,
+	121,
+	116,
+	101,
+	32,
+	107
+]);
+function rotl(x, c) {
+	return x << c | x >>> 32 - c;
+}
+function load32(b, i) {
+	return (b[i] | b[i + 1] << 8 | b[i + 2] << 16 | b[i + 3] << 24) >>> 0;
+}
+function store32(b, i, v) {
+	b[i] = v & 255;
+	b[i + 1] = v >>> 8 & 255;
+	b[i + 2] = v >>> 16 & 255;
+	b[i + 3] = v >>> 24 & 255;
+}
+/**
+* The Salsa20 core over the 4x4 state built from `key` and a 16-byte `input`.
+* With `feedForward` this is the Salsa20 block function (stream generation);
+* without it, the state words at the diagonal and input positions form the
+* HSalsa20 output used for XSalsa20's subkey derivation.
+*/
+function salsa20Core(key, input, feedForward) {
+	const j = /* @__PURE__ */ new Int32Array(16);
+	j[0] = load32(SIGMA, 0);
+	j[1] = load32(key, 0);
+	j[2] = load32(key, 4);
+	j[3] = load32(key, 8);
+	j[4] = load32(key, 12);
+	j[5] = load32(SIGMA, 4);
+	j[6] = load32(input, 0);
+	j[7] = load32(input, 4);
+	j[8] = load32(input, 8);
+	j[9] = load32(input, 12);
+	j[10] = load32(SIGMA, 8);
+	j[11] = load32(key, 16);
+	j[12] = load32(key, 20);
+	j[13] = load32(key, 24);
+	j[14] = load32(key, 28);
+	j[15] = load32(SIGMA, 12);
+	let x0 = j[0], x1 = j[1], x2 = j[2], x3 = j[3];
+	let x4 = j[4], x5 = j[5], x6 = j[6], x7 = j[7];
+	let x8 = j[8], x9 = j[9], x10 = j[10], x11 = j[11];
+	let x12 = j[12], x13 = j[13], x14 = j[14], x15 = j[15];
+	for (let round = 0; round < 20; round += 2) {
+		x4 ^= rotl(x0 + x12 | 0, 7);
+		x8 ^= rotl(x4 + x0 | 0, 9);
+		x12 ^= rotl(x8 + x4 | 0, 13);
+		x0 ^= rotl(x12 + x8 | 0, 18);
+		x9 ^= rotl(x5 + x1 | 0, 7);
+		x13 ^= rotl(x9 + x5 | 0, 9);
+		x1 ^= rotl(x13 + x9 | 0, 13);
+		x5 ^= rotl(x1 + x13 | 0, 18);
+		x14 ^= rotl(x10 + x6 | 0, 7);
+		x2 ^= rotl(x14 + x10 | 0, 9);
+		x6 ^= rotl(x2 + x14 | 0, 13);
+		x10 ^= rotl(x6 + x2 | 0, 18);
+		x3 ^= rotl(x15 + x11 | 0, 7);
+		x7 ^= rotl(x3 + x15 | 0, 9);
+		x11 ^= rotl(x7 + x3 | 0, 13);
+		x15 ^= rotl(x11 + x7 | 0, 18);
+		x1 ^= rotl(x0 + x3 | 0, 7);
+		x2 ^= rotl(x1 + x0 | 0, 9);
+		x3 ^= rotl(x2 + x1 | 0, 13);
+		x0 ^= rotl(x3 + x2 | 0, 18);
+		x6 ^= rotl(x5 + x4 | 0, 7);
+		x7 ^= rotl(x6 + x5 | 0, 9);
+		x4 ^= rotl(x7 + x6 | 0, 13);
+		x5 ^= rotl(x4 + x7 | 0, 18);
+		x11 ^= rotl(x10 + x9 | 0, 7);
+		x8 ^= rotl(x11 + x10 | 0, 9);
+		x9 ^= rotl(x8 + x11 | 0, 13);
+		x10 ^= rotl(x9 + x8 | 0, 18);
+		x12 ^= rotl(x15 + x14 | 0, 7);
+		x13 ^= rotl(x12 + x15 | 0, 9);
+		x14 ^= rotl(x13 + x12 | 0, 13);
+		x15 ^= rotl(x14 + x13 | 0, 18);
+	}
+	const x = [
+		x0,
+		x1,
+		x2,
+		x3,
+		x4,
+		x5,
+		x6,
+		x7,
+		x8,
+		x9,
+		x10,
+		x11,
+		x12,
+		x13,
+		x14,
+		x15
+	];
+	const out = new Uint8Array(feedForward ? 64 : 32);
+	if (feedForward) {
+		for (let i = 0; i < 16; i++) store32(out, 4 * i, x[i] + j[i] | 0);
+		return out;
+	}
+	const picks = [
+		0,
+		5,
+		10,
+		15,
+		6,
+		7,
+		8,
+		9
+	];
+	for (let i = 0; i < 8; i++) store32(out, 4 * i, x[picks[i]]);
+	return out;
+}
+/**
+* The XSalsa20 keystream for a 24-byte nonce: an HSalsa20 subkey from the
+* nonce's first 16 bytes, then Salsa20 blocks over the remaining 8 bytes plus
+* a little-endian 64-bit block counter.
+*/
+function xsalsa20Stream(length, nonce, key) {
+	const subkey = salsa20Core(key, nonce.subarray(0, 16), false);
+	const input = /* @__PURE__ */ new Uint8Array(16);
+	input.set(nonce.subarray(16, 24));
+	const stream = new Uint8Array(length);
+	for (let block = 0; block * 64 < length; block++) {
+		store32(input, 8, block);
+		const chunk = salsa20Core(subkey, input, true);
+		stream.set(chunk.subarray(0, Math.min(64, length - block * 64)), block * 64);
+	}
+	return stream;
+}
+const P1305 = (1n << 130n) - 5n;
+const CLAMP = 21267647620597763993911028882763415551n;
+const MASK128 = (1n << 128n) - 1n;
+function leToBigInt(b) {
+	let v = 0n;
+	for (let i = b.length - 1; i >= 0; i--) v = v << 8n | BigInt(b[i]);
+	return v;
+}
+function poly1305(msg, key) {
+	const r = leToBigInt(key.subarray(0, 16)) & CLAMP;
+	const s = leToBigInt(key.subarray(16, 32));
+	let acc = 0n;
+	for (let i = 0; i < msg.length; i += 16) {
+		const block = msg.subarray(i, Math.min(i + 16, msg.length));
+		acc = (acc + leToBigInt(block) + (1n << BigInt(8 * block.length))) * r % P1305;
+	}
+	acc = acc + s & MASK128;
+	const tag = /* @__PURE__ */ new Uint8Array(16);
+	for (let i = 0; i < 16; i++) {
+		tag[i] = Number(acc & 255n);
+		acc >>= 8n;
+	}
+	return tag;
+}
+/**
+* Seal `plaintext` under a 24-byte `nonce` and 32-byte `key`, returning the
+* 16-byte Poly1305 tag followed by the ciphertext (the NaCl box layout).
+*/
+function seal(plaintext, nonce, key) {
+	const stream = xsalsa20Stream(32 + plaintext.length, nonce, key);
+	const out = new Uint8Array(16 + plaintext.length);
+	for (let i = 0; i < plaintext.length; i++) out[16 + i] = plaintext[i] ^ stream[32 + i];
+	out.set(poly1305(out.subarray(16), stream.subarray(0, 32)));
+	return out;
+}
+//#endregion
+//#region src/core/realtime-crypto.ts
+const ENCRYPTED_CHANNEL_PREFIX = "private-encrypted-";
+function isEncryptedChannel(name) {
+	return name.startsWith(ENCRYPTED_CHANNEL_PREFIX);
+}
+/**
+* Decode and validate the configured master key: 32 bytes, base64. Validated
+* here so a bad key fails with a message naming the config, not a cipher
+* internals error at publish time.
+*/
+function decodeMasterKey(masterKey) {
+	if (!masterKey) throw new BirdError("Publishing to a private-encrypted- channel requires the encryption master key. Set `realtime: { encryptionMasterKey }` on the client — generate one as 32 random bytes, base64-encoded.");
+	let decoded = null;
+	try {
+		decoded = Uint8Array.from(atob(masterKey), (c) => c.charCodeAt(0));
+	} catch {
+		decoded = null;
+	}
+	if (!decoded || decoded.length !== 32) throw new BirdError("realtime.encryptionMasterKey must be 32 bytes, base64-encoded.");
+	return decoded;
+}
+/** SHA-256(channel_name || master_key) — the channel's secretbox key. */
+async function deriveSharedSecret(channelName, masterKey) {
+	const channel = new TextEncoder().encode(channelName);
+	const input = new Uint8Array(channel.length + masterKey.length);
+	input.set(channel);
+	input.set(masterKey, channel.length);
+	return new Uint8Array(await crypto.subtle.digest("SHA-256", input));
+}
+/** Encrypt an event payload for one encrypted channel. */
+async function encryptForChannel(channelName, data, masterKey) {
+	const key = await deriveSharedSecret(channelName, masterKey);
+	const nonce = crypto.getRandomValues(/* @__PURE__ */ new Uint8Array(24));
+	const box = seal(new TextEncoder().encode(JSON.stringify(data ?? null)), nonce, key);
+	return {
+		nonce: toBase64(nonce),
+		ciphertext: toBase64(box)
+	};
+}
+/** `hex(HMAC-SHA256(secret, payload))` — the channel-auth signature. */
+async function hmacSha256Hex(secret, payload) {
+	const key = await crypto.subtle.importKey("raw", new TextEncoder().encode(secret), {
+		name: "HMAC",
+		hash: "SHA-256"
+	}, false, ["sign"]);
+	const sig = new Uint8Array(await crypto.subtle.sign("HMAC", key, new TextEncoder().encode(payload)));
+	return Array.from(sig, (b) => b.toString(16).padStart(2, "0")).join("");
+}
+function toBase64(bytes) {
+	let raw = "";
+	for (const b of bytes) raw += String.fromCharCode(b);
+	return btoa(raw);
+}
+//#endregion
 //#region src/resources/realtime.ts
 /**
 * `bird.realtime` — publish events to a Realtime app's channels and inspect its
@@ -5253,17 +6565,111 @@ var RealtimeResource = class extends RealtimeResourceBase {
 	channels;
 	/** Members — `bird.realtime.members.send(...)`, `.disconnect(...)`. */
 	members;
-	constructor(core, client) {
+	#options;
+	constructor(core, client, options) {
 		super(core, client);
 		this.channels = new RealtimeChannelsResource(core, client);
 		this.members = new RealtimeMembersResource(core, client);
+		this.#options = options;
+	}
+	/**
+	* Publish, with end-to-end encryption when the channel asks for it: a
+	* `private-encrypted-` channel's payload is sealed locally under the
+	* configured master key before the request leaves the process. One channel
+	* per encrypted publish — each channel derives its own key, so a fan-out
+	* would deliver ciphertext other channels' subscribers cannot open.
+	*
+	* @example Publish to an encrypted channel
+	* // Client config: realtime: { key, secret, encryptionMasterKey }
+	* await bird.realtime.publish("rap_01krdgeqcxet5s7t44vh8rt9mg", {
+	*   event: "order.updated",
+	*   channels: ["private-encrypted-orders"],
+	*   data: { order_id: "ord_123", status: "shipped" },
+	* });
+	*/
+	publish(realtimeAppId, params, options) {
+		const encrypted = params.channels.filter(isEncryptedChannel);
+		if (encrypted.length === 0) return super.publish(realtimeAppId, params, options);
+		if (params.channels.length > 1) throw new BirdError("A publish to a private-encrypted- channel must name exactly that one channel: every channel derives its own key, so a multi-channel publish would hand the other channels undecryptable ciphertext. Publish per channel instead.");
+		const masterKey = decodeMasterKey(this.#options?.encryptionMasterKey);
+		return this.call("POST", options, async ({ signal, headers }) => {
+			const body = {
+				...params,
+				data: await encryptForChannel(encrypted[0], params.data, masterKey)
+			};
+			return publishRealtimeAppEvent({
+				client: this.client,
+				path: { realtime_app_id: realtimeAppId },
+				body,
+				headers,
+				signal
+			});
+		}, ["RealtimeKey", "RealtimeSecret"]);
+	}
+	/**
+	* Publish a batch, sealing each event addressed to a `private-encrypted-`
+	* channel under that channel's derived key (batch events carry one channel
+	* each, so items encrypt independently).
+	*/
+	publishBatch(realtimeAppId, params, options) {
+		if (!params.events.some((e) => isEncryptedChannel(e.channel))) return super.publishBatch(realtimeAppId, params, options);
+		const masterKey = decodeMasterKey(this.#options?.encryptionMasterKey);
+		return this.call("POST", options, async ({ signal, headers }) => {
+			const events = await Promise.all(params.events.map(async (e) => isEncryptedChannel(e.channel) ? {
+				...e,
+				data: await encryptForChannel(e.channel, e.data, masterKey)
+			} : e));
+			return publishRealtimeAppBatch({
+				client: this.client,
+				path: { realtime_app_id: realtimeAppId },
+				body: {
+					...params,
+					events
+				},
+				headers,
+				signal
+			});
+		}, ["RealtimeKey", "RealtimeSecret"]);
+	}
+	/**
+	* Sign a channel subscription for the browser client — the body your auth
+	* endpoint returns. Runs locally (no request): the signature is
+	* `HMAC-SHA256(secret, "<connectionId>:<channelName>[:<memberData>]")`,
+	* prefixed with the app key. For a presence channel pass `memberData`, the
+	* exact JSON string carrying `member_id` (and optionally `member_info`) —
+	* it is signed and echoed byte-identical. For a `private-encrypted-`
+	* channel the response also carries the channel's `shared_secret`, derived
+	* from the configured encryption master key.
+	*
+	* @example An Express auth endpoint
+	* app.post("/bird/auth", async (req, res) => {
+	*   const { connection_id, channel_name } = req.body;
+	*   if (!mayJoin(req.session.user, channel_name)) return res.sendStatus(403);
+	*   res.json(
+	*     await bird.realtime.authorizeChannel({
+	*       connectionId: connection_id,
+	*       channelName: channel_name,
+	*     }),
+	*   );
+	* });
+	*/
+	async authorizeChannel(params) {
+		const { key, secret } = this.#options ?? {};
+		if (!key || !secret) throw new BirdError("authorizeChannel signs with the Realtime app credentials. Set `realtime: { key, secret }` on the client.");
+		const out = { auth: `${key}:${await hmacSha256Hex(secret, params.memberData === void 0 ? `${params.connectionId}:${params.channelName}` : `${params.connectionId}:${params.channelName}:${params.memberData}`)}` };
+		if (params.memberData !== void 0) out.member_data = params.memberData;
+		if (isEncryptedChannel(params.channelName)) {
+			const masterKey = decodeMasterKey(this.#options?.encryptionMasterKey);
+			out.shared_secret = toBase64(await deriveSharedSecret(params.channelName, masterKey));
+		}
+		return out;
 	}
 };
 //#endregion
 //#region src/resources/lookup.gen.ts
 var LookupResource = class extends Resource {
 	/**
-	* Look up what a phone number is. Returns the serving network, the issuing network, whether the number was ported, its country, and its line type, free with every call. Pass `type` to buy extra blocks: `classification` (the allocated service of the range, from an intelligence source, reported beside the free `line_type` rather than replacing it), `porting` (whether the number ever moved network, when, and its full history), `presence` (reachable on the network right now), `roaming`, `sim_swap` (when the SIM last changed), and `score` (0-100 credibility). Every requested block reports its own status, and only the ones reading `ok` are billed on top of the lookup. Nothing is sent to the number.
+	* Create a lookup for a phone number's networks, porting state, country, and line type. Pass `type` to request separately billed `classification`, `porting`, `presence`, `roaming`, `sim_swap`, or `score` blocks. Each block reports its own status, and only blocks with an `ok` status add a charge; the lookup does not contact the number.
 	*
 	* @example Look up a number, buying two extra blocks
 	* const answer = await bird.lookup.phoneNumber({
@@ -5283,7 +6689,7 @@ var LookupResource = class extends Resource {
 		}));
 	}
 	/**
-	* Look up whether an email address is worth sending to. Returns `result` (the verdict: `valid`; `neutral`, meaning it could not be confirmed either way; `risky`, meaning it will probably accept mail but is likelier than most to bounce or complain; `undeliverable`; or `typo`), `delivery_confidence` (0-100), `flags` (`role`, `disposable`, `free_provider`), `reason` on an undeliverable address (`invalid_syntax`, `invalid_domain`, `invalid_recipient`), and `did_you_mean` when the address looks like a misspelling of a real one. `result` and `reason` are OPEN vocabularies: the values listed here are today's and more may be added, so treat an unrecognized value as a future one rather than an error, falling back on `delivery_confidence`. One address per call. Every answered lookup is billed the same flat amount whatever the verdict, so treat it as a paid call rather than a free check, and use an `Idempotency-Key` so a retry does not buy a second answer. Nothing is sent to the address.
+	* Create a deliverability lookup for one email address. Returns `result`, `delivery_confidence`, address `flags`, an undeliverable `reason`, and `did_you_mean` when a correction is available. Treat unknown `result` and `reason` values as valid additions and use `delivery_confidence` as the fallback; each completed lookup incurs the same charge.
 	*
 	* @example Check whether an address is worth sending to
 	* const answer = await bird.lookup.email({ email: "aisha.khan@example.com" });
@@ -5317,8 +6723,8 @@ function resolveRawRequestUrl(baseUrl, path) {
 	return url;
 }
 /**
-* The Bird API client. Construct it with an API key; the region is taken from
-* the key's prefix (`bk_{region}_…`) — pass `baseUrl` or `region` to override.
+* The Bird API client. Construct it with an API key. The region comes from the
+* key's prefix (`bk_{region}_…`). Pass `baseUrl` or `region` to override it.
 *
 * @example Construct and send
 * const bird = new BirdClient({ apiKey: process.env.BIRD_API_KEY! });
@@ -5330,7 +6736,7 @@ function resolveRawRequestUrl(baseUrl, path) {
 * });
 * console.log(msg.id);
 *
-* @example Channel defaults — set common send fields once; a per-send value always wins
+* @example Set channel defaults once; a per-send value always wins
 * const bird = new BirdClient({
 *   apiKey: process.env.BIRD_API_KEY!,
 *   email: { from: "hello@acme.com", category: "transactional" },
@@ -5341,8 +6747,8 @@ function resolveRawRequestUrl(baseUrl, path) {
 * @example All client options
 * const bird = new BirdClient({
 *   apiKey: process.env.BIRD_API_KEY!,
-*   region: "eu1", // optional — override the region from the key prefix
-*   baseUrl: "http://localhost:8080", // optional — overrides region entirely (local/self-hosted)
+*   region: "eu1", // optional; overrides the region from the key prefix
+*   baseUrl: "http://localhost:8080", // optional; overrides region (local or self-hosted)
 *   timeout: 60_000, // per-attempt timeout in ms (default 60_000)
 *   maxRetries: 2, // retry budget for transient failures (default 2)
 * });
@@ -5353,31 +6759,35 @@ var BirdClient = class {
 	#baseUrl;
 	#fetch;
 	#headers;
-	/** The email channel — `bird.email.send(...)`, `.get(...)`, `.list(...)`. */
+	/** Email channel: `bird.email.send(...)`, `.get(...)`, `.list(...)`. */
 	email;
-	/** The SMS channel — `bird.sms.send(...)`, `.get(...)`, `.list(...)`. */
+	/** SMS channel: `bird.sms.send(...)`, `.get(...)`, `.list(...)`. */
 	sms;
-	/** SMS templates — `bird.smsTemplates.list(...)`, `.get(...)`. */
+	/** SMS templates: `bird.smsTemplates.list(...)`, `.get(...)`. */
 	smsTemplates;
-	/** The WhatsApp channel — `bird.whatsapp.send(...)`, `.get(...)`, `.list(...)`, `.listEvents(...)`. */
+	/** SMS suppressions: `bird.smsSuppressions.list(...)`, `.add(...)`, `.remove(...)`. */
+	smsSuppressions;
+	/** SMS keyword rules: `bird.smsKeywordRules.list(...)`, `.create(...)`, … */
+	smsKeywordRules;
+	/** WhatsApp channel: `bird.whatsapp.send(...)`, `.get(...)`, `.list(...)`, `.listEvents(...)`. */
 	whatsapp;
-	/** The Voice call log — `bird.voice.list(...)`, `.get(...)`. Calls are placed by your own SIP equipment, so this is a read surface. */
+	/** Voice call log: `bird.voice.list(...)`, `.get(...)`. Your SIP equipment places calls, so this is a read surface. */
 	voice;
-	/** The Verify product — `bird.verify.verifications.create(...)`, `.check(...)`. */
+	/** Verify: `bird.verify.verifications.create(...)`, `.check(...)`. */
 	verify;
-	/** Contacts — `bird.contacts.create(...)`, `.list(...)`, `.get(...)`, `.batch(...)`, … */
+	/** Contacts: `bird.contacts.create(...)`, `.list(...)`, `.get(...)`, `.batch(...)`, … */
 	contacts;
-	/** Audiences — `bird.audiences.create(...)`, `.list(...)`, `.addContacts(...)`, … */
+	/** Audiences: `bird.audiences.create(...)`, `.list(...)`, `.addContacts(...)`, … */
 	audiences;
-	/** Contact properties — `bird.contactProperties.create(...)`, `.list(...)`, `.archive(...)`, … */
+	/** Contact properties: `bird.contactProperties.create(...)`, `.list(...)`, `.archive(...)`, … */
 	contactProperties;
-	/** Sending domains — `bird.domains.create(...)`, `.list(...)`, `.verify(...)`, … */
+	/** Sending domains: `bird.domains.create(...)`, `.list(...)`, `.verify(...)`, … */
 	domains;
-	/** Recipient intelligence — `bird.lookup.email(...)`, `.phoneNumber(...)`. Every answer is billed. */
+	/** Recipient intelligence: `bird.lookup.email(...)`, `.phoneNumber(...)`. Every answer is billed. */
 	lookup;
-	/** Webhooks — `bird.webhooks.unwrap(payload, headers)` verifies an inbound delivery. */
+	/** Webhooks: `bird.webhooks.unwrap(payload, headers)` verifies an inbound delivery. */
 	webhooks;
-	/** Realtime — `bird.realtime.publish(...)`, `.channels.list(...)`, `.members.disconnect(...)`, … */
+	/** Realtime: `bird.realtime.publish(...)`, `.channels.list(...)`, `.members.disconnect(...)`, … */
 	realtime;
 	constructor(options) {
 		const opts = options;
@@ -5386,9 +6796,9 @@ var BirdClient = class {
 		this.#headers = {
 			...opts.defaultHeaders,
 			Authorization: `Bearer ${opts.apiKey}`,
-			"User-Agent": `bird-sdk-js/0.28.0`,
+			"User-Agent": `bird-sdk-js/0.30.0`,
 			"Bird-Surface": "sdk-js",
-			"Bird-Version": "0.28.0"
+			"Bird-Version": "0.30.0"
 		};
 		const caller = detectCaller();
 		if (caller) this.#headers["Bird-Caller"] = caller;
@@ -5416,6 +6826,8 @@ var BirdClient = class {
 		this.email = new EmailResource(this.core, this.#client, opts.email);
 		this.sms = new SmsResource(this.core, this.#client);
 		this.smsTemplates = new SmsTemplatesResource(this.core, this.#client);
+		this.smsSuppressions = new SmsSuppressionsResource(this.core, this.#client);
+		this.smsKeywordRules = new SmsKeywordRulesResource(this.core, this.#client);
 		this.whatsapp = new WhatsappResource(this.core, this.#client);
 		this.voice = new VoiceResource(this.core, this.#client);
 		this.verify = new VerifyResource(this.core, this.#client);
@@ -5425,7 +6837,7 @@ var BirdClient = class {
 		this.domains = new DomainsResource(this.core, this.#client);
 		this.lookup = new LookupResource(this.core, this.#client);
 		this.webhooks = new WebhooksResource(opts.webhooks);
-		this.realtime = new RealtimeResource(this.core, this.#client);
+		this.realtime = new RealtimeResource(this.core, this.#client, opts.realtime);
 	}
 	/**
 	* Escape hatch for endpoints the typed resources don't cover. Runs the full
@@ -5435,7 +6847,7 @@ var BirdClient = class {
 	* @throws {TypeError} if `req.path` does not start with exactly one `/` or
 	*   resolves to a different origin than the configured Bird API base URL.
 	*
-	* @example Reach an endpoint outside the curated surface — you supply the response type
+	* @example Reach an endpoint outside the curated surface. Supply the response type
 	* type Suppressions = { data: Array<{ recipient: string }> };
 	* const suppressions = await bird.request<Suppressions>({ method: "GET", path: "/v1/email/suppressions" });
 	* console.log(suppressions.data.length);
@@ -5529,6 +6941,7 @@ const WebhookEventType = {
 	WhatsappDelivered: "whatsapp.delivered",
 	WhatsappFailed: "whatsapp.failed",
 	WhatsappRead: "whatsapp.read",
+	WhatsappReceived: "whatsapp.received",
 	WhatsappRejected: "whatsapp.rejected",
 	WhatsappSent: "whatsapp.sent"
 };
@@ -5622,6 +7035,80 @@ const SMSErrorCode = {
 	Unreachable: "unreachable"
 };
 /**
+* Values of SMSKeywordOperation known at this SDK version. The wire value is an open
+* string: a value added by a newer server deserializes unchanged, so switch on
+* these with a `default` branch rather than treating the set as closed.
+*/
+const SMSKeywordOperation = {
+	Custom: "custom",
+	Help: "help",
+	Start: "start",
+	Stop: "stop"
+};
+/**
+* Values of SMSSuppressionCoverage known at this SDK version. The wire value is an open
+* string: a value added by a newer server deserializes unchanged, so switch on
+* these with a `default` branch rather than treating the set as closed.
+*/
+const SMSSuppressionCoverage = {
+	All: "all",
+	NonTransactional: "non_transactional"
+};
+/**
+* Values of SMSSuppressionEndReason known at this SDK version. The wire value is an open
+* string: a value added by a newer server deserializes unchanged, so switch on
+* these with a `default` branch rather than treating the set as closed.
+*/
+const SMSSuppressionEndReason = {
+	ApiKey: "api_key",
+	CarrierCleared: "carrier_cleared",
+	KeywordStart: "keyword_start",
+	User: "user"
+};
+/**
+* Values of SMSSuppressionOrigin known at this SDK version. The wire value is an open
+* string: a value added by a newer server deserializes unchanged, so switch on
+* these with a `default` branch rather than treating the set as closed.
+*/
+const SMSSuppressionOrigin = {
+	ApiKey: "api_key",
+	DlrEvent: "dlr_event",
+	Keyword: "keyword",
+	User: "user"
+};
+/**
+* Values of SMSSuppressionReason known at this SDK version. The wire value is an open
+* string: a value added by a newer server deserializes unchanged, so switch on
+* these with a `default` branch rather than treating the set as closed.
+*/
+const SMSSuppressionReason = {
+	CarrierOptedOut: "carrier_opted_out",
+	KeywordStop: "keyword_stop",
+	Manual: "manual"
+};
+/**
+* Values of TemplateLanguageStatus known at this SDK version. The wire value is an open
+* string: a value added by a newer server deserializes unchanged, so switch on
+* these with a `default` branch rather than treating the set as closed.
+*/
+const TemplateLanguageStatus = {
+	Draft: "draft",
+	Live: "live",
+	Superseded: "superseded"
+};
+/**
+* Values of TemplateStatus known at this SDK version. The wire value is an open
+* string: a value added by a newer server deserializes unchanged, so switch on
+* these with a `default` branch rather than treating the set as closed.
+*/
+const TemplateStatus = {
+	Active: "active",
+	Draft: "draft",
+	Inactive: "inactive",
+	Pending: "pending",
+	Rejected: "rejected"
+};
+/**
 * Values of VerificationAttemptFailureReason known at this SDK version. The wire value is an open
 * string: a value added by a newer server deserializes unchanged, so switch on
 * these with a `default` branch rather than treating the set as closed.
@@ -5643,6 +7130,7 @@ const VerificationAttemptFailureReason = {
 const VerificationChannel = {
 	Email: "email",
 	Sms: "sms",
+	Telegram: "telegram",
 	Whatsapp: "whatsapp"
 };
 /**
@@ -5669,6 +7157,20 @@ const WhatsAppErrorCode = {
 	Undeliverable: "undeliverable"
 };
 /**
+* Values of WhatsAppEventType known at this SDK version. The wire value is an open
+* string: a value added by a newer server deserializes unchanged, so switch on
+* these with a `default` branch rather than treating the set as closed.
+*/
+const WhatsAppEventType = {
+	WhatsappAccepted: "whatsapp.accepted",
+	WhatsappDelivered: "whatsapp.delivered",
+	WhatsappFailed: "whatsapp.failed",
+	WhatsappRead: "whatsapp.read",
+	WhatsappReceived: "whatsapp.received",
+	WhatsappRejected: "whatsapp.rejected",
+	WhatsappSent: "whatsapp.sent"
+};
+/**
 * Values of WhatsAppTemplateCategory known at this SDK version. The wire value is an open
 * string: a value added by a newer server deserializes unchanged, so switch on
 * these with a `default` branch rather than treating the set as closed.
@@ -5692,6 +7194,6 @@ const WhatsAppTemplateParameterType = {
 	Video: "video"
 };
 //#endregion
-export { BirdAPIError, BirdAuthError, BirdBadRequestError, BirdBillingError, BirdClient, BirdConflictError, BirdConnectionError, BirdError, BirdInternalError, BirdMisdirectedError, BirdNotFoundError, BirdNotImplementedError, BirdPayloadTooLargeError, BirdPermissionError, BirdPreconditionError, BirdRateLimitError, BirdServiceUnavailableError, BirdTimeoutError, BirdValidationError, BirdWebhookVerificationError, EmailEventType, EmailLookupFlag, EmailLookupReason, EmailLookupResult, LookupFlag, LookupPropertyStatus, SMSErrorCode, VerificationAttemptFailureReason, VerificationChannel, VerificationTerminalReason, WebhookEventType, WhatsAppErrorCode, WhatsAppTemplateCategory, WhatsAppTemplateParameterType, baseUrlForRegion, regionFromApiKey };
+export { BirdAPIError, BirdAuthError, BirdBadRequestError, BirdBillingError, BirdClient, BirdConflictError, BirdConnectionError, BirdError, BirdInternalError, BirdMisdirectedError, BirdNotFoundError, BirdNotImplementedError, BirdPayloadTooLargeError, BirdPermissionError, BirdPreconditionError, BirdRateLimitError, BirdServiceUnavailableError, BirdTimeoutError, BirdValidationError, BirdWebhookVerificationError, EmailEventType, EmailLookupFlag, EmailLookupReason, EmailLookupResult, LookupFlag, LookupPropertyStatus, SMSErrorCode, SMSKeywordOperation, SMSSuppressionCoverage, SMSSuppressionEndReason, SMSSuppressionOrigin, SMSSuppressionReason, TemplateLanguageStatus, TemplateStatus, VerificationAttemptFailureReason, VerificationChannel, VerificationTerminalReason, WebhookEventType, WhatsAppErrorCode, WhatsAppEventType, WhatsAppTemplateCategory, WhatsAppTemplateParameterType, baseUrlForRegion, regionFromApiKey };
 
 //# sourceMappingURL=index.mjs.map