@messagebird/sdk 0.16.0 → 0.21.2

package/dist/index.d.mts

@@ -36,10 +36,27 @@ interface CoreDefaults {
   timeout: number;
   /** Max retry attempts. */
   maxRetries: number;
+  /**
+   * Extra credentials some operations require on top of the API key, keyed by the
+   * security scheme that names them. A generated method names the schemes its
+   * operation declares; the core resolves them, so a credential reaches only
+   * those operations and never an unrelated request.
+   */
+  credentials?: Record<string, {
+    header: string;
+    value?: string;
+    how: string;
+  }>;
 }
 declare class BirdHTTPClient {
   private readonly defaults;
   constructor(defaults: CoreDefaults);
+  /**
+   * Resolve the credential headers an operation's security schemes require.
+   * Throws before the request when one is unconfigured, so a caller gets a named
+   * error instead of a 401.
+   */
+  credentialHeaders(schemes: string[] | undefined, override?: Record<string, string>): Record<string, string>;
   /**
    * Run a generated hey-api SDK call through the request lifecycle.
    *
@@ -206,6 +223,12 @@ declare class BirdRateLimitError extends BirdAPIError {
 //#region src/core/result.d.ts
 /** Per-request overrides accepted by every resource method. */
 interface RequestOptions {
+  /**
+   * Per-call override for the extra credentials an operation requires, keyed by
+   * security scheme (`{ RealtimeKey: "…", RealtimeSecret: "…" }`). Overrides the
+   * client config for this call, so one client can address several apps.
+   */
+  credentials?: Record<string, string>;
   /** Idempotency key; auto-generated for mutations if omitted, reused on retry. */
   idempotencyKey?: string;
   /** Caller cancellation. Rejects with the native `AbortError`. */
@@ -323,11 +346,11 @@ type EventWhatsAppBase = {
    */
   direction: "outbound" | "inbound";
   /**
-   * Sender of the message. On outbound messages, the business number it was sent from.
+   * Sender of the message. On outbound messages, the business number it was sent from; on inbound, the WhatsApp contact.
    */
   from: WhatsAppAddress;
   /**
-   * Recipient of the message. On outbound messages, the WhatsApp contact.
+   * Recipient of the message. On outbound messages, the WhatsApp contact; on inbound, the business number.
    */
   to: WhatsAppAddress;
   /**
@@ -370,12 +393,12 @@ type EventWhatsAppRejectedData = EventWhatsAppBase & {
  * Failure reason, uniform whether the failure happened internally or was reported by the WhatsApp network. `insufficient_balance`: the workspace could not afford the send. `price_not_found`: no price was configured for this destination/template combination. `internal_error`: an unexpected Bird-side failure. `undeliverable`: the recipient could not be reached (for example not on WhatsApp, or the number is invalid). `service_window_expired`: the 24-hour customer care window has closed and a free-form message cannot be sent; send a template instead. `rate_limited`: the send was throttled. `recipient_suppressed`: the recipient is on the workspace's suppression list; the message was rejected before sending. Open enum: new codes may be added over time, so treat any unrecognized value as a future code rather than an error.
  *
  */
-type WhatsAppErrorCode = string;
+type WhatsAppErrorCode$1 = "insufficient_balance" | "price_not_found" | "internal_error" | "undeliverable" | "service_window_expired" | "rate_limited" | "recipient_suppressed" | (string & {});
 /**
  * Failure detail for a message that could not be delivered or was rejected.
  */
 type WhatsAppError = {
-  code: WhatsAppErrorCode;
+  code: WhatsAppErrorCode$1;
   /**
    * Human-readable explanation of the failure.
    */
@@ -390,7 +413,7 @@ type WhatsAppError = {
   readonly occurred_at: string;
 } | null;
 /**
- * Bird rejected the message before sending it to WhatsApp (the recipient is on the workspace suppression list).
+ * Bird rejected the message before sending it to WhatsApp (the recipient is on the workspace suppression list, the wallet had insufficient balance, or the destination is unpriced). It was not sent and not charged.
  */
 type EventWhatsAppRejected = {
   /**
@@ -510,11 +533,11 @@ type EventVoiceBase = {
   /**
    * Calling party number in E.164 format.
    */
-  src_number: string;
+  from: string;
   /**
    * Called party number in E.164 format.
    */
-  dst_number: string;
+  to: string;
 };
 /**
  * A call was initiated — Bird received the INVITE and began routing it.
@@ -600,7 +623,7 @@ type EventVerifyVerificationVerifiedData = EventVerifyBase & {
   /**
    * The channel whose passcode the recipient confirmed, the channel that converted. Null when the verification was resolved without attributing a channel.
    */
-  channel: VerificationChannel | null;
+  channel: VerificationChannel$1 | null;
   /**
    * Time the verification was verified.
    */
@@ -609,7 +632,7 @@ type EventVerifyVerificationVerifiedData = EventVerifyBase & {
 /**
  * The channel a passcode is delivered over. Open enum — new channels may be added over time, so treat any unrecognized value as a future channel rather than an error.
  */
-type VerificationChannel = string;
+type VerificationChannel$1 = "email" | "sms" | "whatsapp" | (string & {});
 /**
  * The recipient to verify. Provide an `email_address`, a `phone_number`, or both; at least one is required. The addresses also identify the verification: a check must supply exactly the set used on the create call, so a verification created with both addresses is not found by either one alone.
  *
@@ -670,7 +693,7 @@ type EventVerifyVerificationCreatedData = EventVerifyBase & {
   /**
    * The first channel of the verification's resolved channel plan.
    */
-  channel: VerificationChannel;
+  channel: VerificationChannel$1;
   /**
    * The verification's state at creation, always `pending`. Open enum for forward compatibility.
    */
@@ -695,9 +718,9 @@ type EventVerifyVerificationCreated = {
   data: EventVerifyVerificationCreatedData;
 };
 /**
- * Why a passcode send did not deliver. Open enum — new reasons may be added over time, so treat any unrecognized value as a future reason rather than an error. Emitted reasons are `carrier_rejected` (SMS), `hard_bounce` (email, permanent bounce), `soft_bounce` (email, transient bounce such as a full mailbox), `undelivered` (a generic delivery failure), and `channel_unavailable` (the channel could not be used and the verification failed over).
+ * Why a passcode send did not deliver. Open enum — new reasons may be added over time, so treat any unrecognized value as a future reason rather than an error. Emitted reasons are `carrier_rejected` (SMS), `hard_bounce` (email, permanent bounce), `soft_bounce` (email, transient bounce such as a full mailbox), `undelivered` (a generic delivery failure), `channel_unavailable` (the channel could not be used and the verification failed over), and `channel_disabled` (Bird has temporarily stopped sending over that channel, so the verification moved on to the next one).
  */
-type VerificationAttemptFailureReason = string;
+type VerificationAttemptFailureReason$1 = "carrier_rejected" | "hard_bounce" | "soft_bounce" | "undelivered" | "channel_unavailable" | "channel_disabled" | (string & {});
 /**
  * Payload of the verify.attempt.undelivered event.
  */
@@ -705,7 +728,7 @@ type EventVerifyAttemptUndeliveredData = EventVerifyBase & {
   /**
    * The channel this attempt was sent on.
    */
-  channel: VerificationChannel;
+  channel: VerificationChannel$1;
   /**
    * The single address this attempt was dispatched to, an E.164 phone number or an email address.
    */
@@ -713,7 +736,7 @@ type EventVerifyAttemptUndeliveredData = EventVerifyBase & {
   /**
    * Why the attempt failed to reach the recipient.
    */
-  reason: VerificationAttemptFailureReason;
+  reason: VerificationAttemptFailureReason$1;
   /**
    * Diagnostic text describing the failure, for display only. Null when none was reported.
    */
@@ -744,7 +767,7 @@ type EventVerifyAttemptSentData = EventVerifyBase & {
   /**
    * The channel this attempt was sent on.
    */
-  channel: VerificationChannel;
+  channel: VerificationChannel$1;
   /**
    * The single address this attempt was dispatched to, an E.164 phone number or an email address.
    */
@@ -779,7 +802,7 @@ type EventVerifyAttemptDeliveredData = EventVerifyBase & {
   /**
    * The channel this attempt was sent on.
    */
-  channel: VerificationChannel;
+  channel: VerificationChannel$1;
   /**
    * The single address this attempt was dispatched to, an E.164 phone number or an email address.
    */
@@ -891,110 +914,6 @@ type EventSmsUndelivered = {
   timestamp: string;
   data: EventSmsUndeliveredData;
 };
-/**
- * Payload of the sms.tfn_verification.submitted event.
- */
-type EventSmsTfnVerificationSubmittedData = EventSmsTfnVerificationBase;
-type SmsSenderId = string;
-type TfnVerificationId = string;
-/**
- * Identity fields shared by every toll-free verification event payload.
- */
-type EventSmsTfnVerificationBase = {
-  /**
-   * ID of the toll-free verification.
-   */
-  verification_id: TfnVerificationId;
-  /**
-   * ID of the workspace that owns the verification.
-   */
-  workspace_id: WorkspaceId;
-  /**
-   * Lifecycle state of the verification at the time of the event.
-   */
-  status: string;
-  /**
-   * ID of the toll-free number the verification licenses.
-   */
-  sender_id: SmsSenderId;
-};
-/**
- * A toll-free number verification was submitted to the carrier for review.
- */
-type EventSmsTfnVerificationSubmitted = {
-  /**
-   * Event type.
-   */
-  type: "sms.tfn_verification.submitted";
-  /**
-   * Time the verification was submitted.
-   */
-  timestamp: string;
-  data: EventSmsTfnVerificationSubmittedData;
-};
-/**
- * Payload of the sms.tfn_verification.rejected event.
- */
-type EventSmsTfnVerificationRejectedData = EventSmsTfnVerificationBase & {
-  /**
-   * Human-readable reasons the carrier gave for the rejection.
-   */
-  denial_reasons: Array<string>;
-  /**
-   * Whether the verification may be corrected and resubmitted within the resubmission window.
-   */
-  resubmit_allowed: boolean;
-};
-/**
- * The carrier rejected a toll-free number verification; the number cannot send until an accepted verification is approved.
- */
-type EventSmsTfnVerificationRejected = {
-  /**
-   * Event type.
-   */
-  type: "sms.tfn_verification.rejected";
-  /**
-   * Time the rejection was recorded.
-   */
-  timestamp: string;
-  data: EventSmsTfnVerificationRejectedData;
-};
-/**
- * Payload of the sms.tfn_verification.info_requested event.
- */
-type EventSmsTfnVerificationInfoRequestedData = EventSmsTfnVerificationBase;
-/**
- * The carrier requested more information before deciding a toll-free number verification.
- */
-type EventSmsTfnVerificationInfoRequested = {
-  /**
-   * Event type.
-   */
-  type: "sms.tfn_verification.info_requested";
-  /**
-   * Time the information request was recorded.
-   */
-  timestamp: string;
-  data: EventSmsTfnVerificationInfoRequestedData;
-};
-/**
- * Payload of the sms.tfn_verification.approved event.
- */
-type EventSmsTfnVerificationApprovedData = EventSmsTfnVerificationBase;
-/**
- * The carrier approved a toll-free number verification; the number can now send in its licensed countries.
- */
-type EventSmsTfnVerificationApproved = {
-  /**
-   * Event type.
-   */
-  type: "sms.tfn_verification.approved";
-  /**
-   * Time the approval was recorded.
-   */
-  timestamp: string;
-  data: EventSmsTfnVerificationApprovedData;
-};
 /**
  * Payload of the sms.sent event.
  */
@@ -2034,14 +1953,6 @@ type WebhookEvent = ({
 } & EventSmsRejected) | ({
   type: "sms.sent";
 } & EventSmsSent) | ({
-  type: "sms.tfn_verification.approved";
-} & EventSmsTfnVerificationApproved) | ({
-  type: "sms.tfn_verification.info_requested";
-} & EventSmsTfnVerificationInfoRequested) | ({
-  type: "sms.tfn_verification.rejected";
-} & EventSmsTfnVerificationRejected) | ({
-  type: "sms.tfn_verification.submitted";
-} & EventSmsTfnVerificationSubmitted) | ({
   type: "sms.undelivered";
 } & EventSmsUndelivered) | ({
   type: "verify.attempt.delivered";
@@ -2879,7 +2790,7 @@ type MailboxUpdate = {
    */
   receive_policy?: "open" | "replies_only" | "allowlist" | "drop";
   /**
-   * How long the mailbox remembers message metadata and extracted text. Lowering the tier deletes memory older than the new horizon and requires `confirm=true` when messages older than the new horizon would be deleted. Only `30d` is available today; longer tiers (`90d`, `1y`, and beyond) are coming soon.
+   * How long the mailbox remembers message metadata and extracted text. Lowering the tier deletes memory older than the new horizon and requires `confirm=true` when messages older than the new horizon would be deleted. Only `30d` is available today; additional tiers are planned.
    */
   retention_tier?: "30d";
   /**
@@ -2914,7 +2825,7 @@ type MailboxCreate = {
    */
   receive_policy?: "open" | "replies_only" | "allowlist" | "drop";
   /**
-   * How long the mailbox remembers message metadata and extracted text. Original rendered source is always available for 30 days regardless of tier. Only `30d` is available today; longer tiers (`90d`, `1y`, and beyond) are coming soon.
+   * How long the mailbox remembers message metadata and extracted text. Original rendered source is always available for 30 days regardless of tier. Only `30d` is available today; additional tiers are planned.
    */
   retention_tier?: "30d";
   /**
@@ -3070,7 +2981,7 @@ type DomainDkimConfig = {
   mode?: "txt" | "delegated";
 };
 /**
- * Tracking domain configuration for branded open and click tracking URLs. Provide only the name part; Bird adds the sending domain automatically. Defaults to `links` when omitted at creation. Tracked links are served over HTTPS once the tracking record verifies.
+ * Tracking domain configuration for branded open and click tracking URLs. Provide only the name part; Bird adds the sending domain automatically. A domain created with no tracking configuration defaults to the name `links`. Tracked links are served over HTTPS once the tracking record verifies.
  *
  */
 type DomainTrackingConfig = {
@@ -3347,44 +3258,6 @@ type EmailStatsByBroadcastResponse = {
    */
   readonly total: number;
 };
-/**
- * One point in a breakdown row's trend series: the headline delivery and engagement rates for that row's dimension value over a single day or hour. Returned only when `include_trend=true`; the bucket grain (day or hour) follows the `trend_grain` parameter. Counts and rates are approximate at scale.
- *
- */
-type EmailStatsSeriesPoint = {
-  /**
-   * The day (YYYY-MM-DD) or hour (ISO 8601, on the hour) this point covers, matching the requested `trend_grain`.
-   */
-  readonly bucket: string;
-  /**
-   * Delivered recipients in this bucket.
-   */
-  readonly delivered: number;
-  /**
-   * Bounced recipients in this bucket.
-   */
-  readonly bounced: number;
-  /**
-   * Delivery rate for this bucket, as a fraction. Null when nothing was delivered or bounced.
-   */
-  readonly delivery_rate: number | null;
-  /**
-   * Bounce rate for this bucket, as a fraction. Null when nothing was delivered or bounced.
-   */
-  readonly bounce_rate: number | null;
-  /**
-   * Complaint rate for this bucket, as a fraction; event-time attribution can push it above 1 when complaints outrun the bucket's deliveries. Null when nothing was delivered in the bucket. On a sending-IP row complaints are not attributed to the IP, so this reads 0 in buckets that had deliveries and null in buckets that had none.
-   */
-  readonly complaint_rate: number | null;
-  /**
-   * Open rate for this bucket, as a fraction; event-time attribution can push it above 1 when opens outrun the bucket's deliveries. Null when nothing was delivered in the bucket. On a sending-IP row engagement is not attributed to the IP, so this reads 0 in buckets that had deliveries and null in buckets that had none.
-   */
-  readonly open_rate: number | null;
-  /**
-   * Click rate for this bucket, as a fraction; event-time attribution can push it above 1 when clicks outrun the bucket's deliveries. Null when nothing was delivered in the bucket. On a sending-IP row engagement is not attributed to the IP, so this reads 0 in buckets that had deliveries and null in buckets that had none.
-   */
-  readonly click_rate: number | null;
-};
 /**
  * Aggregate delivery, engagement, and latency stats for the messages of a single broadcast over the requested period.
  */
@@ -3396,10 +3269,6 @@ type EmailBroadcastStatsPoint = {
   readonly delivery: EmailDeliveryStats;
   readonly engagement: EmailEngagementStats;
   readonly latency: EmailLatencyStats;
-  /**
-   * Per-bucket rate series for this broadcast over the window. Never returned today, because `include_trend` is not available for the broadcast breakdown (supplying it returns 422).
-   */
-  readonly trend?: Array<EmailStatsSeriesPoint>;
 };
 /**
  * The date range the server actually computed against. Echoed back so clients can render the period without tracking it themselves and so cached responses can be keyed by what was queried.
@@ -3645,6 +3514,44 @@ type EmailStatsByTemplateResponse = {
    */
   readonly total: number;
 };
+/**
+ * One point in a breakdown row's trend series: the headline delivery and engagement rates for that row's dimension value over a single day or hour. Returned only when `include_trend=true`; the bucket grain (day or hour) follows the `trend_grain` parameter. Counts and rates are approximate at scale.
+ *
+ */
+type EmailStatsSeriesPoint = {
+  /**
+   * The day (YYYY-MM-DD) or hour (ISO 8601, on the hour) this point covers, matching the requested `trend_grain`.
+   */
+  readonly bucket: string;
+  /**
+   * Delivered recipients in this bucket.
+   */
+  readonly delivered: number;
+  /**
+   * Bounced recipients in this bucket.
+   */
+  readonly bounced: number;
+  /**
+   * Delivery rate for this bucket, as a fraction. Null when nothing was delivered or bounced.
+   */
+  readonly delivery_rate: number | null;
+  /**
+   * Bounce rate for this bucket, as a fraction. Null when nothing was delivered or bounced.
+   */
+  readonly bounce_rate: number | null;
+  /**
+   * Complaint rate for this bucket, as a fraction; event-time attribution can push it above 1 when complaints outrun the bucket's deliveries. Null when nothing was delivered in the bucket. On a sending-IP row complaints are not attributed to the IP, so this reads 0 in buckets that had deliveries and null in buckets that had none.
+   */
+  readonly complaint_rate: number | null;
+  /**
+   * Open rate for this bucket, as a fraction; event-time attribution can push it above 1 when opens outrun the bucket's deliveries. Null when nothing was delivered in the bucket. On a sending-IP row engagement is not attributed to the IP, so this reads 0 in buckets that had deliveries and null in buckets that had none.
+   */
+  readonly open_rate: number | null;
+  /**
+   * Click rate for this bucket, as a fraction; event-time attribution can push it above 1 when clicks outrun the bucket's deliveries. Null when nothing was delivered in the bucket. On a sending-IP row engagement is not attributed to the IP, so this reads 0 in buckets that had deliveries and null in buckets that had none.
+   */
+  readonly click_rate: number | null;
+};
 type EmailTemplateId = string;
 /**
  * Aggregate delivery, engagement, and latency stats for the messages sent with a single template over the requested period.
@@ -4060,7 +3967,7 @@ type EmailStatsComparisonDelta = {
   readonly unsubscribe_rate_pp: number | null;
 };
 /**
- * The same statistics for the equal-length, inclusive period ending the day immediately before the requested start, together with the change between the two periods. Present only when `compare=previous_period` is requested. Use it to render "+X% vs last period" without issuing a second request.
+ * The same statistics for the equal-length, inclusive period ending the day immediately before the requested start, together with the change between the two periods. Present only when `compare=previous_period` is requested. The change is already computed, so a percentage difference needs no second request.
  *
  */
 type EmailStatsComparison = {
@@ -4178,7 +4085,7 @@ type WhatsAppEvent = {
    */
   readonly id: WhatsAppEventId;
   /**
-   * Lifecycle event type. `whatsapp.accepted`: Bird accepted the request. `whatsapp.sent`: handed to the WhatsApp network. `whatsapp.delivered`: delivery confirmed to the recipient's device. `whatsapp.read`: the recipient opened the message (this does not change the message `status`, which never becomes `read`). `whatsapp.failed`: terminal permanent failure. Open enum: new event types may be added over time, so treat any unrecognized value as a future event rather than an error.
+   * Lifecycle event type. `whatsapp.accepted`: Bird accepted the request. `whatsapp.sent`: handed to the WhatsApp network. `whatsapp.delivered`: delivery confirmed to the recipient's device. `whatsapp.read`: the recipient opened the message (this does not change the message `status`, which never becomes `read`). `whatsapp.failed`: terminal permanent failure. `whatsapp.rejected`: Bird refused the message before sending it, so it was never charged. `whatsapp.received`: an inbound message arrived from the contact. Open enum: new event types may be added over time, so treat any unrecognized value as a future event rather than an error.
    *
    */
   readonly type: string;
@@ -4187,18 +4094,22 @@ type WhatsAppEvent = {
    */
   readonly occurred_at: string;
   /**
-   * Failure detail. Present only on `whatsapp.failed` events.
+   * Failure detail. Present only on `whatsapp.failed` and `whatsapp.rejected` events.
    */
   error?: WhatsAppError;
 };
+/**
+ * A WhatsApp message to send. Carry exactly one kind of content: a request with none returns a `422` `WhatsAppContentRequired`, and one carrying more than one returns a `422` `WhatsAppContentAmbiguous`. The schema does not express that constraint, because which combinations are available depends on the content types your workspace can send.
+ *
+ */
 type WhatsAppMessageSendRequest = {
   /**
-   * The message recipient's phone number in E.164 format (for example `+31612345678`). A value that is not a valid phone number returns a `422` `WhatsAppInvalidRecipient`.
+   * The message recipient: a phone number in E.164 format (for example `+31612345678`), or the recipient's business-scoped user ID (for example `US.13491208655302741918`), which addresses a WhatsApp user whose phone number you do not have. A value that is neither returns a `422` `WhatsAppInvalidRecipient`. One-time-passcode templates require a phone number and return a `422` `WhatsAppRecipientNotSupportedForTemplate` when sent to a business-scoped user ID.
    *
    */
   to: string;
   /**
-   * The template to send. Bird selects the sender number from the template's category, so there is no sender field on this request. Templates are the only supported content type today: a request without one is rejected with a `422`.
+   * The template to send. For a Bird-managed template, Bird selects the sender number from the template's category, so `from` must be omitted. A template is the only content deliverable outside a customer service window.
    *
    */
   template?: WhatsAppTemplateSend;
@@ -4219,18 +4130,19 @@ type WhatsAppMessageSendRequest = {
  * The kind of value a template parameter accepts. `text` (the only kind today) is a plain string substituted into the placeholder. Open enum: more kinds may be added over time.
  *
  */
-type WhatsAppTemplateParameterType = string;
+type WhatsAppTemplateParameterType$1 = "text" | (string & {});
 type WhatsAppMessageTemplateComponentParameter = {
   /**
    * The kind of value this parameter carries. `text` is the only kind today.
    */
-  type: WhatsAppTemplateParameterType;
+  type: WhatsAppTemplateParameterType$1;
   /**
    * The value substituted into the placeholder, as a plain string.
    */
   text: string;
   /**
-   * For named-parameter templates: the placeholder this value fills (for example `first_name`). Omit for positional templates.
+   * Required when the template declares named parameters: the placeholder this value fills (for example `first_name`), matching exactly one of the names the template declares. Name every parameter in that case; order does not matter once names are supplied. Omit this field for a positional template, which takes its values in `{{n}}` order instead. Sending the wrong set of names, or leaving one out that the template requires, returns a `422` `WhatsAppTemplateParameterMismatch`.
+   *
    */
   name?: string;
 };
@@ -4241,32 +4153,37 @@ type WhatsAppMessageTemplateComponent = {
    */
   type: string;
   /**
-   * The values that fill this part's placeholders, in `{{n}}` placeholder order.
+   * The values that fill this part's placeholders. A positional template takes them in `{{n}}` placeholder order; a template with named parameters requires each parameter's `name` to match one the template declares, and order then carries no meaning.
    *
    */
   parameters?: Array<WhatsAppMessageTemplateComponentParameter>;
 };
 /**
- * Language code of the template variant (for example `en` or `pt_BR`).
+ * A language tag in BCP-47 form, for example `en` or `pt-BR`.
  */
-type WhatsAppLanguage = string;
+type LanguageTag = string;
 /**
  * A template's slug: its permanent, workspace-unique handle and API address. Lowercase letters, numbers, hyphens, and underscores. Fixed at creation, so anything that references it never breaks; the display name is the label to change freely.
  *
  */
 type TemplateSlug = string;
-type WhatsAppTemplateSend = {
+type WhatsAppTemplateId = string;
+type WhatsAppTemplateSend = unknown & {
+  /**
+   * The template to send, by its id.
+   */
+  id?: WhatsAppTemplateId;
   /**
    * The template to send, by its slug (for example `bird_otp`).
    */
-  slug: TemplateSlug;
+  slug?: TemplateSlug;
   /**
-   * Language code of the template variant to send (for example `en` or `pt_BR`). May be omitted when the template has a single language; when it is stocked in several, omitting the language returns a `422` that names the available codes. The accepted message echoes the resolved language.
+   * Which of the template's languages to send, as a BCP-47 tag (for example `en` or `pt-BR`). Meta's underscore form (`pt_BR`) is accepted and normalized; the accepted message echoes the canonical BCP-47 form. May be omitted when the template has a single language; when it is stocked in several, omitting the language returns a `422` that names the available tags.
    *
    */
-  language?: WhatsAppLanguage;
+  language?: LanguageTag;
   /**
-   * The values that fill the template's placeholders: one entry per content block that has placeholders, each carrying its `parameters` in `{{n}}` order. Parameter counts must match the template's declared placeholders exactly, or the send returns a `422` `WhatsAppTemplateParameterMismatch`.
+   * The values that fill the template's placeholders: one entry per content block that has placeholders, each carrying its `parameters`. A positional template takes its parameters in `{{n}}` order; a template with named parameters requires each parameter's `name` to match one the template declares. Either way, sending parameters that do not match what the template declares returns a `422` `WhatsAppTemplateParameterMismatch`.
    *
    */
   components?: Array<WhatsAppMessageTemplateComponent>;
@@ -4286,7 +4203,7 @@ type Money = {
   currency_code: CurrencyCode;
 };
 /**
- * Delivery status. `accepted` (the initial status of an outbound send) means Bird accepted the request and it is queued for sending. `sent` means it was handed to the WhatsApp network. `delivered` is confirmed delivery to the recipient's device. `failed` is a terminal permanent failure. `rejected` means the recipient is on the workspace's suppression list; the message was not sent and not charged. There is no `read` status: a read receipt is reported as `read_at` and a `whatsapp.read` event, not a status value. The remaining values are reserved and not returned today: `scheduled` (queued to send at a future time), `canceled` (a scheduled message canceled before sending), and `received` (an inbound message, `direction: inbound`, sent to you by a contact).
+ * Delivery status. `accepted` (the initial status of an outbound send) means Bird accepted the request and it is queued for sending. `sent` means it was handed to the WhatsApp network. `delivered` is confirmed delivery to the recipient's device. `failed` is a terminal permanent failure. `rejected` means Bird refused the message before sending it to WhatsApp, because the recipient is on the workspace's suppression list, the wallet had insufficient balance, or the destination is unpriced. A rejected message was not sent and not charged. There is no `read` status: a read receipt is reported as `read_at` and a `whatsapp.read` event, not a status value. The remaining values are reserved and not returned today: `scheduled` (queued to send at a future time), `canceled` (a scheduled message canceled before sending), and `received` (a message a contact sent you).
  *
  */
 type WhatsAppMessageStatus = "scheduled" | "accepted" | "sent" | "delivered" | "failed" | "rejected" | "canceled" | "received";
@@ -4294,7 +4211,7 @@ type WhatsAppMessageStatus = "scheduled" | "accepted" | "sent" | "delivered" | "
  * Meta's content classification for a template. `authentication` templates deliver one-time passcodes, `utility` templates deliver transaction-triggered updates (receipts, order status), and `marketing` templates carry promotional content. The category drives which sender number Bird selects and how the send is priced. Open enum: Meta may add new categories over time, so treat any unrecognized value as a future category rather than an error.
  *
  */
-type WhatsAppTemplateCategory = string;
+type WhatsAppTemplateCategory$1 = "authentication" | "utility" | "marketing" | (string & {});
 /**
  * The template a message was sent from. On reads `slug`, `language`, `category`, and `components` are always present; `components` is an empty array for an authentication template (the filled-in values, for example a verification code, are never returned).
  *
@@ -4307,11 +4224,11 @@ type WhatsAppMessageTemplate = {
   /**
    * Content classification applied to messages sent from this template.
    */
-  readonly category: WhatsAppTemplateCategory;
+  readonly category: WhatsAppTemplateCategory$1;
   /**
-   * The language code of the template variant that was sent (for example `en`).
+   * The canonical BCP-47 tag of the template variant that was sent.
    */
-  readonly language: string;
+  readonly language: LanguageTag;
   /**
    * The values that filled the template's placeholders. Empty for an authentication template, whose content is never returned.
    *
@@ -4389,12 +4306,12 @@ type VerificationCheckResult = {
   readonly attempts_remaining?: number | null;
 };
 type VerificationChannelEntry = {
-  channel: VerificationChannel;
+  channel: VerificationChannel$1;
 };
 /**
  * Why a verification session reached its final state without succeeding: `attempts_exhausted` (too many incorrect passcodes) or `ttl_elapsed` (the time window elapsed before a correct passcode). Open enum — new reasons may be added over time, so treat any unrecognized value as a future reason rather than an error.
  */
-type VerificationTerminalReason = string;
+type VerificationTerminalReason$1 = "attempts_exhausted" | "ttl_elapsed" | (string & {});
 type Verification = {
   readonly id: VerificationId;
   /**
@@ -4404,7 +4321,7 @@ type Verification = {
   /**
    * Why the verification reached its final state, or null while `pending` and once `verified`. See the enum for the values it can take.
    */
-  readonly reason?: VerificationTerminalReason | null;
+  readonly reason?: VerificationTerminalReason$1 | null;
   readonly to: VerificationTo;
   /**
    * The channels this verification uses to deliver the passcode, in attempt order: the first entry is tried first and later entries are fallbacks. An email recipient is verified over email; a phone recipient is verified over SMS.
@@ -4457,7 +4374,7 @@ type VerificationOptions = {
   /**
    * Reorder or narrow the delivery channels for this request. List channel names in the order to try them; a channel you omit is not used for this request, and a channel not already enabled for the recipient is ignored. A list that leaves no usable channel fails the request with `422`. Omit the field to use the configured order.
    */
-  channels?: Array<VerificationChannel>;
+  channels?: Array<VerificationChannel$1>;
 };
 /**
  * Bucket grain for a stats trend series.
@@ -4493,6 +4410,11 @@ type TemplateVariable = {
    * A human-readable description of the accepted values.
    */
   readonly constraint: string;
+  /**
+   * Whether this slot's value is redacted before it reaches storage. A sensitive slot's rendered value never appears in message content read back through the API: a stand-in placeholder is stored instead.
+   *
+   */
+  readonly sensitive?: boolean;
 };
 /**
  * Content classification. Tells Bird and carriers why you're sending; per-country compliance rules (opt-out policy, quiet hours) key on it as they roll out.
@@ -4666,7 +4588,7 @@ type SmsMessage = {
    */
   from: string;
   /**
-   * The message body as sent. For a template send, this is the rendered text after parameter substitution.
+   * The message body as sent. For a template send, this is the rendered text after parameter substitution. When `category` is `authentication` (a message carrying a one-time code), this is `**REDACTED**`: the code still reaches the recipient, Bird just does not persist it for later reads.
    *
    */
   text: string;
@@ -4736,10 +4658,10 @@ type SmsTemplateSend = unknown & {
    */
   name?: TemplateName;
   /**
-   * Language tag (BCP 47, for example `fr` or `pt-BR`) selecting the localized body. Falls back to the closest available language, then English, when the exact tag is not stocked. Omit for English.
+   * Which of the template's localized bodies to send, as a BCP-47 tag. Falls back to the closest available language, then English, when the exact tag is not stocked. Omit for English.
    *
    */
-  language?: string;
+  language?: LanguageTag;
   /**
    * Values for the template's variables, keyed by variable name. The accepted keys and their formats are fixed per template (the template's `variables` on the templates endpoint). A missing required variable, an undeclared key, a value that does not match its variable's format, or a serialized payload over 16 KB each return a `422`.
    *
@@ -4867,20 +4789,19 @@ type AudienceRef = {
    */
   name: string;
 };
-/**
- * A channel a contact can be reached on. Open enum: `email` is present when the contact has an email address; more values (`sms`, `whatsapp`, `voice`) are added as contacts gain identifiers for other channels. Treat any unrecognized value as a future channel rather than an error. Slugs match `ChannelSlug`.
- *
- */
-type ContactChannel = string;
 type Contact = {
   /**
    * ID of the contact (`con_`-prefixed), accepted by every operation that takes a `contact_id`.
    */
   readonly id: ContactId;
   /**
-   * The contact's email address, stored trimmed and lowercased. Unique within the workspace.
+   * The contact's email address, in its stored form, trimmed and lowercased before uniqueness is checked. Unique within the workspace. Null when the contact has no email address.
    */
-  email: string;
+  email: string | null;
+  /**
+   * The contact's phone number in normalized international form (a leading `+` and four to 15 digits), which may differ from the form it was supplied in. Bird normalizes formatting but does not verify the number against numbering-plan metadata. Unique within the workspace. Carriers recycle disconnected numbers, so a long-stored number can come to belong to someone else; `external_id` is the durable key for your own records. Null when the contact has no phone number.
+   */
+  phone: string | null;
   /**
    * The contact's first name. Available in broadcast templates as the `contact.first_name` variable.
    */
@@ -4894,17 +4815,12 @@ type Contact = {
    */
   external_id?: string | null;
   /**
-   * Custom property values for this contact, available as template variables in broadcasts. Each key is a property created via the contact properties API, and each value is a string, number, or boolean matching the property's declared type (strings up to 500 characters). Total size is capped at 2 KB serialized. Values stored under a property that was later archived remain readable here.
+   * Custom property values for this contact, available as template variables in broadcasts. Each key is a property created via the contact properties API, and each value is a string, number, boolean, or RFC 3339 datetime matching the property's declared type (strings up to 500 characters). Total size is capped at 2 KB serialized. Values stored under a property that was later archived remain readable here.
    *
    */
   data?: {
     [key: string]: unknown;
   };
-  /**
-   * Channels this contact can be reached on, derived from the identifiers it has. A contact with an email address includes `email`. More values are added as a contact gains identifiers for other channels.
-   *
-   */
-  readonly channels?: Array<ContactChannel>;
 } & Timestamps;
 type AudienceMember = {
   contact: Contact;
@@ -4944,7 +4860,7 @@ type AudienceCreateRequest = {
 };
 type ContactPropertyUpdateRequest = {
   /**
-   * Default used when a contact has no value for this property and the template does not supply an inline fallback. A string, number, or boolean matching the declared type (strings up to 500 characters); a value of another type returns a validation error. Set to null to remove the fallback.
+   * Default used when a contact has no value for this property and the template does not supply an inline fallback. A string, number, boolean, or RFC 3339 datetime matching the declared type (strings up to 500 characters); a value of another type returns a validation error. Set to null to remove the fallback.
    */
   fallback_value?: unknown;
 };
@@ -4955,14 +4871,17 @@ type ContactPropertyCreateRequest = {
   key: string;
   type: ContactPropertyType;
   /**
-   * Default used when a contact has no value for this property and the template does not supply an inline fallback. A string, number, or boolean matching the declared type (strings up to 500 characters), or null for no fallback; a value of another type returns a validation error.
+   * Default used when a contact has no value for this property and the template does not supply an inline fallback. A string, number, boolean, or RFC 3339 datetime matching the declared type (strings up to 500 characters), or null for no fallback; a value of another type returns a validation error.
    */
   fallback_value?: unknown;
 };
 /**
  * The value type every contact must use for a property. Cannot be changed after creation.
+ *
+ * `datetime` values are RFC 3339 timestamps with an explicit offset (for example `2024-01-15T09:30:00Z` or `2024-01-15T11:30:00+02:00`); a bare date or a time with no offset is rejected. The value is normalized to UTC with second precision on write, so `2024-01-15T11:30:00+02:00` is stored and returned as `2024-01-15T09:30:00Z`, and any fractional seconds are dropped.
+ *
  */
-type ContactPropertyType = "string" | "number" | "boolean";
+type ContactPropertyType = "string" | "number" | "boolean" | "datetime";
 type ContactPropertyId = string;
 type ContactProperty = {
   /**
@@ -4975,7 +4894,7 @@ type ContactProperty = {
   key: string;
   type: ContactPropertyType;
   /**
-   * Default used when a contact has no value for this property and the template does not supply an inline fallback. A string, number, or boolean matching the declared type (strings up to 500 characters), or null when no fallback is set.
+   * Default used when a contact has no value for this property and the template does not supply an inline fallback. A string, number, boolean, or RFC 3339 datetime matching the declared type (strings up to 500 characters), or null when no fallback is set.
    */
   fallback_value?: unknown;
   /**
@@ -5004,9 +4923,13 @@ type Audience = {
 } & Timestamps;
 type ContactUpdateRequest = {
   /**
-   * New email address for the contact. Trimmed and lowercased before it is stored and checked for uniqueness. Must not be in use by another contact in the workspace. Omit to keep the current address; a contact's email cannot be removed.
+   * New email address for the contact. Trimmed and lowercased before it is stored and checked for uniqueness. Must not be in use by another contact in the workspace. Omit to keep the current address; set to null to remove it, as long as the contact keeps at least one identifier.
    */
-  email?: string;
+  email?: string | null;
+  /**
+   * New phone number for the contact, in E.164 format with the leading `+` and country code. Spaces and punctuation are accepted and stripped. Stored in its canonical form, which may differ from what you send, and unique within the workspace. Omit to keep the current number; set to null to remove it, as long as the contact keeps at least one identifier. An empty string behaves as null.
+   */
+  phone?: string | null;
   /**
    * The contact's first name. Set to null to clear.
    */
@@ -5020,7 +4943,7 @@ type ContactUpdateRequest = {
    */
   external_id?: string | null;
   /**
-   * Custom property values to change, merged into the contact's existing data. Keys you supply are set, keys set to null are removed, and keys you omit are left unchanged. Each key must be a property created via the contact properties API, and each value must be a string, number, or boolean matching the property's declared type (strings up to 500 characters); writing an unregistered or archived key returns a validation error. The merged result is capped at 2 KB serialized.
+   * Custom property values to change, merged into the contact's existing data. Keys you supply are set, keys set to null are removed, and keys you omit are left unchanged. Each key must be a property created via the contact properties API, and each value must be a string, number, boolean, or RFC 3339 datetime matching the property's declared type (strings up to 500 characters); writing an unregistered or archived key returns a validation error. The merged result is capped at 2 KB serialized.
    *
    */
   data?: {
@@ -5038,16 +4961,42 @@ type ContactUpsertError = {
    * Machine-readable error category for this entry, such as `validation_error` or `conflict_error`, in the same vocabulary as the top-level error `type`. New categories may be added over time, so treat unrecognized values as a generic failure.
    */
   type: string;
+  /**
+   * The specific error code for this entry, from the same catalog as the top-level error `code`: the discriminator within a category. `E04058` (the entry matched two different contacts, a human must decide) and `E04055` (the phone belongs to another contact, retry with different data) are both `conflict_error`; the code tells a sync which one it hit.
+   */
+  code: string;
   /**
    * Human-readable explanation of why this entry failed.
    */
   message: string;
 };
+/**
+ * Which identifier matched a batch entry to an existing contact. Null when the entry created a new contact.
+ */
+type ContactMatchedOn = "email" | "phone" | "external_id" | null;
+/**
+ * The identifiers a batch entry supplied, in the normalized form they were matched with, null where the entry carried none. An echo of the request row for correlation, never the contact's current state.
+ */
+type ContactUpsertEntry = {
+  /**
+   * Email address this entry carried, trimmed and lowercased. Null when the entry carried none.
+   */
+  email: string | null;
+  /**
+   * Phone number this entry carried, in its normalized international form. Null when the entry carried none. A row rejected for an invalid phone echoes the value as sent, trimmed, since no normalized form exists.
+   */
+  phone: string | null;
+  /**
+   * Your own identifier for this entry, when the entry supplied one.
+   */
+  external_id: string | null;
+};
 type ContactUpsertResultItem = {
+  entry: ContactUpsertEntry;
   /**
-   * Email address this entry refers to, in the normalized (trimmed and lowercased) form it was matched and stored as.
+   * Which identifier matched this entry to an existing contact. Null when the entry created a new contact.
    */
-  email: string;
+  matched_on: ContactMatchedOn;
   /**
    * What happened to this contact. `created` means a new contact was created for the address; `updated` means an existing contact with the address was updated; `failed` means the entry was rejected and `error` explains why. A failed entry does not affect the other entries in the request.
    */
@@ -5063,24 +5012,37 @@ type ContactUpsertResultItem = {
 };
 type ContactUpsertRequest = {
   /**
-   * Contacts to create or update, matched by email address. Existing contacts are updated with the fields each entry supplies; omitted fields keep their stored values, so an entry can set fields but never clear them. New addresses create contacts.
+   * Contacts to create or update, matched automatically against every identifier an entry supplies. Existing contacts are updated with the fields each entry supplies; omitted fields keep their stored values, so an entry can set fields but never clear them. Unmatched entries create contacts.
    */
   contacts: Array<ContactCreateRequest>;
   /**
    * Audiences every contact in this request is added to. Contacts that are already members are left in place. Every listed audience must exist, or the whole request fails with a validation error and nothing is written.
    */
   audience_ids?: Array<AudienceId>;
+  /**
+   * Optional. Forces every entry to be matched to an existing contact by this one field, which every entry must then carry. When omitted, each entry is matched automatically against every identifier it supplies: no match creates a contact, one match updates it, and an entry whose identifiers belong to more than one contact fails with an error naming each.
+   *
+   */
+  match_on?: ContactMatchKey;
   /**
    * How a supplied `data` object is applied to an existing contact. `merge` (the default) merges the supplied keys onto the contact's stored custom values, and a key with a `null` value deletes that one key. `replace` overwrites the whole stored `data` map with the supplied one. In both modes a contact that omits `data` keeps its stored values unchanged, so an import that touches one attribute never wipes the others.
    *
    */
   data_mode?: "merge" | "replace";
 };
+/**
+ * A contact identifier a batch entry can be matched on.
+ */
+type ContactMatchKey = "email" | "phone" | "external_id";
 type ContactCreateRequest = {
   /**
-   * The contact's email address. Trimmed and lowercased before it is stored and checked for uniqueness. Unique within the workspace.
+   * The contact's email address. Trimmed and lowercased before it is stored and checked for uniqueness. Unique within the workspace. Supply an email address, a phone number, or both.
    */
-  email: string;
+  email?: string;
+  /**
+   * The contact's phone number in E.164 format, including the leading `+` and country code. Spaces and punctuation are accepted and stripped; the number is stored in its canonical form, which may differ from what you send, and is unique within the workspace. An empty string is treated as if the field were omitted. Supply an email address, a phone number, or both.
+   */
+  phone?: string;
   /**
    * The contact's first name.
    */
@@ -5094,7 +5056,7 @@ type ContactCreateRequest = {
    */
   external_id?: string;
   /**
-   * Custom property values for this contact. Each key must be a property created via the contact properties API, and each value must be a string, number, or boolean matching the property's declared type (strings up to 500 characters); a null value is ignored. Unregistered or archived keys are rejected with a validation error. Total size is capped at 2 KB serialized.
+   * Custom property values for this contact. Each key must be a property created via the contact properties API, and each value must be a string, number, boolean, or RFC 3339 datetime matching the property's declared type (strings up to 500 characters); a null value is ignored. Unregistered or archived keys are rejected with a validation error. Total size is capped at 2 KB serialized.
    *
    */
   data?: {
@@ -5107,6 +5069,7 @@ type EmailMessageBatchResponse = {
    */
   data: Array<EmailMessageBatchItem>;
 };
+type EmailTemplateVersionId = string;
 type EmailMessageBatchItem = {
   /**
    * Message ID assigned to this batch item.
@@ -5120,16 +5083,32 @@ type EmailMessageBatchItem = {
    * Resolved category for this batch item.
    */
   category: "marketing" | "transactional";
+  /**
+   * The template language this item asked for, in canonical form. Null when the item named no language or used no template. Every item in a batch resolves its own template reference, so this and `resolved_language` can differ from item to item.
+   *
+   */
+  readonly requested_language?: LanguageTag | null;
+  /**
+   * The template language this item was actually delivered in, in canonical form. Null when the item used no template. A value here differing from `requested_language` means the template did not carry the language asked for and its `on_missing_language` policy chose this one.
+   *
+   */
+  readonly resolved_language?: LanguageTag | null;
+  /**
+   * The template this item rendered from, or null for an item that supplied its content inline.
+   *
+   */
+  readonly template_id?: EmailTemplateId | null;
+  /**
+   * The exact template version this item rendered from, or null for an inline item. Record it if you need to reproduce what was sent: a template's live version changes every time you submit it.
+   *
+   */
+  readonly template_version_id?: EmailTemplateVersionId | null;
 };
 /**
  * Batch of email message send requests. All items are validated before any are queued. Attachments are allowed on individual messages. Each message must stay within the 20 MB estimated generated message-size cap. The serialized JSON request body for the batch has a hard 20 MB cap.
  *
  */
 type EmailMessageBatchRequest = Array<EmailMessageSendRequest>;
-/**
- * A language tag in BCP-47 form, for example `en` or `pt-BR`.
- */
-type LanguageTag = string;
 type EmailTemplateSend = unknown & {
   /**
    * The template to send, by its id.
@@ -5145,7 +5124,7 @@ type EmailTemplateSend = unknown & {
    */
   language?: LanguageTag;
   /**
-   * Values for the template's variables, keyed by variable name. A token with no matching value renders empty. Send everything the template's `variables` lists rather than only what you expect the chosen language to use: languages need not reference the same variables, and a value no language uses is ignored. Cap: 16 KB serialized.
+   * Values for the template's variables, keyed by variable name. A token with no matching value renders empty. Nest values to fill dotted tokens: `{"contact": {"first_name": "Ada"}}` fills `{{ contact.first_name }}`. Send everything the template's `variables` lists rather than only what you expect the chosen language to use: languages need not reference the same variables, and a value no language uses is ignored. Cap: 16 KB serialized.
    *
    */
   parameters?: {
@@ -5401,6 +5380,26 @@ type EmailMessage = {
    * Total click events across all recipients.
    */
   readonly click_count: number;
+  /**
+   * The template language this send asked for, in canonical form (`pt-BR` for a request of `pt-br`). Null when the send named no language (it took the template's default) or used no template at all. Compare it with `resolved_language`: when they differ, the language you asked for was not available and the template's `on_missing_language` policy chose the one shown there instead.
+   *
+   */
+  readonly requested_language?: LanguageTag | null;
+  /**
+   * The template language this send was actually delivered in, in canonical form. Null when the send used no template. A non-null value with a null `requested_language` means the send named no language and took the template's default.
+   *
+   */
+  readonly resolved_language?: LanguageTag | null;
+  /**
+   * The template this send rendered from, or null for a send that supplied its content inline.
+   *
+   */
+  readonly template_id?: EmailTemplateId | null;
+  /**
+   * The exact template version this send rendered from, or null for an inline send. A template's live version changes every time you submit it, so this is what identifies the wording that was actually delivered, together with `resolved_language`.
+   *
+   */
+  readonly template_version_id?: EmailTemplateVersionId | null;
   /**
    * Structured `{name, value}` filter labels applied to this send. See EmailMessageSendRequest for the tags vs metadata distinction.
    */
@@ -5412,7 +5411,7 @@ type EmailMessage = {
     [key: string]: unknown;
   };
   /**
-   * The substitution values this send supplied, or null for a send that carried its content inline. They are the values applied to `subject` and to the bodies the content endpoint returns, kept so you can see what produced the delivered copy and not only the result.
+   * The substitution values this send supplied, whether inline or from a template, or null if none were supplied. They are the values applied to `subject` and to the bodies the content endpoint returns, kept so you can see what produced the delivered copy and not only the result.
    *
    */
   readonly parameters?: {
@@ -5451,6 +5450,21 @@ type EmailMessage = {
    */
   readonly scheduled_at?: string | null;
 };
+/**
+ * An event addressed to one member rather than to a channel. Every connection that member currently holds receives it; if they hold none, the event is dropped.
+ */
+type RealtimeMemberPublish = {
+  event: RealtimeEventName;
+  data?: RealtimeEventData;
+};
+/**
+ * Arbitrary JSON payload delivered as the event data — an object, array, or scalar. Cap: 10 KB serialized.
+ */
+type RealtimeEventData = unknown;
+/**
+ * The event name clients bind to. Application event names are free-form; the `bird:` and `bird_internal:` prefixes are reserved for the protocol and rejected.
+ */
+type RealtimeEventName = string;
 /**
  * The members present on a presence channel.
  */
@@ -5532,14 +5546,6 @@ type RealtimeChannelInclude = "member_count" | "connection_count";
  * Exclude this connection from delivery, to avoid echoing a change back to the client that triggered it. The value is the client's connection id, assigned when its connection is established.
  */
 type RealtimeExcludeConnectionId = string;
-/**
- * Arbitrary JSON payload delivered as the event data — an object, array, or scalar. Cap: 10 KB serialized.
- */
-type RealtimeEventData = unknown;
-/**
- * The event name clients bind to. Application event names are free-form; the `bird:` and `bird_internal:` prefixes are reserved for the protocol and rejected.
- */
-type RealtimeEventName = string;
 /**
  * One item of a batch publish — a single event to a single channel.
  */
@@ -5582,23 +5588,73 @@ type RealtimePublish = {
   include?: Array<RealtimeChannelInclude>;
 };
 type RealtimeAppId = string;
-type ListRealtimeAppChannelsData = {
-  body?: never;
-  headers: {
+type PublishRealtimeAppEventData = {
+  body: RealtimePublish;
+  headers?: {
     /**
      * Workspace context. Required for session auth; derived from API key otherwise.
      */
     "X-Workspace-Id"?: string;
     /**
-     * The Realtime app key. With X-Realtime-Secret it authenticates the request to the Realtime edge. Both come from the app's credentials (shown once at creation) and must belong to the calling workspace.
+     * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
+     * Two distinct 409 errors signal misuse:
+     * - `request_in_progress` (E01004): the same key is currently being
+     * processed by a concurrent request. Wait briefly and retry; the lock
+     * expires within 30 seconds.
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
+     * against a different request body or method. Generate a new key.
+     *
+     * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
      *
      */
-    "X-Realtime-Key": string;
+    "Idempotency-Key"?: string;
+  };
+  path: {
     /**
-     * The Realtime app secret, paired with X-Realtime-Key. Sent over TLS and used only to sign the request to the edge — never stored. Rotate it by rotating the app key.
+     * Realtime app ID
+     */
+    realtime_app_id: RealtimeAppId;
+  };
+  query?: never;
+  url: "/v1/realtime/apps/{realtime_app_id}/events";
+};
+type PublishRealtimeAppBatchData = {
+  body: RealtimeBatchPublish;
+  headers?: {
+    /**
+     * Workspace context. Required for session auth; derived from API key otherwise.
+     */
+    "X-Workspace-Id"?: string;
+    /**
+     * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
+     * Two distinct 409 errors signal misuse:
+     * - `request_in_progress` (E01004): the same key is currently being
+     * processed by a concurrent request. Wait briefly and retry; the lock
+     * expires within 30 seconds.
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
+     * against a different request body or method. Generate a new key.
      *
+     * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
+     *
+     */
+    "Idempotency-Key"?: string;
+  };
+  path: {
+    /**
+     * Realtime app ID
+     */
+    realtime_app_id: RealtimeAppId;
+  };
+  query?: never;
+  url: "/v1/realtime/apps/{realtime_app_id}/batch-events";
+};
+type ListRealtimeAppChannelsData = {
+  body?: never;
+  headers?: {
+    /**
+     * Workspace context. Required for session auth; derived from API key otherwise.
      */
-    "X-Realtime-Secret": string;
+    "X-Workspace-Id"?: string;
   };
   path: {
     /**
@@ -5620,21 +5676,11 @@ type ListRealtimeAppChannelsData = {
 };
 type GetRealtimeAppChannelData = {
   body?: never;
-  headers: {
+  headers?: {
     /**
      * Workspace context. Required for session auth; derived from API key otherwise.
      */
     "X-Workspace-Id"?: string;
-    /**
-     * The Realtime app key. With X-Realtime-Secret it authenticates the request to the Realtime edge. Both come from the app's credentials (shown once at creation) and must belong to the calling workspace.
-     *
-     */
-    "X-Realtime-Key": string;
-    /**
-     * The Realtime app secret, paired with X-Realtime-Key. Sent over TLS and used only to sign the request to the edge — never stored. Rotate it by rotating the app key.
-     *
-     */
-    "X-Realtime-Secret": string;
   };
   path: {
     /**
@@ -5654,6 +5700,40 @@ type GetRealtimeAppChannelData = {
   };
   url: "/v1/realtime/apps/{realtime_app_id}/channels/{channel_name}";
 };
+type SendRealtimeAppMemberEventData = {
+  body: RealtimeMemberPublish;
+  headers?: {
+    /**
+     * Workspace context. Required for session auth; derived from API key otherwise.
+     */
+    "X-Workspace-Id"?: string;
+    /**
+     * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
+     * Two distinct 409 errors signal misuse:
+     * - `request_in_progress` (E01004): the same key is currently being
+     * processed by a concurrent request. Wait briefly and retry; the lock
+     * expires within 30 seconds.
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
+     * against a different request body or method. Generate a new key.
+     *
+     * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
+     *
+     */
+    "Idempotency-Key"?: string;
+  };
+  path: {
+    /**
+     * Realtime app ID
+     */
+    realtime_app_id: RealtimeAppId;
+    /**
+     * The member to deliver the event to.
+     */
+    member_id: RealtimeMemberId;
+  };
+  query?: never;
+  url: "/v1/realtime/apps/{realtime_app_id}/members/{member_id}/events";
+};
 type ListEmailMessagesData = {
   body?: never;
   path?: never;
@@ -5709,15 +5789,19 @@ type ListContactsData = {
   path?: never;
   query?: {
     /**
-     * Return the contact with exactly this email address (case-insensitive). Email is unique within a workspace, so this matches at most one contact.
+     * Return the contact with exactly this email address (case-insensitive). Email is unique within a workspace, so this matches at most one contact. An empty value is a validation error, never an unfiltered page.
      */
     email?: string;
     /**
-     * Return the contact with exactly this external_id (your own identifier for the contact). Unique within a workspace, so this matches at most one contact.
+     * Return the contact with exactly this phone number in international E.164 form. Encode the leading plus sign as `%2B` (an unencoded `+` arrives as a space and is rejected). Phone numbers are unique within a workspace, so this matches at most one contact. Non-canonical forms of the same number match the contact they canonicalize to; a value that is not a phone number shape, or an empty value, is a validation error, never an unfiltered page.
+     */
+    phone?: string;
+    /**
+     * Return the contact with exactly this external_id (your own identifier for the contact). Unique within a workspace, so this matches at most one contact. An empty value is a validation error, never an unfiltered page.
      */
     external_id?: string;
     /**
-     * Case-insensitive substring match against the contact's email address.
+     * Case-insensitive substring match against the contact's email address, first name, last name, or phone number. Phone matching is over the digits of the international form, so a full pasted number, a formatted number, or trailing digits all match; a national form with a leading trunk zero does not.
      */
     q?: string;
     /**
@@ -5732,6 +5816,10 @@ type ListContactsData = {
      * Cursor from the `prev_cursor` field of a previous list response. Returns items immediately before the cursor position in the current sort order.
      */
     ending_before?: string;
+    /**
+     * When true, the response includes a `total` field with the total number of items matching the request's filters across all pages.
+     */
+    include_total?: boolean;
   };
   url: "/v1/contacts";
 };
@@ -5741,10 +5829,10 @@ type CreateContactData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -5762,10 +5850,10 @@ type CreateContactBatchData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -5783,10 +5871,10 @@ type UpdateContactData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -5828,10 +5916,10 @@ type CreateContactPropertyData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -5849,10 +5937,10 @@ type UpdateContactPropertyData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -5898,10 +5986,10 @@ type CreateAudienceData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -5919,10 +6007,10 @@ type UpdateAudienceData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -5949,7 +6037,7 @@ type ListAudienceContactsData = {
   };
   query?: {
     /**
-     * Case-insensitive substring match against the member's email address.
+     * Case-insensitive substring match against the member's email address or phone number (digits of the international form).
      */
     q?: string;
     /**
@@ -5973,10 +6061,10 @@ type AssignAudienceContactsData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -5999,10 +6087,10 @@ type UnassignAudienceContactsData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -6108,10 +6196,10 @@ type CreateVerificationData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -6133,10 +6221,10 @@ type CreateVerificationCheckData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -6176,6 +6264,11 @@ type ListWhatsAppMessagesData = {
      * Filter by status. Repeat the parameter to match any of several statuses.
      */
     status?: Array<WhatsAppMessageStatus>;
+    /**
+     * Filter by whether the business sent the message (`outbound`) or received it from the contact (`inbound`).
+     *
+     */
+    direction?: MessageDirection;
     /**
      * Filter by contact phone number (E.164 exact match).
      */
@@ -6222,7 +6315,7 @@ type GetEmailStatsDailyData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6271,7 +6364,7 @@ type GetEmailStatsHourlyData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6320,7 +6413,7 @@ type GetEmailStatsByTagData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6364,7 +6457,7 @@ type GetEmailStatsSummaryData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6418,7 +6511,7 @@ type GetEmailStatsBySendingIpData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6460,7 +6553,7 @@ type GetEmailStatsBySendingDomainData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6502,7 +6595,7 @@ type GetEmailStatsByCategoryData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6540,7 +6633,7 @@ type GetEmailStatsByMailboxProviderData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6582,7 +6675,7 @@ type GetEmailStatsByMailboxProviderRegionData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6624,7 +6717,7 @@ type GetEmailStatsByRecipientDomainData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6666,7 +6759,7 @@ type GetEmailStatsByTemplateData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6708,7 +6801,7 @@ type GetEmailStatsByLocationData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6746,7 +6839,7 @@ type GetEmailStatsByClientData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6784,7 +6877,7 @@ type GetEmailStatsByBounceCodeData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6817,7 +6910,7 @@ type GetEmailStatsByComplaintTypeData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -6862,15 +6955,6 @@ type GetEmailStatsByBroadcastData = {
      * Maximum number of broadcast rows to return, ranked by the `sort` field descending.
      */
     limit?: number;
-    /**
-     * Requests a per-row `trend` series. Not available for the broadcast breakdown; supplying `true` returns 422.
-     *
-     */
-    include_trend?: boolean;
-    /**
-     * Bucket grain for the `trend` series. Has no effect on this breakdown, where `include_trend` is not available.
-     */
-    trend_grain?: StatsTrendGrain;
   };
   url: "/v1/email/stats/broadcasts";
 };
@@ -6916,10 +7000,10 @@ type CreateDomainData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -6937,10 +7021,10 @@ type UpdateDomainData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -7002,10 +7086,10 @@ type CreateMailboxData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -7023,10 +7107,10 @@ type UpdateMailboxData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -7068,7 +7152,7 @@ type GetMailboxStatsData = {
      */
     to?: string;
     /**
-     * IANA timezone identifier (for example `Asia/Kathmandu` or `America/New_York`) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when `from` and `to` are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a `from` or `to` given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a `from` or `to` that carries its own numeric UTC offset (for example `+05:45`) is rejected when `timezone` is set; use a calendar day or a `Z` (UTC) instant instead. Defaults to UTC.
+     * IANA timezone identifier (for example `Asia/Kathmandu`) to report in; defaults to UTC. Day and hour boundaries and the default window when `from` and `to` are omitted both follow it, so a calendar-day `from` or `to` names a local day. A `from` or `to` carrying its own UTC offset is rejected while this is set: pass a calendar day or a `Z` instant.
      *
      */
     timezone?: string;
@@ -7114,10 +7198,10 @@ type CreateMailboxReceiveRuleData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -7191,10 +7275,10 @@ type DeleteEmailThreadData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -7222,10 +7306,10 @@ type UpdateEmailThreadData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -7285,10 +7369,10 @@ type ReplyEmailThreadMessageData = {
     /**
      * Client-supplied deduplication key. When present, the server replays the original response for any duplicate request with the same key within the idempotency TTL window (3 hours by default).
      * Two distinct 409 errors signal misuse:
-     * - `request_in_progress` (E01004) — the same key is currently being
+     * - `request_in_progress` (E01004): the same key is currently being
      * processed by a concurrent request. Wait briefly and retry; the lock
      * expires within 30 seconds.
-     * - `idempotency_key_reuse` (E01005) — the same key has already completed
+     * - `idempotency_key_reuse` (E01005): the same key has already completed
      * against a different request body or method. Generate a new key.
      *
      * Recommended key format is `<event-type>/<entity-id>` (e.g. `welcome-user/usr_abc123`).
@@ -7637,16 +7721,16 @@ declare abstract class Resource {
   protected readonly client: Client;
   constructor(core: BirdHTTPClient, client: Client);
   /** Run a single typed call through the lifecycle. */
-  protected call<T>(method: string, options: RequestOptions | undefined, invoke: (ctx: CallContext) => Promise<FetchOutcome<T>>): APIPromise<T>;
+  protected call<T>(method: string, options: RequestOptions | undefined, invoke: (ctx: CallContext) => Promise<FetchOutcome<T>>, schemes?: string[]): APIPromise<T>;
   /** Run a cursor-paginated list through the lifecycle (each page retried independently). */
-  protected paginated<T>(method: string, options: RequestOptions | undefined, invoke: (ctx: CallContext, cursor: string | undefined) => Promise<FetchOutcome<CursorPage<T>>>): PaginatedPromise<T>;
+  protected paginated<T>(method: string, options: RequestOptions | undefined, invoke: (ctx: CallContext, cursor: string | undefined) => Promise<FetchOutcome<CursorPage<T>>>, schemes?: string[]): PaginatedPromise<T>;
 }
 //#endregion
 //#region src/resources/email.gen.d.ts
 type EmailListQuery$1 = NonNullable<ListEmailMessagesData["query"]>;
 declare class EmailResourceBase extends Resource {
   /**
-   * Fetch one email message by id — aggregate delivery status and per-state recipient counts. The message body (html, text) is not returned. Per-recipient delivery statuses and the event log are separate sub-resources: GET /v1/email/messages/{message_id}/recipients and GET /v1/email/messages/{message_id}/events.
+   * Fetch one email message by id, with aggregate delivery status and per-state recipient counts. The message body (html, text) is not returned. Per-recipient delivery statuses and the event log are separate sub-resources: GET /v1/email/messages/{message_id}/recipients and GET /v1/email/messages/{message_id}/events.
    *
    * @example
    * const msg = await bird.email.get("em_abc123");
@@ -7656,7 +7740,7 @@ declare class EmailResourceBase extends Resource {
    */
   get(messageId: string, options?: RequestOptions): APIPromise<EmailMessage>;
   /**
-   * List sent email messages, newest first, as a cursor page ({data, next_cursor, …}). Pass next_cursor back as starting_after to fetch the next page. Filter by creation time with the half-open range created_after (inclusive) / created_before (exclusive) — e.g. for a single UTC day set created_after to that day at 00:00:00Z and created_before to the next day at 00:00:00Z.
+   * List sent email messages, newest first, as a cursor page ({data, next_cursor, …}). Pass next_cursor back as starting_after to fetch the next page. Filter by creation time with the half-open range created_after (inclusive) / created_before (exclusive). For a single UTC day, created_after is that day at 00:00:00Z and created_before is the next day at 00:00:00Z.
    *
    * @example
    * for await (const message of bird.email.list({ status: "bounced" })) {
@@ -7665,7 +7749,7 @@ declare class EmailResourceBase extends Resource {
    */
   list(query?: EmailListQuery$1, options?: RequestOptions): PaginatedPromise<EmailMessage>;
   /**
-   * Cancel a scheduled email before it sends. Only works while the message is still scheduled (status `scheduled`); once it starts sending — or was already canceled — the call returns a conflict error. Canceling does not return consumed scheduled-send quota.
+   * Cancel a scheduled email before it sends. Only works while the message is still scheduled (status `scheduled`); once it starts sending, or was already canceled, the call returns a conflict error. Canceling does not return consumed scheduled-send quota.
    *
    * @example
    * await bird.email.cancel("em_abc123");
@@ -7800,7 +7884,7 @@ declare class EmailStatsResource extends Resource {
    */
   byMailboxProviderRegion(query?: EmailStatsByMailboxProviderRegionQuery, options?: RequestOptions): APIPromise<EmailStatsByMailboxProviderRegionResponse>;
   /**
-   * Email delivery and engagement stats grouped by the template used at send time, keyed by template id (`emt_…`); only templated sends appear. To track a single template over time, pass `template` to email_stats_daily instead.
+   * Email delivery and engagement stats grouped by the template used at send time, keyed by template id (`emt_…`); only templated sends appear. A single template's trend over time comes from email_stats_daily with its `template` filter.
    *
    * @example
    * const { data } = await bird.email.stats.byTemplate({
@@ -7837,7 +7921,7 @@ declare class EmailStatsResource extends Resource {
    */
   byClient(query?: EmailStatsByClientQuery, options?: RequestOptions): APIPromise<EmailStatsByClientResponse>;
   /**
-   * Bounce counts grouped by the SMTP error code the receiving server returned, with the hard/soft/admin/block/undetermined split; failure side only. Use it to find what is driving bounces; for bounces by destination use email_stats_by_recipient_domain or email_stats_by_mailbox_provider.
+   * Bounce counts grouped by the SMTP error code the receiving server returned, with the hard/soft/admin/block/undetermined split; failure side only. It shows what is driving bounces, while bounces by destination come from email_stats_by_recipient_domain or email_stats_by_mailbox_provider.
    *
    * @example
    * const { data } = await bird.email.stats.byBounceCode({
@@ -7858,7 +7942,7 @@ declare class EmailStatsResource extends Resource {
    */
   byComplaintType(query?: EmailStatsByComplaintTypeQuery, options?: RequestOptions): APIPromise<EmailStatsByComplaintTypeResponse>;
   /**
-   * Email delivery and engagement stats grouped by broadcast; only broadcast sends appear. Reflects roughly the last 30 days of activity; `include_trend` is not available here and returns 422.
+   * Email delivery and engagement stats grouped by broadcast; only broadcast sends appear. Reflects roughly the last 30 days of activity.
    *
    * @example
    * const { data } = await bird.email.stats.byBroadcast({
@@ -7878,7 +7962,7 @@ type EmailMailboxesCreateParams = NonNullable<CreateMailboxData["body"]>;
 type EmailMailboxesUpdateParams = NonNullable<UpdateMailboxData["body"]>;
 type EmailMailboxesUpdateQuery = NonNullable<UpdateMailboxData["query"]>;
 type EmailMailboxesStatsQuery = NonNullable<GetMailboxStatsData["query"]>;
-declare class EmailMailboxesResource$1 extends Resource {
+declare class EmailMailboxesResourceBase extends Resource {
   /**
    * List the workspace's mailboxes as a cursor page, newest first. Search addresses and display names with q, or filter by exact address, state, or domain.
    *
@@ -7889,7 +7973,7 @@ declare class EmailMailboxesResource$1 extends Resource {
    */
   list(query?: EmailMailboxesListQuery, options?: RequestOptions): PaginatedPromise<Mailbox>;
   /**
-   * Create a mailbox — a durable agent identity that owns an email address, groups mail into threads, and remembers conversations for its retention tier.
+   * Create a mailbox: a durable agent identity that owns an email address, groups mail into threads, and remembers conversations for its retention tier.
    *
    * @example Create a mailbox
    * const mailbox = await bird.email.mailboxes.create({ display_name: "Support" });
@@ -7897,13 +7981,15 @@ declare class EmailMailboxesResource$1 extends Resource {
    */
   create(params?: EmailMailboxesCreateParams, options?: RequestOptions): APIPromise<Mailbox>;
   /**
+   * Read one mailbox by id. A mailbox deleted within its 30-day restore window is still returned, carrying a non-null `deleted_at`; once that window closes it is gone and this returns 404.
+   *
    * @example Get a mailbox
    * const mailbox = await bird.email.mailboxes.get("mbx_01abc");
    * console.log(mailbox.state); // "active"
    */
   get(mailboxId: string, options?: RequestOptions): APIPromise<Mailbox>;
   /**
-   * Update a mailbox's display name, reply-to, receive policy, retention tier, contact, or metadata. Lowering the retention tier onto remembered messages older than the new horizon requires confirm=true.
+   * Update a mailbox's display name, reply-to, receive policy, retention tier, IP pool, or metadata. Lowering the retention tier onto remembered messages older than the new horizon requires confirm=true.
    *
    * @example Change a mailbox's receive policy
    * const mailbox = await bird.email.mailboxes.update("mbx_01abc", {
@@ -7936,6 +8022,8 @@ declare class EmailMailboxesResource$1 extends Resource {
    */
   resume(mailboxId: string, options?: RequestOptions): APIPromise<Mailbox>;
   /**
+   * Read a mailbox's sent and received email statistics over a window: a period summary plus a bucketed series. Rows are bucketed by event time rather than send time, so engagement that arrived during the period for messages sent earlier is counted here. Both window bounds must use the same form, calendar days or RFC 3339 instants, matching the granularity.
+   *
    * @example Get mailbox stats
    * const stats = await bird.email.mailboxes.stats("mbx_01abc");
    * console.log(stats.summary?.sends_accepted);
@@ -7993,7 +8081,7 @@ declare class EmailMailboxesReceiveRulesResource extends Resource {
    */
   create(mailboxId: string, params: EmailMailboxesReceiveRulesCreateParams, options?: RequestOptions): APIPromise<ReceiveRule>;
   /**
-   * Remove a receive rule from a mailbox. Delete-and-recreate is how an entry's action is flipped.
+   * Remove a receive rule from a mailbox. Rules have no update operation, so a rule's allow or block action cannot be changed after it is created.
    *
    * @example Delete a rule
    * await bird.email.mailboxes.receiveRules.delete("mbx_01abc", "erl_01xyz");
@@ -8002,7 +8090,7 @@ declare class EmailMailboxesReceiveRulesResource extends Resource {
 }
 //#endregion
 //#region src/resources/emailMailboxes.d.ts
-declare class EmailMailboxesResource extends EmailMailboxesResource$1 {
+declare class EmailMailboxesResource extends EmailMailboxesResourceBase {
   /** Messages sent from the mailbox's own address — `bird.email.mailboxes.messages.create(...)`. */
   readonly messages: EmailMailboxesMessagesResource;
   /** Per-sender allow/block rules — `bird.email.mailboxes.receiveRules.create(...)`, `.list(...)`, `.delete(...)`. */
@@ -8014,9 +8102,9 @@ declare class EmailMailboxesResource extends EmailMailboxesResource$1 {
 type EmailThreadsListQuery = NonNullable<ListEmailThreadsData["query"]>;
 type EmailThreadsUpdateParams = NonNullable<UpdateEmailThreadData["body"]>;
 type EmailThreadsDeleteQuery = NonNullable<DeleteEmailThreadData["query"]>;
-declare class EmailThreadsResource$1 extends Resource {
+declare class EmailThreadsResourceBase extends Resource {
   /**
-   * List mailbox conversations as a cursor page, most recently active first. `label` selects the view — inbox (default), archive, spam, blocked, or a custom label. Filter by mailbox, contact, participant address, or subject substring.
+   * List mailbox conversations as a cursor page, most recently active first. `label` selects the view: inbox (default), archive, spam, blocked, or a custom label. Filter by mailbox, contact, participant address, or subject substring.
    *
    * @example List conversation threads
    * for await (const thread of bird.email.threads.list({ mailbox_id: "mbx_01abc" })) {
@@ -8033,7 +8121,7 @@ declare class EmailThreadsResource$1 extends Resource {
    */
   get(threadId: string, options?: RequestOptions): APIPromise<EmailThread>;
   /**
-   * Add or remove labels on a conversation — adding `spam` files it as spam, adding `archive` clears it out of the inbox, adding `inbox` brings it back — or link/unlink a contact.
+   * Add or remove labels on a conversation, or link and unlink a contact. Adding `spam` files it as spam, `archive` clears it out of the inbox, and `inbox` brings it back.
    *
    * @example Apply label changes to a thread
    * const thread = await bird.email.threads.update("thr_01abc", {
@@ -8065,7 +8153,7 @@ declare class EmailThreadsMessagesResource extends Resource {
    */
   list(threadId: string, query?: EmailThreadsMessagesListQuery, options?: RequestOptions): PaginatedPromise<EmailThreadMessage>;
   /**
-   * Get one conversation message with its extracted plain text — readable for the mailbox's full retention period, no MIME parsing needed.
+   * Get one conversation message with its extracted plain text, readable for the mailbox's full retention period without MIME parsing.
    *
    * @example Get a message
    * const msg = await bird.email.threads.messages.get("thr_01abc", "rem_01xyz");
@@ -8101,7 +8189,7 @@ declare class EmailThreadsMessagesResource extends Resource {
 }
 //#endregion
 //#region src/resources/emailThreads.d.ts
-declare class EmailThreadsResource extends EmailThreadsResource$1 {
+declare class EmailThreadsResource extends EmailThreadsResourceBase {
   /** Messages in a conversation — `bird.email.threads.messages.list(...)`, `.reply(...)`, … */
   readonly messages: EmailThreadsMessagesResource;
   constructor(...args: ConstructorParameters<typeof Resource>);
@@ -8334,7 +8422,7 @@ declare class DomainsResource extends Resource {
    */
   get(domainId: string, options?: RequestOptions): APIPromise<Domain>;
   /**
-   * Register a new sending domain and get the DNS records to publish. Flow: call this, publish the returned DNS records at your DNS provider, then call email_domains_verify (repeat until status is verified — DNS propagation can take minutes to hours).
+   * Register a new sending domain and get the DNS records to publish. Verification is a second step: the records go live at the DNS provider, then email_domains_verify confirms them. Propagation takes minutes to hours, so the first verify often still reports unverified and a later one succeeds.
    *
    * @example Register a sending domain
    * const domain = await bird.domains.create({ domain: "mail.acme.com" });
@@ -8350,7 +8438,7 @@ declare class DomainsResource extends Resource {
    */
   verify(domainId: string, options?: RequestOptions): APIPromise<Domain>;
   /**
-   * Update a sending domain's tracking and inbound configuration. Tracking: toggle click_tracking and open_tracking (applied immediately to new sends), and set, change, or remove the tracking domain (the name part only — Bird appends the sending domain). Enabling either toggle with no tracking domain configured returns 409; removing the tracking domain while either toggle is still on also returns 409. Tracking-domain changes on a verified domain are staged behind DNS verification, so the current config keeps serving until the new records verify. Inbound receiving: set inbound.enabled to start or stop receiving mail for the domain. Enabling requires the domain's DKIM to be verified first (a fresh enable on an unverified domain returns 422), and a domain already receiving inbound for another organization returns 422. The MX records to publish are always listed in dns_records regardless, so enabling — not merely publishing them — is what turns receiving on.
+   * Update a sending domain's tracking and inbound configuration. Tracking: click_tracking and open_tracking apply immediately to new sends, and the tracking domain can be set, changed, or removed (the name part only; Bird appends the sending domain). Enabling either toggle with no tracking domain configured returns 409, and removing the tracking domain while either toggle is still on also returns 409. Tracking-domain changes on a verified domain are staged behind DNS verification, so the current config keeps serving until the new records verify. Inbound receiving: inbound.enabled starts or stops receiving mail for the domain. Enabling requires the domain's DKIM to be verified first (a fresh enable on an unverified domain returns 422), and a domain already receiving inbound for another organization returns 422. The MX records to publish are always listed in dns_records regardless, so receiving starts only once inbound.enabled is set, even when those records are already published.
    *
    * @example Enable tracking on a domain
    * await bird.domains.update("dom_01krdgeqcxet5s7t44vh8rt9mg", {
@@ -8400,7 +8488,7 @@ declare class ContactPropertiesResource extends Resource {
    */
   create(params: ContactPropertyCreateParams, options?: RequestOptions): APIPromise<ContactProperty>;
   /**
-   * Update a contact property's fallback value. The key and type are immutable; create a new property instead.
+   * Update a contact property's fallback value. Only the fallback value can change; the key and type are fixed at creation, so a different key or type needs a new property.
    *
    * @example Change a property's fallback value
    * await bird.contactProperties.update("cp_01krdgeqcxet5s7t44vh8rt9mg", { fallback_value: "free" });
@@ -8430,7 +8518,7 @@ type ContactUpdateParams = NonNullable<UpdateContactData["body"]>;
 type ContactBatchParams = NonNullable<CreateContactBatchData["body"]>;
 declare class ContactsResource extends Resource {
   /**
-   * List the workspace's contacts as a cursor page, newest first. Look one up by exact email or external_id, or search by email substring.
+   * List the workspace's contacts as a cursor page, newest first. Look one up by exact email, phone, or external_id, 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" })) {
@@ -8440,7 +8528,7 @@ declare class ContactsResource extends Resource {
    */
   list(query?: ContactListQuery, options?: RequestOptions): PaginatedPromise<Contact>;
   /**
-   * Get a single contact by ID (`con_`-prefixed). Look up an ID by exact email or external_id with `contacts.list`.
+   * Get a single contact by ID (`con_`-prefixed). Look up an ID by exact email, phone, or external_id with `contacts.list`.
    *
    * @example Fetch a contact by id
    * const contact = await bird.contacts.get("con_01krdgeqcxet5s7t44vh8rt9mg");
@@ -8448,7 +8536,7 @@ declare class ContactsResource extends Resource {
    */
   get(contactId: string, options?: RequestOptions): APIPromise<Contact>;
   /**
-   * Create a contact by email address in the workspace. Fails with a conflict if the email 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, 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({
@@ -8457,9 +8545,9 @@ declare class ContactsResource extends Resource {
    * });
    * console.log(contact.id); // "con_…"
    */
-  create(params: ContactCreateParams, options?: RequestOptions): APIPromise<Contact>;
+  create(params?: ContactCreateParams, options?: RequestOptions): APIPromise<Contact>;
   /**
-   * Update a contact's name, external_id, email, or custom data. Only supplied fields change; custom data keys are merged, with null removing a key.
+   * Update a contact's name, external_id, email, phone, 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 is rejected.
    *
    * @example Change a contact's fields
    * const contact = await bird.contacts.update("con_01krdgeqcxet5s7t44vh8rt9mg", {
@@ -8476,14 +8564,14 @@ declare class ContactsResource extends Resource {
    */
   delete(contactId: string, options?: RequestOptions): APIPromise<void>;
   /**
-   * Create or update up to 1,000 contacts in one request, matched by email address, and optionally add them all to one or more audiences. Per-contact results are returned in submission order.
+   * Create or update up to 1,000 contacts in one request, each entry matched automatically against every identifier it supplies (email, phone, 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.
    *
-   * @example Create or update many contacts at once, matched by email
+   * @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.email, item.status);
+   *   console.log(item.entry.email, item.status);
    * }
    */
   batch(params: ContactBatchParams, options?: RequestOptions): APIPromise<ContactUpsertResult>;
@@ -8588,7 +8676,7 @@ declare class WhatsappResourceBase extends Resource {
    */
   get(messageId: string, options?: RequestOptions): APIPromise<WhatsAppMessage>;
   /**
-   * 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 status, contact phone number, bsuid, or tag. Use whatsapp_get for one message's current state.
+   * 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, 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"] })) {
@@ -8719,56 +8807,37 @@ declare class WebhooksResource {
   unwrap(payload: string, headers: WebhookHeaders, options?: WebhookOptions): BirdWebhookEvent;
 }
 //#endregion
-//#region src/resources/realtime.d.ts
-/** Body for `bird.realtime.publish` — one event to one or more channels. */
-type RealtimePublishParams = RealtimePublish;
-/** Body for `bird.realtime.publishBatch` — up to 10 events, one channel each. */
-type RealtimeBatchPublishParams = RealtimeBatchPublish;
-/** Query params for `bird.realtime.channels.list`. */
-type RealtimeChannelsListQuery = NonNullable<ListRealtimeAppChannelsData["query"]>;
-/** Query params for `bird.realtime.channels.get`. */
-type RealtimeChannelGetQuery = NonNullable<GetRealtimeAppChannelData["query"]>;
-/**
- * Realtime app credentials — `new BirdClient({ realtime: { key, secret } })`.
- * They come from the app's credentials (shown once at creation) and must belong
- * to the calling workspace. Any Realtime method takes the same pair in its
- * trailing options to override the configured one for a single call — the way
- * to talk to a second app without a second client.
- */
-interface RealtimeOptions {
-  /** The Realtime app key, sent as `X-Realtime-Key`. */
-  key?: string;
-  /** The Realtime app secret, sent as `X-Realtime-Secret`. */
-  secret?: string;
-}
-/** Per-call options for a Realtime method: the usual request options plus a credential override. */
-interface RealtimeRequestOptions extends RequestOptions, RealtimeOptions {}
-/** The resolved credential headers, in wire form. */
-interface RealtimeAuthHeaders {
-  "X-Realtime-Key": string;
-  "X-Realtime-Secret": string;
-}
-declare abstract class RealtimeBase extends Resource {
-  #private;
-  constructor(core: ConstructorParameters<typeof Resource>[0], client: ConstructorParameters<typeof Resource>[1], config?: RealtimeOptions);
+//#region src/resources/realtime.gen.d.ts
+type RealtimePublishParams = NonNullable<PublishRealtimeAppEventData["body"]>;
+type RealtimePublishBatchParams = NonNullable<PublishRealtimeAppBatchData["body"]>;
+declare class RealtimeResourceBase extends Resource {
   /**
-   * Resolve the app credentials for one call. Called eagerly at the top of each
-   * method so a missing credential throws before the lifecycle starts — never
-   * as a rejected promise after a request is already in flight.
+   * @example Broadcast an event to a channel
+   * const result = await bird.realtime.publish("rap_01krdgeqcxet5s7t44vh8rt9mg", {
+   *   event: "order.updated",
+   *   channels: ["orders", "presence-lobby"],
+   *   data: { order_id: "ord_123", status: "shipped" },
+   * });
+   * console.log(result.data?.length); // one entry per channel
    */
-  protected auth(options?: RealtimeOptions): RealtimeAuthHeaders;
+  publish(realtimeAppId: string, params: RealtimePublishParams, options?: RequestOptions): APIPromise<RealtimePublishResult>;
+  /**
+   * @example Publish two events in one call
+   * await bird.realtime.publishBatch("rap_01krdgeqcxet5s7t44vh8rt9mg", {
+   *   events: [
+   *     { event: "order.created", channel: "orders", data: { id: 1 } },
+   *     { event: "order.updated", channel: "orders", data: { id: 2 } },
+   *   ],
+   * });
+   */
+  publishBatch(realtimeAppId: string, params: RealtimePublishBatchParams, options?: RequestOptions): APIPromise<RealtimeBatchPublishResult>;
 }
-/**
- * `bird.realtime.channels` — reads the app's live channel state. Channels exist
- * implicitly: one appears when the first connection subscribes and vanishes when
- * the last one leaves, so these report occupancy, never existence.
- */
-declare class RealtimeChannelsResource extends RealtimeBase {
+//#endregion
+//#region src/resources/realtimeChannels.gen.d.ts
+type RealtimeChannelListQuery = NonNullable<ListRealtimeAppChannelsData["query"]>;
+type RealtimeChannelGetQuery = NonNullable<GetRealtimeAppChannelData["query"]>;
+declare class RealtimeChannelsResource extends Resource {
   /**
-   * List the app's currently occupied channels, optionally filtered by name
-   * prefix. The Realtime service returns them all in one response — this is a
-   * point read, not a cursor list, so there is nothing to iterate.
-   *
    * @example List the occupied presence channels with their member counts
    * const { data } = await bird.realtime.channels.list("rap_01krdgeqcxet5s7t44vh8rt9mg", {
    *   prefix: "presence-",
@@ -8776,89 +8845,63 @@ declare class RealtimeChannelsResource extends RealtimeBase {
    * });
    * for (const channel of data) console.log(channel.name, channel.member_count);
    */
-  list(appId: string, query?: RealtimeChannelsListQuery, options?: RealtimeRequestOptions): APIPromise<RealtimeChannelsList>;
+  list(realtimeAppId: string, query?: RealtimeChannelListQuery, options?: RequestOptions): APIPromise<RealtimeChannelsList>;
   /**
-   * Read one channel's state. An unknown or never-used name is not an error —
-   * it resolves with `occupied: false`.
-   *
    * @example Check whether anyone is in a channel
-   * const channel = await bird.realtime.channels.get(
-   *   "rap_01krdgeqcxet5s7t44vh8rt9mg",
-   *   "presence-lobby",
-   *   { include: ["member_count"] },
-   * );
+   * const channel = await bird.realtime.channels.get("rap_01krdgeqcxet5s7t44vh8rt9mg", "presence-lobby", {
+   *   include: ["member_count"],
+   * });
    * console.log(channel.occupied, channel.member_count);
    */
-  get(appId: string, channelName: string, query?: RealtimeChannelGetQuery, options?: RealtimeRequestOptions): APIPromise<RealtimeChannelInfo>;
+  get(realtimeAppId: string, channelName: string, query?: RealtimeChannelGetQuery, options?: RequestOptions): APIPromise<RealtimeChannelInfo>;
   /**
-   * List the member ids subscribed to a presence channel. Ids only — the
-   * `member_info` your authorization endpoint attaches is delivered to subscribed
-   * clients over the realtime connection and is not available over REST.
-   *
    * @example Who is in the lobby
-   * const { members } = await bird.realtime.channels.members(
-   *   "rap_01krdgeqcxet5s7t44vh8rt9mg",
-   *   "presence-lobby",
-   * );
+   * const { members } = await bird.realtime.channels.members("rap_01krdgeqcxet5s7t44vh8rt9mg", "presence-lobby");
    * for (const member of members) console.log(member.member_id);
    */
-  members(appId: string, channelName: string, options?: RealtimeRequestOptions): APIPromise<RealtimeChannelMembers>;
+  members(realtimeAppId: string, channelName: string, options?: RequestOptions): APIPromise<RealtimeChannelMembers>;
 }
-/** `bird.realtime.members` — acts on a member across all of its connections. */
-declare class RealtimeMembersResource extends RealtimeBase {
+//#endregion
+//#region src/resources/realtimeMembers.gen.d.ts
+type RealtimeMemberSendParams = NonNullable<SendRealtimeAppMemberEventData["body"]>;
+declare class RealtimeMembersResource extends Resource {
+  /**
+   * @example Notify one person wherever they are signed in
+   * await bird.realtime.members.send("rap_01krdgeqcxet5s7t44vh8rt9mg", "user_42", {
+   *   event: "order-shipped",
+   *   data: { order_id: "ord_123" },
+   * });
+   */
+  send(realtimeAppId: string, memberId: string, params: RealtimeMemberSendParams, options?: RequestOptions): APIPromise<void>;
   /**
-   * Disconnect every active connection a member holds — sign-out, ban, or a
-   * revoked session. Resolves once the disconnect is applied; the member may
-   * reconnect immediately unless your authorization endpoint refuses them.
-   *
    * @example Kick a member off every connection
    * await bird.realtime.members.disconnect("rap_01krdgeqcxet5s7t44vh8rt9mg", "user_42");
    */
-  disconnect(appId: string, memberId: string, options?: RealtimeRequestOptions): APIPromise<void>;
+  disconnect(realtimeAppId: string, memberId: string, options?: RequestOptions): APIPromise<void>;
+}
+//#endregion
+//#region src/resources/realtime.d.ts
+/**
+ * Realtime app credentials — `new BirdClient({ realtime: { key, secret } })`.
+ * They come from the app's credentials (shown once at creation) and must belong
+ * to the calling workspace.
+ */
+interface RealtimeOptions {
+  /** The Realtime app key, sent as `X-Realtime-Key`. */
+  key?: string;
+  /** The Realtime app secret, sent as `X-Realtime-Secret`. */
+  secret?: string;
 }
 /**
  * `bird.realtime` — publish events to a Realtime app's channels and inspect its
- * live state. Every method needs the app's key/secret pair: set it once as
- * `realtime: { key, secret }` on the client, or pass `{ key, secret }` in a
- * call's options to reach a different app. Reached as `bird.realtime.*`.
+ * live state. Reached as `bird.realtime.*`.
  */
-declare class RealtimeResource extends RealtimeBase {
+declare class RealtimeResource extends RealtimeResourceBase {
   /** Channel state — `bird.realtime.channels.list(...)`, `.get(...)`, `.members(...)`. */
   readonly channels: RealtimeChannelsResource;
-  /** Members — `bird.realtime.members.disconnect(...)`. */
+  /** Members — `bird.realtime.members.send(...)`, `.disconnect(...)`. */
   readonly members: RealtimeMembersResource;
-  constructor(core: ConstructorParameters<typeof Resource>[0], client: ConstructorParameters<typeof Resource>[1], config?: RealtimeOptions);
-  /**
-   * Publish one event to one or more of the app's channels. Listing several
-   * channels broadcasts the same event to all of them in a single call. Resolves
-   * once the event is accepted — delivery to connected clients is asynchronous.
-   *
-   * Pass `exclude_connection_id` to skip the connection that triggered the
-   * change, so the originating client doesn't echo its own update.
-   *
-   * @example Broadcast an event to a channel
-   * const result = await bird.realtime.publish("rap_01krdgeqcxet5s7t44vh8rt9mg", {
-   *   event: "order.updated",
-   *   channels: ["orders", "presence-lobby"],
-   *   data: { order_id: "ord_123", status: "shipped" },
-   * });
-   * console.log(result.data?.length); // one entry per channel
-   */
-  publish(appId: string, params: RealtimePublishParams, options?: RealtimeRequestOptions): APIPromise<RealtimePublishResult>;
-  /**
-   * Publish up to 10 events in one request, each to a single channel. Use it to
-   * fan different events out at once; to send the *same* event to many channels,
-   * use `publish` with several `channels` instead.
-   *
-   * @example Publish two events in one call
-   * await bird.realtime.publishBatch("rap_01krdgeqcxet5s7t44vh8rt9mg", {
-   *   events: [
-   *     { event: "order.created", channel: "orders", data: { id: 1 } },
-   *     { event: "order.updated", channel: "orders", data: { id: 2 } },
-   *   ],
-   * });
-   */
-  publishBatch(appId: string, params: RealtimeBatchPublishParams, options?: RealtimeRequestOptions): APIPromise<RealtimeBatchPublishResult>;
+  constructor(core: ConstructorParameters<typeof Resource>[0], client: ConstructorParameters<typeof Resource>[1]);
 }
 //#endregion
 //#region src/client.d.ts
@@ -9020,10 +9063,6 @@ declare const WebhookEventType: {
   readonly SmsFailed: "sms.failed";
   readonly SmsRejected: "sms.rejected";
   readonly SmsSent: "sms.sent";
-  readonly SmsTfnVerificationApproved: "sms.tfn_verification.approved";
-  readonly SmsTfnVerificationInfoRequested: "sms.tfn_verification.info_requested";
-  readonly SmsTfnVerificationRejected: "sms.tfn_verification.rejected";
-  readonly SmsTfnVerificationSubmitted: "sms.tfn_verification.submitted";
   readonly SmsUndelivered: "sms.undelivered";
   readonly VerifyAttemptDelivered: "verify.attempt.delivered";
   readonly VerifyAttemptSent: "verify.attempt.sent";
@@ -9043,5 +9082,106 @@ declare const WebhookEventType: {
 /** A known webhook event type value. */
 type WebhookEventTypeValue = (typeof WebhookEventType)[keyof typeof WebhookEventType];
 //#endregion
-export { type APIPromise, type Audience, type AudienceAddContactsParams, type AudienceCreateParams, type AudienceListContactsQuery, type AudienceListQuery, type AudienceMember, type AudienceRemoveContactsParams, type AudienceUpdateParams, BirdAPIError, BirdAuthError, BirdBadRequestError, BirdBillingError, BirdClient, type BirdClientOptions, BirdConflictError, BirdConnectionError, BirdError, BirdInternalError, BirdMisdirectedError, BirdNotFoundError, BirdNotImplementedError, BirdPayloadTooLargeError, BirdPermissionError, BirdPreconditionError, BirdRateLimitError, type BirdRequest, type BirdResponse, BirdServiceUnavailableError, BirdTimeoutError, BirdValidationError, type BirdWebhookEvent, BirdWebhookVerificationError, type Contact, type ContactBatchParams, type ContactCreateParams, type ContactListQuery, type ContactProperty, type ContactPropertyCreateParams, type ContactPropertyListQuery, type ContactPropertyUpdateParams, type ContactUpdateParams, type ContactUpsertResult, type CursorPage, type DnsRecord, type Domain, type DomainCapabilities, type DomainCreateParams, type DomainDkim, type DomainListQuery, type DomainUpdateParams, type EmailChannelDefaults, type EmailListQuery, type EmailMailboxLabelList, type EmailMailboxesCreateParams, type EmailMailboxesListQuery, type EmailMailboxesMessagesCreateParams, type EmailMailboxesReceiveRulesCreateParams, type EmailMailboxesReceiveRulesListQuery, type EmailMailboxesStatsQuery, type EmailMailboxesUpdateParams, type EmailMailboxesUpdateQuery, type EmailMessage, type EmailSendBatchParams, type EmailSendBatchResult, type EmailSendParams, type EmailStatsByBounceCodeQuery, type EmailStatsByBounceCodeResponse, type EmailStatsByBroadcastQuery, type EmailStatsByBroadcastResponse, type EmailStatsByCategoryQuery, type EmailStatsByCategoryResponse, type EmailStatsByClientQuery, type EmailStatsByClientResponse, type EmailStatsByComplaintTypeQuery, type EmailStatsByComplaintTypeResponse, type EmailStatsByLocationQuery, type EmailStatsByLocationResponse, type EmailStatsByMailboxProviderQuery, type EmailStatsByMailboxProviderRegionQuery, type EmailStatsByMailboxProviderRegionResponse, type EmailStatsByMailboxProviderResponse, type EmailStatsByRecipientDomainQuery, type EmailStatsByRecipientDomainResponse, type EmailStatsBySendingDomainQuery, type EmailStatsBySendingDomainResponse, type EmailStatsBySendingIpQuery, type EmailStatsBySendingIpResponse, type EmailStatsByTagQuery, type EmailStatsByTemplateQuery, type EmailStatsByTemplateResponse, type EmailStatsDailyQuery, type EmailStatsHourlyQuery, type EmailStatsResponse, type EmailStatsSummary, type EmailStatsSummaryQuery, type EmailStatsTagsResponse, type EmailThread, type EmailThreadMessage, type EmailThreadMessageAttachmentList, type EmailThreadMessageBody, type EmailThreadsDeleteQuery, type EmailThreadsListQuery, type EmailThreadsMessagesListQuery, type EmailThreadsMessagesReplyParams, type EmailThreadsUpdateParams, type ErrorDetail, type ErrorNextAction, type Mailbox, type MailboxStatsResponse, type PaginatedPromise, type RealtimeBatchPublishParams, type RealtimeBatchPublishResult, type RealtimeChannelGetQuery, type RealtimeChannelInclude, type RealtimeChannelInfo, type RealtimeChannelListItem, type RealtimeChannelMember, type RealtimeChannelMembers, type RealtimeChannelsList, type RealtimeChannelsListQuery, type RealtimeOptions, type RealtimePublishParams, type RealtimePublishResult, type RealtimeRequestOptions, type ReceiveRule, type RequestOptions, type SafeResult, type SmsListQuery, type SmsMessage, type SmsSendBatchParams, type SmsSendBatchResult, type SmsSendParams, type SmsTemplate, type SmsTemplateList, type SmsTemplateListQuery, type UnmetGate, type Verification, type VerificationCheckResult, type VerifyVerificationsCheckParams, type VerifyVerificationsCreateParams, WebhookEventType, type WebhookEventTypeValue, type WebhookHeaders, type WebhookOptions, type WhatsAppEventList, type WhatsAppMessage, type WhatsappListEventsQuery, type WhatsappListQuery, type WhatsappSendParams, baseUrlForRegion, regionFromApiKey };
+//#region src/open-enums.gen.d.ts
+/**
+ * Values of EmailEventType 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.
+ */
+declare const EmailEventType: {
+  readonly EmailAccepted: "email.accepted";
+  readonly EmailBounced: "email.bounced";
+  readonly EmailCanceled: "email.canceled";
+  readonly EmailClicked: "email.clicked";
+  readonly EmailComplained: "email.complained";
+  readonly EmailDeferred: "email.deferred";
+  readonly EmailDelivered: "email.delivered";
+  readonly EmailListUnsubscribed: "email.list_unsubscribed";
+  readonly EmailOpened: "email.opened";
+  readonly EmailOutOfBandBounce: "email.out_of_band_bounce";
+  readonly EmailProcessed: "email.processed";
+  readonly EmailRejected: "email.rejected";
+  readonly EmailScheduled: "email.scheduled";
+  readonly EmailUnsubscribed: "email.unsubscribed";
+};
+/** A known EmailEventType value. */
+type EmailEventTypeValue = (typeof EmailEventType)[keyof typeof EmailEventType];
+/**
+ * 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.
+ */
+declare const VerificationAttemptFailureReason: {
+  readonly CarrierRejected: "carrier_rejected";
+  readonly ChannelDisabled: "channel_disabled";
+  readonly ChannelUnavailable: "channel_unavailable";
+  readonly HardBounce: "hard_bounce";
+  readonly SoftBounce: "soft_bounce";
+  readonly Undelivered: "undelivered";
+};
+/** A known VerificationAttemptFailureReason value. */
+type VerificationAttemptFailureReasonValue = (typeof VerificationAttemptFailureReason)[keyof typeof VerificationAttemptFailureReason];
+/**
+ * Values of VerificationChannel 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.
+ */
+declare const VerificationChannel: {
+  readonly Email: "email";
+  readonly Sms: "sms";
+  readonly Whatsapp: "whatsapp";
+};
+/** A known VerificationChannel value. */
+type VerificationChannelValue = (typeof VerificationChannel)[keyof typeof VerificationChannel];
+/**
+ * Values of VerificationTerminalReason 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.
+ */
+declare const VerificationTerminalReason: {
+  readonly AttemptsExhausted: "attempts_exhausted";
+  readonly TtlElapsed: "ttl_elapsed";
+};
+/** A known VerificationTerminalReason value. */
+type VerificationTerminalReasonValue = (typeof VerificationTerminalReason)[keyof typeof VerificationTerminalReason];
+/**
+ * Values of WhatsAppErrorCode 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.
+ */
+declare const WhatsAppErrorCode: {
+  readonly InsufficientBalance: "insufficient_balance";
+  readonly InternalError: "internal_error";
+  readonly PriceNotFound: "price_not_found";
+  readonly RateLimited: "rate_limited";
+  readonly RecipientSuppressed: "recipient_suppressed";
+  readonly ServiceWindowExpired: "service_window_expired";
+  readonly Undeliverable: "undeliverable";
+};
+/** A known WhatsAppErrorCode value. */
+type WhatsAppErrorCodeValue = (typeof WhatsAppErrorCode)[keyof typeof WhatsAppErrorCode];
+/**
+ * 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.
+ */
+declare const WhatsAppTemplateCategory: {
+  readonly Authentication: "authentication";
+  readonly Marketing: "marketing";
+  readonly Utility: "utility";
+};
+/** A known WhatsAppTemplateCategory value. */
+type WhatsAppTemplateCategoryValue = (typeof WhatsAppTemplateCategory)[keyof typeof WhatsAppTemplateCategory];
+/**
+ * Values of WhatsAppTemplateParameterType 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.
+ */
+declare const WhatsAppTemplateParameterType: {
+  readonly Text: "text";
+};
+/** A known WhatsAppTemplateParameterType value. */
+type WhatsAppTemplateParameterTypeValue = (typeof WhatsAppTemplateParameterType)[keyof typeof WhatsAppTemplateParameterType];
+//#endregion
+export { type APIPromise, type Audience, type AudienceAddContactsParams, type AudienceCreateParams, type AudienceListContactsQuery, type AudienceListQuery, type AudienceMember, type AudienceRemoveContactsParams, type AudienceUpdateParams, BirdAPIError, BirdAuthError, BirdBadRequestError, BirdBillingError, BirdClient, type BirdClientOptions, BirdConflictError, BirdConnectionError, BirdError, BirdInternalError, BirdMisdirectedError, BirdNotFoundError, BirdNotImplementedError, BirdPayloadTooLargeError, BirdPermissionError, BirdPreconditionError, BirdRateLimitError, type BirdRequest, type BirdResponse, BirdServiceUnavailableError, BirdTimeoutError, BirdValidationError, type BirdWebhookEvent, BirdWebhookVerificationError, type Contact, type ContactBatchParams, type ContactCreateParams, type ContactListQuery, type ContactProperty, type ContactPropertyCreateParams, type ContactPropertyListQuery, type ContactPropertyUpdateParams, type ContactUpdateParams, type ContactUpsertResult, type CursorPage, type DnsRecord, type Domain, type DomainCapabilities, type DomainCreateParams, type DomainDkim, type DomainListQuery, type DomainUpdateParams, type EmailChannelDefaults, EmailEventType, type EmailEventTypeValue, type EmailListQuery, type EmailMailboxLabelList, type EmailMailboxesCreateParams, type EmailMailboxesListQuery, type EmailMailboxesMessagesCreateParams, type EmailMailboxesReceiveRulesCreateParams, type EmailMailboxesReceiveRulesListQuery, type EmailMailboxesStatsQuery, type EmailMailboxesUpdateParams, type EmailMailboxesUpdateQuery, type EmailMessage, type EmailSendBatchParams, type EmailSendBatchResult, type EmailSendParams, type EmailStatsByBounceCodeQuery, type EmailStatsByBounceCodeResponse, type EmailStatsByBroadcastQuery, type EmailStatsByBroadcastResponse, type EmailStatsByCategoryQuery, type EmailStatsByCategoryResponse, type EmailStatsByClientQuery, type EmailStatsByClientResponse, type EmailStatsByComplaintTypeQuery, type EmailStatsByComplaintTypeResponse, type EmailStatsByLocationQuery, type EmailStatsByLocationResponse, type EmailStatsByMailboxProviderQuery, type EmailStatsByMailboxProviderRegionQuery, type EmailStatsByMailboxProviderRegionResponse, type EmailStatsByMailboxProviderResponse, type EmailStatsByRecipientDomainQuery, type EmailStatsByRecipientDomainResponse, type EmailStatsBySendingDomainQuery, type EmailStatsBySendingDomainResponse, type EmailStatsBySendingIpQuery, type EmailStatsBySendingIpResponse, type EmailStatsByTagQuery, type EmailStatsByTemplateQuery, type EmailStatsByTemplateResponse, type EmailStatsDailyQuery, type EmailStatsHourlyQuery, type EmailStatsResponse, type EmailStatsSummary, type EmailStatsSummaryQuery, type EmailStatsTagsResponse, type EmailThread, type EmailThreadMessage, type EmailThreadMessageAttachmentList, type EmailThreadMessageBody, type EmailThreadsDeleteQuery, type EmailThreadsListQuery, type EmailThreadsMessagesListQuery, type EmailThreadsMessagesReplyParams, type EmailThreadsUpdateParams, type ErrorDetail, type ErrorNextAction, type Mailbox, type MailboxStatsResponse, type PaginatedPromise, type RealtimeBatchPublishResult, type RealtimeChannelGetQuery, type RealtimeChannelInclude, type RealtimeChannelInfo, type RealtimeChannelListItem, type RealtimeChannelListQuery, type RealtimeChannelMember, type RealtimeChannelMembers, type RealtimeChannelsList, type RealtimeOptions, type RealtimePublishBatchParams, type RealtimePublishParams, type RealtimePublishResult, type ReceiveRule, type RequestOptions, type SafeResult, type SmsListQuery, type SmsMessage, type SmsSendBatchParams, type SmsSendBatchResult, type SmsSendParams, type SmsTemplate, type SmsTemplateList, type SmsTemplateListQuery, type UnmetGate, type Verification, VerificationAttemptFailureReason, type VerificationAttemptFailureReasonValue, VerificationChannel, type VerificationChannelValue, type VerificationCheckResult, VerificationTerminalReason, type VerificationTerminalReasonValue, type VerifyVerificationsCheckParams, type VerifyVerificationsCreateParams, WebhookEventType, type WebhookEventTypeValue, type WebhookHeaders, type WebhookOptions, WhatsAppErrorCode, type WhatsAppErrorCodeValue, type WhatsAppEventList, type WhatsAppMessage, WhatsAppTemplateCategory, type WhatsAppTemplateCategoryValue, WhatsAppTemplateParameterType, type WhatsAppTemplateParameterTypeValue, type WhatsappListEventsQuery, type WhatsappListQuery, type WhatsappSendParams, baseUrlForRegion, regionFromApiKey };
 //# sourceMappingURL=index.d.mts.map