rcs-js 2.0.14 → 2.0.15

package/dist/esm/api/types/AttachWebhookResult.d.mts

@@ -0,0 +1,22 @@
+import type * as Pinnacle from "../index.mjs";
+export interface AttachWebhookResult {
+    webhook: AttachWebhookResult.Webhook;
+    /** The event type filter applied to these subscriptions. */
+    event: Pinnacle.WebhookEventEnum | null;
+    /** Senders that were successfully attached (phone numbers in E.164 format or RCS agent IDs). */
+    senders: string[];
+    /** Senders that could not be attached, with error details. */
+    failed: Pinnacle.FailedSender[];
+}
+export declare namespace AttachWebhookResult {
+    interface Webhook {
+        /** Unique webhook identifier (starts with `wh_`). */
+        id: string;
+        /** Name of the webhook. */
+        name: string;
+        /** HTTPS endpoint URL where events are delivered. */
+        url: string;
+        /** Signing secret sent in the `PINNACLE-SIGNING-SECRET` header for request verification. */
+        secret: string;
+    }
+}

package/dist/esm/api/types/DetachWebhookResult.d.mts

@@ -0,0 +1,9 @@
+import type * as Pinnacle from "../index.mjs";
+export interface DetachWebhookResult {
+    /** The webhook that was detached from the senders. */
+    webhookId: string;
+    /** Senders that were successfully detached (phone numbers in E.164 format or RCS agent IDs). */
+    senders: string[];
+    /** Senders that could not be detached, with error details. */
+    failed: Pinnacle.FailedSender[];
+}

package/dist/esm/api/types/DetachWebhookResult.mjs

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/types/ExtendedRcsCampaign.d.mts

@@ -13,21 +13,15 @@ export interface ExtendedRcsCampaign {
     /** Legal documentation links. */
     links?: ExtendedRcsCampaign.Links;
     status: Pinnacle.ProfileStatusEnum;
-    /** Use case classification for the campaign. */
-    useCase?: ExtendedRcsCampaign.UseCase;
-    /** Details on how opt-in is acquired. If it is done through a website or app, provide the link. See the [Opt-In Terms and Conditions](/guides/campaigns/rcs-compliance#opt-in-terms-and-conditions) section for requirements. */
-    optInTermsAndConditions?: string;
+    /** Detailed summary of what the brand is and how this agent will be used. See the [Use Case Behavior](/guides/campaigns/rcs-compliance#use-case-behavior) section for requirements. */
+    useCaseDescription?: string;
     messagingType?: Pinnacle.RcsMessagingTypeEnum;
-    /** Description of the agent's purpose, shown to carriers for approval. See the [Carrier Description](/guides/campaigns/rcs-compliance#carrier-description) section for requirements. */
-    carrierDescription?: string;
+    /** URL to the opt-in form or a URL to a screenshot of the opt-in CTA. */
+    ctaMedia?: string;
+    /** Details on how opt-in is acquired. If it is done through a website or app, provide the link. See the [Opt-In Method](/guides/campaigns/rcs-compliance#opt-in-method) section for requirements. */
+    optInMethod?: string;
     keywords?: ExtendedRcsCampaign.Keywords;
     traffic?: ExtendedRcsCampaign.Traffic;
-    /** Explanation of how the agent is triggered. This includes how the first message is delivered, whether messages follow a schedule or triggered by user actions, and any external triggers. See the [Agent Triggers](/guides/campaigns/rcs-compliance#agent-triggers) section for requirements. */
-    agentTriggers?: string;
-    /** Description of all agent interactions, including primary and secondary use cases. See the [Interaction Description](/guides/campaigns/rcs-compliance#interaction-description) section for requirements. */
-    interactionDescription?: string;
-    /** Whether the agent supports conversational flows or respond to P2A messages from the users. Set to false for one-way messages from agent to user. */
-    isConversational?: boolean;
     /** Required text that appears next to the opt-in checkbox for your opt-in form. This checkbox has to be unchecked by default. See the [CTA Language](/guides/campaigns/rcs-compliance#cta-language-opt-in-disclosure) section for requirements. */
     ctaLanguage?: string;
     /** Instructions on how an external reviewer can trigger messages and an example flow from the agent. This is usually an inbound text message to the agent that will start a flow of messages between the agent and the user. See the [Demo Trigger](/guides/campaigns/rcs-compliance#demo-trigger) section for requirements. */
@@ -93,14 +87,6 @@ export declare namespace ExtendedRcsCampaign {
         /** Terms of service URL. */
         termsOfService?: string;
     }
-    /**
-     * Use case classification for the campaign.
-     */
-    interface UseCase {
-        /** Detailed summary of what the brand is and how this agent will be used. See the [Use Case Behavior](/guides/campaigns/rcs-compliance#use-case-behavior) section for requirements. */
-        behavior?: string;
-        value?: Pinnacle.RcsCampaignUseCaseEnum;
-    }
     interface Keywords {
         HELP?: Keywords.Help;
         OPT_IN?: Keywords.OptIn;

package/dist/esm/api/types/FailedSender.d.mts

@@ -0,0 +1,6 @@
+export interface FailedSender {
+    /** The sender that failed. */
+    sender: string;
+    /** Reason for the failure. */
+    error: string;
+}

package/dist/esm/api/types/FailedSender.mjs

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/types/RcsCampaign.d.mts

@@ -8,21 +8,15 @@ export interface RcsCampaign {
     expectedAgentResponses?: string[];
     /** Legal documentation links. */
     links?: RcsCampaign.Links;
-    /** Use case classification for the campaign. */
-    useCase?: RcsCampaign.UseCase;
-    /** Details on how opt-in is acquired. If it is done through a website or app, provide the link. See the [Opt-In Terms and Conditions](/guides/campaigns/rcs-compliance#opt-in-terms-and-conditions) section for requirements. */
-    optInTermsAndConditions?: string;
+    /** Detailed summary of what the brand is and how this agent will be used. See the [Use Case Behavior](/guides/campaigns/rcs-compliance#use-case-behavior) section for requirements. */
+    useCaseDescription?: string;
     messagingType?: Pinnacle.RcsMessagingTypeEnum;
-    /** Description of the agent's purpose, shown to carriers for approval. See the [Carrier Description](/guides/campaigns/rcs-compliance#carrier-description) section for requirements. */
-    carrierDescription?: string;
+    /** URL to the opt-in form or a URL to a screenshot of the opt-in CTA. */
+    ctaMedia?: string;
+    /** Details on how opt-in is acquired. If it is done through a website or app, provide the link. See the [Opt-In Method](/guides/campaigns/rcs-compliance#opt-in-method) section for requirements. */
+    optInMethod?: string;
     keywords?: RcsCampaign.Keywords;
     traffic?: RcsCampaign.Traffic;
-    /** Explanation of how the agent is triggered. This includes how the first message is delivered, whether messages follow a schedule or triggered by user actions, and any external triggers. See the [Agent Triggers](/guides/campaigns/rcs-compliance#agent-triggers) section for requirements. */
-    agentTriggers?: string;
-    /** Description of all agent interactions, including primary and secondary use cases. See the [Interaction Description](/guides/campaigns/rcs-compliance#interaction-description) section for requirements. */
-    interactionDescription?: string;
-    /** Whether the agent supports conversational flows or respond to P2A messages from the users. Set to false for one-way messages from agent to user. */
-    isConversational?: boolean;
     /** Required text that appears next to the opt-in checkbox for your opt-in form. This checkbox has to be unchecked by default. See the [CTA Language](/guides/campaigns/rcs-compliance#cta-language-opt-in-disclosure) section for requirements. */
     ctaLanguage?: string;
     /** Instructions on how an external reviewer can trigger messages and an example flow from the agent. This is usually an inbound text message to the agent that will start a flow of messages between the agent and the user. See the [Demo Trigger](/guides/campaigns/rcs-compliance#demo-trigger) section for requirements. */
@@ -88,14 +82,6 @@ export declare namespace RcsCampaign {
         /** Terms of service URL. */
         termsOfService?: string;
     }
-    /**
-     * Use case classification for the campaign.
-     */
-    interface UseCase {
-        /** Detailed summary of what the brand is and how this agent will be used. See the [Use Case Behavior](/guides/campaigns/rcs-compliance#use-case-behavior) section for requirements. */
-        behavior?: string;
-        value?: Pinnacle.RcsCampaignUseCaseEnum;
-    }
     interface Keywords {
         HELP?: Keywords.Help;
         OPT_IN?: Keywords.OptIn;

package/dist/esm/api/types/RcsCampaignSummary.d.mts

@@ -7,8 +7,6 @@ export interface RcsCampaignSummary {
     status: RcsCampaignSummary.Status;
     /** Brand ID associated with this campaign. */
     brandId?: string;
-    /** Primary use case for this campaign. */
-    useCase?: string;
     /** RCS agent ID associated with this campaign. */
     agentId?: string;
     /** ISO 8601 timestamp of when the campaign was created. */

package/dist/esm/api/types/WebhookEventEnum.d.mts

@@ -1,10 +1,11 @@
 /**
- * Types of events that can trigger webhook notifications for phone numbers.
- * Subscribe to specific events to receive real-time updates about your phone number activity.
+ * Types of events that can trigger webhook notifications.
+ * Subscribe to specific events to receive real-time updates about your sender activity.
  * Use `null` to listen to all events.
  */
 export declare const WebhookEventEnum: {
     readonly MessageStatus: "MESSAGE.STATUS";
     readonly MessageReceived: "MESSAGE.RECEIVED";
+    readonly UserTyping: "USER.TYPING";
 };
 export type WebhookEventEnum = (typeof WebhookEventEnum)[keyof typeof WebhookEventEnum];

package/dist/esm/api/types/WebhookEventEnum.mjs

@@ -1,10 +1,11 @@
 // This file was auto-generated by Fern from our API Definition.
 /**
- * Types of events that can trigger webhook notifications for phone numbers.
- * Subscribe to specific events to receive real-time updates about your phone number activity.
+ * Types of events that can trigger webhook notifications.
+ * Subscribe to specific events to receive real-time updates about your sender activity.
  * Use `null` to listen to all events.
  */
 export const WebhookEventEnum = {
     MessageStatus: "MESSAGE.STATUS",
     MessageReceived: "MESSAGE.RECEIVED",
+    UserTyping: "USER.TYPING",
 };

package/dist/esm/api/types/index.d.mts

@@ -5,7 +5,7 @@ export * from "./AgentSummary.mjs";
 export * from "./AgentUseCase.mjs";
 export * from "./AgentWebsiteEntry.mjs";
 export * from "./AttachedPhoneNumberResult.mjs";
-export * from "./AttachWebhookParams.mjs";
+export * from "./AttachWebhookResult.mjs";
 export * from "./AudienceCountOnly.mjs";
 export * from "./AudienceSummary.mjs";
 export * from "./AudienceWithPagination.mjs";
@@ -29,7 +29,6 @@ export * from "./CarrierLaunchStatus.mjs";
 export * from "./CompanyEntityTypeEnum.mjs";
 export * from "./CompanySectorEnum.mjs";
 export * from "./CompanyTypeEnum.mjs";
-export * from "./ConfiguredWebhook.mjs";
 export * from "./Contact.mjs";
 export * from "./ContactId.mjs";
 export * from "./Conversation.mjs";
@@ -37,7 +36,7 @@ export * from "./ConversationList.mjs";
 export * from "./CreateUrlOptions.mjs";
 export * from "./DeleteAudienceResponse.mjs";
 export * from "./DetachedPhoneNumberResult.mjs";
-export * from "./DetachedWebhookInfo.mjs";
+export * from "./DetachWebhookResult.mjs";
 export * from "./DetailedPhoneNumberEnum.mjs";
 export * from "./DlcAssignmentStatusEnum.mjs";
 export * from "./DlcCampaignStatus.mjs";
@@ -50,6 +49,7 @@ export * from "./Error_.mjs";
 export * from "./ExtendedBrand.mjs";
 export * from "./ExtendedBrandWithVetting.mjs";
 export * from "./ExtendedRcsCampaign.mjs";
+export * from "./FailedSender.mjs";
 export * from "./FallbackMessage.mjs";
 export * from "./GetConversationParams.mjs";
 export * from "./LinkClickEvent.mjs";
@@ -119,7 +119,6 @@ export * from "./RcsButtonTrigger.mjs";
 export * from "./RcsCampaign.mjs";
 export * from "./RcsCampaignStatus.mjs";
 export * from "./RcsCampaignSummary.mjs";
-export * from "./RcsCampaignUseCaseEnum.mjs";
 export * from "./RcsCapabilitiesResult.mjs";
 export * from "./RcsCapability.mjs";
 export * from "./RcsCardsContent.mjs";

package/dist/esm/api/types/index.mjs

@@ -5,7 +5,7 @@ export * from "./AgentSummary.mjs";
 export * from "./AgentUseCase.mjs";
 export * from "./AgentWebsiteEntry.mjs";
 export * from "./AttachedPhoneNumberResult.mjs";
-export * from "./AttachWebhookParams.mjs";
+export * from "./AttachWebhookResult.mjs";
 export * from "./AudienceCountOnly.mjs";
 export * from "./AudienceSummary.mjs";
 export * from "./AudienceWithPagination.mjs";
@@ -29,7 +29,6 @@ export * from "./CarrierLaunchStatus.mjs";
 export * from "./CompanyEntityTypeEnum.mjs";
 export * from "./CompanySectorEnum.mjs";
 export * from "./CompanyTypeEnum.mjs";
-export * from "./ConfiguredWebhook.mjs";
 export * from "./Contact.mjs";
 export * from "./ContactId.mjs";
 export * from "./Conversation.mjs";
@@ -37,7 +36,7 @@ export * from "./ConversationList.mjs";
 export * from "./CreateUrlOptions.mjs";
 export * from "./DeleteAudienceResponse.mjs";
 export * from "./DetachedPhoneNumberResult.mjs";
-export * from "./DetachedWebhookInfo.mjs";
+export * from "./DetachWebhookResult.mjs";
 export * from "./DetailedPhoneNumberEnum.mjs";
 export * from "./DlcAssignmentStatusEnum.mjs";
 export * from "./DlcCampaignStatus.mjs";
@@ -50,6 +49,7 @@ export * from "./Error_.mjs";
 export * from "./ExtendedBrand.mjs";
 export * from "./ExtendedBrandWithVetting.mjs";
 export * from "./ExtendedRcsCampaign.mjs";
+export * from "./FailedSender.mjs";
 export * from "./FallbackMessage.mjs";
 export * from "./GetConversationParams.mjs";
 export * from "./LinkClickEvent.mjs";
@@ -119,7 +119,6 @@ export * from "./RcsButtonTrigger.mjs";
 export * from "./RcsCampaign.mjs";
 export * from "./RcsCampaignStatus.mjs";
 export * from "./RcsCampaignSummary.mjs";
-export * from "./RcsCampaignUseCaseEnum.mjs";
 export * from "./RcsCapabilitiesResult.mjs";
 export * from "./RcsCapability.mjs";
 export * from "./RcsCardsContent.mjs";

package/dist/esm/version.d.mts

@@ -1 +1 @@
-export declare const SDK_VERSION = "2.0.14";
+export declare const SDK_VERSION = "2.0.15";

package/dist/esm/version.mjs

@@ -1 +1 @@
-export const SDK_VERSION = "2.0.14";
+export const SDK_VERSION = "2.0.15";

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "rcs-js",
-    "version": "2.0.14",
+    "version": "2.0.15",
     "private": false,
     "repository": "github:pinnacle-dev/rcs-js",
     "type": "commonjs",

package/reference.md

@@ -2172,6 +2172,143 @@ await client.webhooks.list();
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.webhooks.<a href="/src/api/resources/webhooks/client/Client.ts">attach</a>({ ...params }) -> Pinnacle.AttachWebhookResult</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Attach a webhook to one or more senders (phone numbers or RCS agent IDs) to receive real-time event notifications. <br>
+
+You can attach an existing webhook by providing its ID, or create a new webhook by specifying a name and URL. Supports bulk operations with up to 50 senders per request. <br>
+
+Subscriptions are additive — attaching new senders does not remove existing ones. Re-attaching the same sender updates the event type filter without creating duplicates.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.webhooks.attach({
+    senders: ["+14155551234", "agent_abc123"]
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `Pinnacle.AttachWebhookParams` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `Webhooks.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.webhooks.<a href="/src/api/resources/webhooks/client/Client.ts">detach</a>({ ...params }) -> Pinnacle.DetachWebhookResult</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Detach a webhook from one or more senders (phone numbers or RCS agent IDs) to stop receiving event notifications. <br>
+
+The webhook itself is not deleted and remains available for use with other senders. Works regardless of webhook status. Supports bulk operations with up to 50 senders per request.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.webhooks.detach({
+    webhookId: "webhookId",
+    senders: ["+14155551234", "agent_abc123"]
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `Pinnacle.DetachWebhookParams` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `Webhooks.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -3429,16 +3566,13 @@ await client.campaigns.rcs.upsert({
     campaignId: "rcs_1234567890",
     expectedAgentResponses: ["Here are the things I can help you with.", "I can assist you with booking an appointment, or you may choose to book manually.", "Here are the available times to connect with a representative tomorrow.", "Your appointment has been scheduled."],
     links: {
-        privacyPolicy: "https://www.trypinnacle.app/privacy",
-        termsOfService: "https://www.trypinnacle.app/terms"
-    },
-    useCase: {
-        behavior: "Pinnacle is a developer-focused RCS assistant that helps teams design, test, and optimize rich messaging experiences across SMS, MMS, and RCS. The agent acts as both an \u201Conboarding guide\u201D for new customers and a \u201Cbest-practices coach\u201D for existing teams exploring higher-value RCS workflows like rich cards, carousels, and suggested actions.<br>\nThe agent delivers a mix of operational updates and educational content (2\u20136 messages/month). Content includes important platform notices (e.g., deliverability or throughput changes), implementation tips with sample RCS templates, and personalized recommendations on how to upgrade existing SMS campaigns into richer, higher-converting RCS conversations.\n",
-        value: "OTHER"
+        privacyPolicy: "\u201Chttps://www.trypinnacle.app/privacy\u201D",
+        termsOfService: "\u201Chttps://www.trypinnacle.app/terms\u201D"
     },
-    optInTermsAndConditions: "We ensure consent through an explicit opt-in process that follows 10DLC best practices.Users must agree to receive messages from Pinnacle before the agent sends them any messages.<br>\nUsers agree to these messages by signing an opt-in paper form that they can be found online at https://www.pinnacle.sh/opt-in. We only send messages once users have filled out the form and submitted it to us via email or through the dashboard.\n",
-    messagingType: "MULTI_USE",
-    carrierDescription: "Demonstrate the power of RCS to medium and large companies already sending massive SMS/MMS volumes through our platform. These clients send conversational messages in industries such as commerce, appointments, and customer support.",
+    useCaseDescription: "Pinnacle is a developer-focused RCS assistant that helps teams design, test, and optimize rich messaging experiences across SMS, MMS, and RCS. The agent acts as both an \u201Conboarding guide\u201D for new customers and a \u201Cbest-practices coach\u201D for existing teams exploring higher-value RCS workflows like rich cards, carousels, and suggested actions.<br>\nThe agent delivers a mix of operational updates and educational content (2\u20136 messages/month). Content includes important platform notices (e.g., deliverability or throughput changes), implementation tips with sample RCS templates, and personalized recommendations on how to upgrade existing SMS campaigns into richer, higher-converting RCS conversations.\n",
+    messagingType: "OTP",
+    ctaMedia: "\u201Chttps://www.pinnacle.sh/send\u201D",
+    optInMethod: "We ensure consent through an explicit opt-in process that follows 10DLC best practices.Users must agree to receive messages from Pinnacle before the agent sends them any messages.<br>\nUsers agree to these messages by signing an opt-in paper form that they can be found online at https://www.pinnacle.sh/opt-in. We only send messages once users have filled out the form and submitted it to us via email or through the dashboard.\n",
     keywords: {
         HELP: {
             message: "Email founders@trypinnacle.app for support.",
@@ -3457,9 +3591,6 @@ await client.campaigns.rcs.upsert({
         monthlyWebsite: 10000,
         monthlyRcsEstimate: 10000
     },
-    agentTriggers: "The agent sends the first message when the user subscribes to Pinnacle. Messages are based on user actions such as pressing suggestion buttons. External triggers such as reminders can be setup by users in advance for a later time.",
-    interactionDescription: "The agent's primary interaction will be customer service \u2014 helping users with questions, troubleshooting issues, and providing quick assistance through chat. Other interactions include appointment management and sending notifications to the user.",
-    isConversational: true,
     ctaLanguage: "By checking this box and submitting this form, you consent to receive transactional text messages for support, appointment, and reminder messages from Pinnacle Software Development Inc. Reply STOP to opt out. Reply HELP for help. Standard message and data rates may apply. Message frequency may vary. View our Terms and Conditions at https://www.pinnacle.sh/terms. View our Privacy Policy at https://www.pinnacle.sh/privacy.",
     demoTrigger: "Text \"START\" to trigger the flow."
 });
@@ -4547,166 +4678,6 @@ await client.messages.blasts.list();
 </dl>
 
 
-</dd>
-</dl>
-</details>
-
-## PhoneNumbers Webhook
-<details><summary><code>client.phoneNumbers.webhook.<a href="/src/api/resources/phoneNumbers/resources/webhook/client/Client.ts">attach</a>(phone, { ...params }) -> Pinnacle.ConfiguredWebhook</code></summary>
-<dl>
-<dd>
-
-#### 📝 Description
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-Connect a webhook to your phone number to receive real-time notifications for incoming messages, delivery status updates, and other communication events.
-</dd>
-</dl>
-</dd>
-</dl>
-
-#### 🔌 Usage
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-```typescript
-await client.phoneNumbers.webhook.attach("%2B14155551234", {
-    webhookId: "wh_1234567890",
-    event: "MESSAGE.STATUS"
-});
-
-```
-</dd>
-</dl>
-</dd>
-</dl>
-
-#### ⚙️ Parameters
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-**phone:** `string` 
-
-The phone number you want to attach the webhook to in E.164 format. Make sure it is url encoded (i.e. replace the leading + with %2B). <br>
-
-Must be a phone number that you own and have already [purchased](./buy) through the API. A phone number can have multiple webhooks attached to it.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request:** `Pinnacle.AttachWebhookParams` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**requestOptions:** `Webhook.RequestOptions` 
-    
-</dd>
-</dl>
-</dd>
-</dl>
-
-
-</dd>
-</dl>
-</details>
-
-<details><summary><code>client.phoneNumbers.webhook.<a href="/src/api/resources/phoneNumbers/resources/webhook/client/Client.ts">detach</a>(phone, webhookId) -> Pinnacle.DetachedWebhookInfo</code></summary>
-<dl>
-<dd>
-
-#### 📝 Description
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-Disconnect a webhook from your phone number to stop receiving event notifications for that specific number. <br>
-
-The webhook configuration itself remains intact and available for use with other phone numbers.
-</dd>
-</dl>
-</dd>
-</dl>
-
-#### 🔌 Usage
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-```typescript
-await client.phoneNumbers.webhook.detach("+14155551234", "wh_1234567890");
-
-```
-</dd>
-</dl>
-</dd>
-</dl>
-
-#### ⚙️ Parameters
-
-<dl>
-<dd>
-
-<dl>
-<dd>
-
-**phone:** `string` 
-
-The phone number you want to attach the webhook to in E.164 format. Make sure it is url encoded (i.e. replace the leading + with %2B). <br>
-
-Must be a phone number that you own and currently has the specified webhook attached.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**webhookId:** `string` 
-
-The unique identifier of the webhook you want to detach from the phone number. <br>
-
-This must be a valid webhook ID that is currently attached to the specified phone number. This identifier is a string that always begins with the prefix `wh_`, for example: `wh_1234567890`.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**requestOptions:** `Webhook.RequestOptions` 
-    
-</dd>
-</dl>
-</dd>
-</dl>
-
-
 </dd>
 </dl>
 </details>