rcs 2.0.19 → 2.0.20.pre.rc.1

data/reference.md

@@ -2966,8 +2966,8 @@ client.webhooks.detach(
 </dl>
 </details>
 
-## Forms
-<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">get</a>(id) -> Pinnacle::Types::Form</code></summary>
+## Calls
+<details><summary><code>client.calls.<a href="/lib/pinnacle/calls/client.rb">list</a>() -> Pinnacle::Types::ListCallsResponse</code></summary>
 <dl>
 <dd>
 
@@ -2979,7 +2979,7 @@ client.webhooks.detach(
 <dl>
 <dd>
 
-Retrieve a form by id. Includes submission count, last submission timestamp, and archive state.
+List voice calls for your team. Results are sorted newest first.
 </dd>
 </dl>
 </dd>
@@ -2994,7 +2994,7 @@ Retrieve a form by id. Includes submission count, last submission timestamp, and
 <dd>
 
 ```ruby
-client.forms.get(id: "form_Oy2n7iUoi9CJwUU6")
+client.calls.list
 ```
 </dd>
 </dl>
@@ -3009,10 +3009,7 @@ client.forms.get(id: "form_Oy2n7iUoi9CJwUU6")
 <dl>
 <dd>
 
-**id:** `String` 
-
-The unique identifier of the form you want to retrieve.
-<br><br> This identifier is a string that always begins with the prefix `form_`, for example: `form_Oy2n7iUoi9CJwUU6`. It's returned on every form response (`Form.id`) and by [`POST /forms/send`](/api-reference/forms/send-form) (`response.form.id`).
+**limit:** `Integer` — Maximum calls to return.
     
 </dd>
 </dl>
@@ -3020,101 +3017,120 @@ The unique identifier of the form you want to retrieve.
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Forms::RequestOptions` 
+**cursor:** `String` — Opaque cursor returned by the previous page.
     
 </dd>
 </dl>
-</dd>
-</dl>
 
+<dl>
+<dd>
 
+**state:** `Pinnacle::Types::CallState` 
+    
 </dd>
 </dl>
-</details>
 
-<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">update</a>(id, request) -> Pinnacle::Types::Form</code></summary>
 <dl>
 <dd>
 
-#### 📝 Description
+**direction:** `Pinnacle::Types::CallDirection` 
+    
+</dd>
+</dl>
 
 <dl>
 <dd>
 
+**from:** `String` 
+    
+</dd>
+</dl>
+
 <dl>
 <dd>
 
-Partial update. Only keys present in the body are applied. Archived forms (non-null `archived_at`) cannot be updated — restore the form by setting `archived_at: null` in a PATCH first.
+**to:** `String` 
+    
 </dd>
 </dl>
+
+<dl>
+<dd>
+
+**created_after:** `String` 
+    
 </dd>
 </dl>
 
-#### 🔌 Usage
-
 <dl>
 <dd>
 
+**created_before:** `String` 
+    
+</dd>
+</dl>
+
 <dl>
 <dd>
 
-```ruby
-client.forms.update(
-  id: "form_Oy2n7iUoi9CJwUU6",
-  name: "Contact request (v2)",
-  can_update: true,
-  expires_at: "2026-12-31T23:59:59Z"
-)
-```
+**request_options:** `Pinnacle::Calls::RequestOptions` 
+    
 </dd>
 </dl>
 </dd>
 </dl>
 
-#### ⚙️ Parameters
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.calls.<a href="/lib/pinnacle/calls/client.rb">create</a>(request) -> Pinnacle::Types::CreatedCall</code></summary>
 <dl>
 <dd>
 
+#### 📝 Description
+
 <dl>
 <dd>
 
-**id:** `String` 
+<dl>
+<dd>
 
-The unique identifier of the form you want to update.
-<br><br> This identifier is a string that always begins with the prefix `form_`, for example: `form_Oy2n7iUoi9CJwUU6`.
-    
+Start an outbound voice call from a voice-enabled phone number owned by your team.
 </dd>
 </dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
 
 <dl>
 <dd>
 
-**name:** `String` — Replace the form's title. Pass `null` to clear.
-    
-</dd>
-</dl>
-
 <dl>
 <dd>
 
-**description:** `String` — Replace the form's description. Pass `null` to clear.
-    
+```ruby
+client.calls.create(
+  to: "to",
+  from: "from"
+)
+```
+</dd>
+</dl>
 </dd>
 </dl>
 
+#### ⚙️ Parameters
+
 <dl>
 <dd>
 
-**fields:** `Internal::Types::Array[Pinnacle::Types::FormField]` — Replace the full set of fields on the form. Partial field updates aren't supported — send the complete new list.
-    
-</dd>
-</dl>
-
 <dl>
 <dd>
 
-**can_update:** `Internal::Types::Boolean` — Toggle whether the recipient can re-edit their submission.
+**to:** `String` — Destination phone number in E.164 format.
     
 </dd>
 </dl>
@@ -3122,7 +3138,7 @@ The unique identifier of the form you want to update.
 <dl>
 <dd>
 
-**expires_at:** `String` — Set or clear the form's expiration timestamp.
+**from:** `String` — Voice-enabled phone number owned by your team.
     
 </dd>
 </dl>
@@ -3130,7 +3146,7 @@ The unique identifier of the form you want to update.
 <dl>
 <dd>
 
-**theme_override:** `Pinnacle::Types::FormThemeOverride` — Replace the per-form theme override. Pass `null` to revert to team defaults.
+**record:** `Internal::Types::Boolean` — Start recording as soon as the call stream connects.
     
 </dd>
 </dl>
@@ -3138,7 +3154,7 @@ The unique identifier of the form you want to update.
 <dl>
 <dd>
 
-**archived_at:** `String` — Set to an ISO timestamp to archive the form (soft-delete), or `null` to restore an archived form.
+**metadata:** `Internal::Types::Hash[String, String]` 
     
 </dd>
 </dl>
@@ -3146,7 +3162,7 @@ The unique identifier of the form you want to update.
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Forms::RequestOptions` 
+**request_options:** `Pinnacle::Calls::RequestOptions` 
     
 </dd>
 </dl>
@@ -3158,7 +3174,7 @@ The unique identifier of the form you want to update.
 </dl>
 </details>
 
-<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">list</a>(request) -> Pinnacle::Types::ListFormsResponse</code></summary>
+<details><summary><code>client.calls.<a href="/lib/pinnacle/calls/client.rb">get</a>(id) -> Pinnacle::Types::Call</code></summary>
 <dl>
 <dd>
 
@@ -3170,7 +3186,7 @@ The unique identifier of the form you want to update.
 <dl>
 <dd>
 
-Paginated list of forms on your team, sorted by creation date (newest first). Includes archived forms.
+Retrieve one voice call by its Pinnacle call ID.
 </dd>
 </dl>
 </dd>
@@ -3185,10 +3201,7 @@ Paginated list of forms on your team, sorted by creation date (newest first). In
 <dd>
 
 ```ruby
-client.forms.list(
-  page_index: 0,
-  page_size: 20
-)
+client.calls.get(id: "call_7cQe4F8xT1yB2mN9pK3L")
 ```
 </dd>
 </dl>
@@ -3203,15 +3216,7 @@ client.forms.list(
 <dl>
 <dd>
 
-**page_index:** `Integer` — Zero-based page index.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**page_size:** `Integer` — Number of forms to return in a single page. Max 100.
+**id:** `String` — Pinnacle call ID.
     
 </dd>
 </dl>
@@ -3219,7 +3224,7 @@ client.forms.list(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Forms::RequestOptions` 
+**request_options:** `Pinnacle::Calls::RequestOptions` 
     
 </dd>
 </dl>
@@ -3231,7 +3236,7 @@ client.forms.list(
 </dl>
 </details>
 
-<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">create</a>(request) -> Pinnacle::Types::Form</code></summary>
+<details><summary><code>client.calls.<a href="/lib/pinnacle/calls/client.rb">cancel</a>(id) -> Pinnacle::Types::Call</code></summary>
 <dl>
 <dd>
 
@@ -3243,11 +3248,7 @@ client.forms.list(
 <dl>
 <dd>
 
-Create a hosted form without sending it. <br>
-
-Returns the form object including its public URL — `https://forms.pinnacle.sh/{form_id}`. <br>
-
-To also deliver the URL to a recipient over SMS or RCS in a single call, use [`POST /forms/send`](/api-reference/forms/send-form).
+End a live call. Terminal calls are returned unchanged.
 </dd>
 </dl>
 </dd>
@@ -3262,12 +3263,7 @@ To also deliver the URL to a recipient over SMS or RCS in a single call, use [`P
 <dd>
 
 ```ruby
-client.forms.create(
-  name: "Contact request",
-  description: "We'll follow up over SMS or RCS.",
-  fields: [],
-  can_update: false
-)
+client.calls.cancel(id: "call_7cQe4F8xT1yB2mN9pK3L")
 ```
 </dd>
 </dl>
@@ -3282,7 +3278,7 @@ client.forms.create(
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::FormDefinition` 
+**id:** `String` — Pinnacle call ID.
     
 </dd>
 </dl>
@@ -3290,7 +3286,7 @@ client.forms.create(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Forms::RequestOptions` 
+**request_options:** `Pinnacle::Calls::RequestOptions` 
     
 </dd>
 </dl>
@@ -3302,7 +3298,7 @@ client.forms.create(
 </dl>
 </details>
 
-<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">send_</a>(request) -> Pinnacle::Forms::Types::FormsSendResponse</code></summary>
+<details><summary><code>client.calls.<a href="/lib/pinnacle/calls/client.rb">update</a>(id, request) -> Pinnacle::Types::Call</code></summary>
 <dl>
 <dd>
 
@@ -3314,19 +3310,7 @@ client.forms.create(
 <dl>
 <dd>
 
-Send a form to a recipient over SMS or RCS, or mint a standalone submission URL.
-
-Pass `form` as either an existing form id (`form_*`) or an inline `{ fields, ... }` definition to mint a new form for this send.
-
-The delivery channel is inferred from `from`:
-- `from: "agent_*"` → RCS (with optional SMS `fallback`)
-- `from: "+E.164"` → SMS
-
-When `to` is provided, Pinnacle dispatches a message whose body contains the submission URL and the recipient is recorded on the response: `submission.to` echoes the same E.164 number and `message_id` is the id of the outbound SMS/RCS. 
-
-When `to` is omitted, no message is sent — `submission.to` and `message_id` are both `null` — which is useful for embedding the URL in your own outreach.
-
-On completion, a `FORM.SUBMISSION` webhook event is delivered to webhooks subscribed to the sender. See [Receiving Messages and User Events](/guides/messages/receiving).
+Replace a call's metadata. For live calls, future call events carry the updated metadata.
 </dd>
 </dl>
 </dd>
@@ -3341,15 +3325,10 @@ On completion, a `FORM.SUBMISSION` webhook event is delivered to webhooks subscr
 <dd>
 
 ```ruby
-client.forms.send_(
-  from: "agent_iM9wQcyBBjYn",
-  to: "+14155551234",
-  form: "form_Oy2n7iUoi9CJwUU6",
-  fallback: {
-    from: "+14155550000"
-  },
-  options: {
-    webview_mode: "FULL"
+client.calls.update(
+  id: "call_7cQe4F8xT1yB2mN9pK3L",
+  metadata: {
+    key: "value"
   }
 )
 ```
@@ -3366,7 +3345,7 @@ client.forms.send_(
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::SendFormParams` 
+**id:** `String` — Pinnacle call ID.
     
 </dd>
 </dl>
@@ -3374,7 +3353,15 @@ client.forms.send_(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Forms::RequestOptions` 
+**metadata:** `Internal::Types::Hash[String, String]` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Calls::RequestOptions` 
     
 </dd>
 </dl>
@@ -3386,8 +3373,7 @@ client.forms.send_(
 </dl>
 </details>
 
-## Audiences Contacts
-<details><summary><code>client.audiences.contacts.<a href="/lib/pinnacle/audiences/contacts/client.rb">remove</a>(request) -> Pinnacle::Types::AudienceCountOnly</code></summary>
+<details><summary><code>client.calls.<a href="/lib/pinnacle/calls/client.rb">list_events</a>(id) -> Pinnacle::Types::ListCallEventsResponse</code></summary>
 <dl>
 <dd>
 
@@ -3399,10 +3385,7 @@ client.forms.send_(
 <dl>
 <dd>
 
-Remove contacts from an existing audience. This operation is idempotent.
-
-- Only removes contacts that exist in the audience
-- Contacts not in the audience are ignored
+List the event timeline for a call.
 </dd>
 </dl>
 </dd>
@@ -3417,10 +3400,7 @@ Remove contacts from an existing audience. This operation is idempotent.
 <dd>
 
 ```ruby
-client.audiences.contacts.remove(
-  id: "aud_abc123",
-  contacts: %w[+12125551234 co_def456]
-)
+client.calls.list_events(id: "call_7cQe4F8xT1yB2mN9pK3L")
 ```
 </dd>
 </dl>
@@ -3435,7 +3415,7 @@ client.audiences.contacts.remove(
 <dl>
 <dd>
 
-**id:** `String` — Audience ID. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`.
+**id:** `String` — Pinnacle call ID.
     
 </dd>
 </dl>
@@ -3443,10 +3423,15 @@ client.audiences.contacts.remove(
 <dl>
 <dd>
 
-**contacts:** `Internal::Types::Array[String]` 
+**limit:** `Integer` — Maximum call events to return.
+    
+</dd>
+</dl>
 
-Array of phone numbers (E.164 format) or contact IDs. <br><br>
-**Limit:** 1 min
+<dl>
+<dd>
+
+**cursor:** `String` — Opaque cursor returned by the previous page.
     
 </dd>
 </dl>
@@ -3454,7 +3439,7 @@ Array of phone numbers (E.164 format) or contact IDs. <br><br>
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Audiences::Contacts::RequestOptions` 
+**request_options:** `Pinnacle::Calls::RequestOptions` 
     
 </dd>
 </dl>
@@ -3466,7 +3451,7 @@ Array of phone numbers (E.164 format) or contact IDs. <br><br>
 </dl>
 </details>
 
-<details><summary><code>client.audiences.contacts.<a href="/lib/pinnacle/audiences/contacts/client.rb">add</a>(request) -> Pinnacle::Types::AudienceCountOnly</code></summary>
+<details><summary><code>client.calls.<a href="/lib/pinnacle/calls/client.rb">create_stream_token</a>(id, request) -> Pinnacle::Types::CallStreamToken</code></summary>
 <dl>
 <dd>
 
@@ -3478,11 +3463,7 @@ Array of phone numbers (E.164 format) or contact IDs. <br><br>
 <dl>
 <dd>
 
-Add contacts to an existing audience. This operation is additive and idempotent.
-
-- Phone numbers that don't exist will be auto-created as contacts
-- Duplicate adds are ignored
-- Contacts already in the audience are ignored
+Mint a short-lived WebSocket token for a call. Use the returned `stream_url` to connect to Pinnacle's bidirectional voice stream.
 </dd>
 </dl>
 </dd>
@@ -3497,10 +3478,7 @@ Add contacts to an existing audience. This operation is additive and idempotent.
 <dd>
 
 ```ruby
-client.audiences.contacts.add(
-  id: "aud_abc123",
-  contacts: %w[+12125551234 co_def456 +13105551234]
-)
+client.calls.create_stream_token(id: "call_7cQe4F8xT1yB2mN9pK3L")
 ```
 </dd>
 </dl>
@@ -3515,7 +3493,7 @@ client.audiences.contacts.add(
 <dl>
 <dd>
 
-**id:** `String` — Audience ID. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`.
+**id:** `String` — Pinnacle call ID.
     
 </dd>
 </dl>
@@ -3523,10 +3501,15 @@ client.audiences.contacts.add(
 <dl>
 <dd>
 
-**contacts:** `Internal::Types::Array[String]` 
+**commands_enabled:** `Internal::Types::Boolean` — Whether this WebSocket may send call commands. Defaults to true.
+    
+</dd>
+</dl>
 
-Array of phone numbers (E.164 format) or contact IDs. <br><br>
-**Limit:** 1 min
+<dl>
+<dd>
+
+**stream_id:** `String` — Customer-chosen stream ID for reconnects and multiple subscribers.
     
 </dd>
 </dl>
@@ -3534,7 +3517,15 @@ Array of phone numbers (E.164 format) or contact IDs. <br><br>
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Audiences::Contacts::RequestOptions` 
+**record:** `Internal::Types::Boolean` — Enable recording for this WebSocket stream.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Calls::RequestOptions` 
     
 </dd>
 </dl>
@@ -3546,8 +3537,7 @@ Array of phone numbers (E.164 format) or contact IDs. <br><br>
 </dl>
 </details>
 
-## Campaigns Dlc
-<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">autofill</a>(request) -> Pinnacle::Types::AutofillDlcCampaignResponse</code></summary>
+<details><summary><code>client.calls.<a href="/lib/pinnacle/calls/client.rb">download_recording</a>(id) -> Pinnacle::Types::RecordingDownload</code></summary>
 <dl>
 <dd>
 
@@ -3559,7 +3549,7 @@ Array of phone numbers (E.164 format) or contact IDs. <br><br>
 <dl>
 <dd>
 
-Generate campaign details based off existing campaign and the brand it's connected to.
+Return a short-lived signed URL for the call recording.
 </dd>
 </dl>
 </dd>
@@ -3574,10 +3564,7 @@ Generate campaign details based off existing campaign and the brand it's connect
 <dd>
 
 ```ruby
-client.campaigns.dlc.autofill(
-  additional_info: "Please autofill missing campaign fields using my brand profile",
-  campaign_id: "dlc_1234567890"
-)
+client.calls.download_recording(id: "call_7cQe4F8xT1yB2mN9pK3L")
 ```
 </dd>
 </dl>
@@ -3592,7 +3579,7 @@ client.campaigns.dlc.autofill(
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::AutofillCampaignParams` 
+**id:** `String` — Pinnacle call ID.
     
 </dd>
 </dl>
@@ -3600,7 +3587,15 @@ client.campaigns.dlc.autofill(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
+**expires_in:** `Integer` — Signed URL lifetime in seconds. Defaults to 300 and may be at most 86400.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Calls::RequestOptions` 
     
 </dd>
 </dl>
@@ -3612,7 +3607,7 @@ client.campaigns.dlc.autofill(
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">get</a>(campaign_id) -> Pinnacle::Types::DlcCampaignWithExtendedBrandAndStatus</code></summary>
+<details><summary><code>client.calls.<a href="/lib/pinnacle/calls/client.rb">delete_recording</a>(id) -> </code></summary>
 <dl>
 <dd>
 
@@ -3624,7 +3619,7 @@ client.campaigns.dlc.autofill(
 <dl>
 <dd>
 
-Retrieve 10DLC campaign.
+Delete the canonical recording and queued fragments for a terminal call.
 </dd>
 </dl>
 </dd>
@@ -3639,7 +3634,7 @@ Retrieve 10DLC campaign.
 <dd>
 
 ```ruby
-client.campaigns.dlc.get(campaign_id: "dlc_1234567890")
+client.calls.delete_recording(id: "call_7cQe4F8xT1yB2mN9pK3L")
 ```
 </dd>
 </dl>
@@ -3654,7 +3649,7 @@ client.campaigns.dlc.get(campaign_id: "dlc_1234567890")
 <dl>
 <dd>
 
-**campaign_id:** `String` — Unique identifier of the 10DLC campaign. This identifier is a string that always begins with the prefix `dlc_`, for example: `dlc_1234567890`.
+**id:** `String` — Pinnacle call ID.
     
 </dd>
 </dl>
@@ -3662,7 +3657,7 @@ client.campaigns.dlc.get(campaign_id: "dlc_1234567890")
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
+**request_options:** `Pinnacle::Calls::RequestOptions` 
     
 </dd>
 </dl>
@@ -3674,7 +3669,8 @@ client.campaigns.dlc.get(campaign_id: "dlc_1234567890")
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">submit</a>(campaign_id) -> Pinnacle::Types::CampaignSubmissionResult</code></summary>
+## Forms
+<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">get</a>(id) -> Pinnacle::Types::Form</code></summary>
 <dl>
 <dd>
 
@@ -3686,7 +3682,7 @@ client.campaigns.dlc.get(campaign_id: "dlc_1234567890")
 <dl>
 <dd>
 
-Submit your 10DLC campaign for approval and activation with carriers.
+Retrieve a form by id. Includes submission count, last submission timestamp, and archive state.
 </dd>
 </dl>
 </dd>
@@ -3701,7 +3697,7 @@ Submit your 10DLC campaign for approval and activation with carriers.
 <dd>
 
 ```ruby
-client.campaigns.dlc.submit(campaign_id: "dlc_1234567890")
+client.forms.get(id: "form_Oy2n7iUoi9CJwUU6")
 ```
 </dd>
 </dl>
@@ -3716,10 +3712,10 @@ client.campaigns.dlc.submit(campaign_id: "dlc_1234567890")
 <dl>
 <dd>
 
-**campaign_id:** `String` 
+**id:** `String` 
 
-Unique identifier of the 10DLC campaign to submit.
-<br><br> This identifier is a string that always begins with the prefix `dlc_`, for example: `dlc_1234567890`.
+The unique identifier of the form you want to retrieve.
+<br><br> This identifier is a string that always begins with the prefix `form_`, for example: `form_Oy2n7iUoi9CJwUU6`. It's returned on every form response (`Form.id`) and by [`POST /forms/send`](/api-reference/forms/send-form) (`response.form.id`).
     
 </dd>
 </dl>
@@ -3727,7 +3723,7 @@ Unique identifier of the 10DLC campaign to submit.
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
+**request_options:** `Pinnacle::Forms::RequestOptions` 
     
 </dd>
 </dl>
@@ -3739,7 +3735,7 @@ Unique identifier of the 10DLC campaign to submit.
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">upsert</a>(request) -> Pinnacle::Types::DlcCampaignWithExtendedBrandAndStatus</code></summary>
+<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">update</a>(id, request) -> Pinnacle::Types::Form</code></summary>
 <dl>
 <dd>
 
@@ -3751,17 +3747,7 @@ Unique identifier of the 10DLC campaign to submit.
 <dl>
 <dd>
 
-Create a new 10DLC campaign or update an existing one.
-
-<Note>
-**To create a new campaign:** Omit `campaignId` — one will be generated automatically.
-
-**Before you start:** Create a [brand](/api-reference/brands/upsert) first — you'll need its `id` for the [`brand`](#request.body.brand) field.
-
-All fields are **required** unless specified otherwise, and will be validated when [submitted](/api-reference/campaigns/10-dlc/submit).
-
-**See the response for example values for each field.**
-</Note>
+Partial update. Only keys present in the body are applied. Archived forms (non-null `archived_at`) cannot be updated — restore the form by setting `archived_at: null` in a PATCH first.
 </dd>
 </dl>
 </dd>
@@ -3776,43 +3762,11 @@ All fields are **required** unless specified otherwise, and will be validated wh
 <dd>
 
 ```ruby
-client.campaigns.dlc.upsert(
-  auto_renew: true,
-  brand: "b_1234567890",
-  description: "This campaign sends transactional SMS messages to customers who have opted in, including account notifications, security alerts, and customer care responses. Messages are sent when triggered by account activity such as login attempts, password changes, order updates, or support inquiries. All messages include required STOP/HELP disclosures and comply with TCPA guidelines.",
-  keywords: {
-    help: {
-      message: "Pinnacle Software Development Inc.: For assistance, visit https://pinnacle.sh/support or email founders@trypinnacle.app. Msg&data rates may apply. Reply STOP to cancel.",
-      values: %w[HELP SUPPORT INFO]
-    },
-    opt_in: {
-      message: "Pinnacle Software Development Inc.: You're enrolled in account & security alerts. Msg&data rates may apply. Message frequency varies. Reply HELP for help, STOP to cancel. Terms: https://pinnacle.sh/terms Privacy: https://pinnacle.sh/privacy",
-      values: %w[START YES SUBSCRIBE]
-    },
-    opt_out: {
-      message: "Pinnacle Software Development Inc.: You're unsubscribed and will receive no further texts. For assistance, visit https://pinnacle.sh or call 877-389-0460. Reply START to resubscribe.",
-      values: %w[STOP CANCEL UNSUBSCRIBE]
-    }
-  },
-  links: {
-    privacy_policy: "https://www.pinnacle.sh/privacy",
-    terms_of_service: "https://www.pinnacle.sh/terms"
-  },
-  message_flow: "The user fills out a paper form during onboarding at [Address] which they learn about at our website (https://pinnacle.sh) in which they provide their phone number and sign their consent. The form includes a disclaimer: \"By signing this form and providing your phone number, you agree to receive SMS Mixed - Account Notification, Customer Care, Security Alert, Delivery Notification from Pinnacle Software Development Inc. Message frequency may vary. Standard Message and Data Rates may apply. Reply STOP to opt out. Reply HELP for help. Consent is not a condition of purchase. Your mobile information will not be sold or shared with third parties for promotional or marketing purposes.\" Once the information is entered into the system, the user receives a confirmation SMS: \"Thank you for signing up for SMS updates from Pinnacle Software Development Inc. Msg freq may vary. Std msg & data rates apply. Reply STOP to opt out, HELP for help.\" Link to paper form: https://www.pinnacle.sh/opt-in",
-  name: "Pinnacle's Account Notifications",
-  options: {
-    affiliate_marketing: false,
-    age_gated: false,
-    direct_lending: false,
-    embedded_link: "https://www.pinnacle.sh/example",
-    embedded_phone: false,
-    number_pooling: false
-  },
-  sample_messages: ["Pinnacle Software Development Inc.: We're here to help. Visit https://pinnacle.sh or call 877-389-0460. Msg&data rates may apply. Reply STOP to cancel.", "Pinnacle Software Development Inc.: You're enrolled in account & security alerts. Msg&data rates may apply. Message frequency varies. Reply HELP for help, STOP to cancel. Terms: https://pinnacle.sh/terms/ Privacy: https://pinnacle.sh/privacy/", "Pinnacle Software Development Inc.: An update has been made to your account. Read it in the portal.", "Pinnacle Software Development Inc.: We received your message. A team member will reply shortly. For immediate help call 877-389-0460. Msg&data rates may apply. Reply STOP to cancel."],
-  use_case: {
-    sub: %w[ACCOUNT_NOTIFICATION CUSTOMER_CARE SECURITY_ALERT],
-    value: "MIXED"
-  }
+client.forms.update(
+  id: "form_Oy2n7iUoi9CJwUU6",
+  name: "Contact request (v2)",
+  can_update: true,
+  expires_at: "2026-12-31T23:59:59Z"
 )
 ```
 </dd>
@@ -3828,35 +3782,10 @@ client.campaigns.dlc.upsert(
 <dl>
 <dd>
 
-**auto_renew:** `Internal::Types::Boolean` — Whether the campaign renews automatically.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**brand:** `String` — Brand id. This identifier is a string that always begins with the prefix `b_`, for example: `b_1234567890`.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**campaign_id:** `String` — Unique identifier for the campaign. This identifier is a string that always begins with the prefix `dlc_`, for example: `dlc_1234567890`.
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**description:** `String` 
-
-Description of the campaign. Explain the purpose, use case, and types of messages your campaign will send.
+**id:** `String` 
 
-**Example:** `This campaign allows users who have specifically opted in to interact with our chatbot for a range of automated services, including order status notifications, shipping updates, security alerts, and help desk support. Users can manage their account, receive transactional SMS prompts, and access interactive support. They may also share images, such as receipts, and receive immediate responses for support or account updates. All messages are strictly transactional or support-related, never unsolicited, and initiated only after clear user consent.`
+The unique identifier of the form you want to update.
+<br><br> This identifier is a string that always begins with the prefix `form_`, for example: `form_Oy2n7iUoi9CJwUU6`.
     
 </dd>
 </dl>
@@ -3864,7 +3793,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 <dl>
 <dd>
 
-**keywords:** `Pinnacle::Campaigns::Dlc::Types::DlcCampaignKeywords` — Keyword response configuration.
+**name:** `String` — Replace the form's title. Pass `null` to clear.
     
 </dd>
 </dl>
@@ -3872,7 +3801,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 <dl>
 <dd>
 
-**links:** `Pinnacle::Campaigns::Dlc::Types::DlcCampaignLinks` — Legal documentation links.
+**description:** `String` — Replace the form's description. Pass `null` to clear.
     
 </dd>
 </dl>
@@ -3880,7 +3809,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 <dl>
 <dd>
 
-**message_flow:** `String` — Describe your opt-in workflow. See the [Opt-In Methods and Workflow](/guides/campaigns/opt-in-compliance#opt-in-methods-and-workflow) section for requirements and examples.
+**fields:** `Internal::Types::Array[Pinnacle::Types::FormField]` — Replace the full set of fields on the form. Partial field updates aren't supported — send the complete new list.
     
 </dd>
 </dl>
@@ -3888,7 +3817,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 <dl>
 <dd>
 
-**name:** `String` — Display name of the campaign.
+**can_update:** `Internal::Types::Boolean` — Toggle whether the recipient can re-edit their submission.
     
 </dd>
 </dl>
@@ -3896,7 +3825,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 <dl>
 <dd>
 
-**options:** `Pinnacle::Campaigns::Dlc::Types::DlcCampaignOptions` — Campaign configuration options.
+**expires_at:** `String` — Set or clear the form's expiration timestamp.
     
 </dd>
 </dl>
@@ -3904,7 +3833,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 <dl>
 <dd>
 
-**sample_messages:** `Internal::Types::Array[String]` — Example messages for the campaign. Include 1-5 messages that represent the types of messages you will send. See the [Sample Messages](/guides/campaigns/opt-in-compliance#sample-messages) section for requirements and examples.
+**theme_override:** `Pinnacle::Types::FormThemeOverride` — Replace the per-form theme override. Pass `null` to revert to team defaults.
     
 </dd>
 </dl>
@@ -3912,7 +3841,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 <dl>
 <dd>
 
-**use_case:** `Pinnacle::Campaigns::Dlc::Types::DlcCampaignUseCase` — Use case for the campaign.
+**archived_at:** `String` — Set to an ISO timestamp to archive the form (soft-delete), or `null` to restore an archived form.
     
 </dd>
 </dl>
@@ -3920,7 +3849,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
+**request_options:** `Pinnacle::Forms::RequestOptions` 
     
 </dd>
 </dl>
@@ -3932,7 +3861,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">validate</a>(request) -> Pinnacle::Types::CampaignValidationResult</code></summary>
+<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">list</a>(request) -> Pinnacle::Types::ListFormsResponse</code></summary>
 <dl>
 <dd>
 
@@ -3944,7 +3873,7 @@ Description of the campaign. Explain the purpose, use case, and types of message
 <dl>
 <dd>
 
-Validate your 10DLC campaign configuration against carrier requirements and compliance rules.
+Paginated list of forms on your team, sorted by creation date (newest first). Includes archived forms.
 </dd>
 </dl>
 </dd>
@@ -3959,9 +3888,9 @@ Validate your 10DLC campaign configuration against carrier requirements and comp
 <dd>
 
 ```ruby
-client.campaigns.dlc.validate(
-  additional_info: "Please validate this DLC campaign for 10DLC compliance",
-  campaign_id: "dlc_1234567890"
+client.forms.list(
+  page_index: 0,
+  page_size: 20
 )
 ```
 </dd>
@@ -3977,7 +3906,7 @@ client.campaigns.dlc.validate(
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::ValidateCampaignParams` 
+**page_index:** `Integer` — Zero-based page index.
     
 </dd>
 </dl>
@@ -3985,7 +3914,15 @@ client.campaigns.dlc.validate(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
+**page_size:** `Integer` — Number of forms to return in a single page. Max 100.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Forms::RequestOptions` 
     
 </dd>
 </dl>
@@ -3997,7 +3934,7 @@ client.campaigns.dlc.validate(
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">list</a>(request) -> Pinnacle::Types::ListDlcCampaignsResponse</code></summary>
+<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">create</a>(request) -> Pinnacle::Types::Form</code></summary>
 <dl>
 <dd>
 
@@ -4009,7 +3946,11 @@ client.campaigns.dlc.validate(
 <dl>
 <dd>
 
-List all 10DLC campaigns with optional filtering and pagination. Results are sorted by creation date, newest first.
+Create a hosted form without sending it. <br>
+
+Returns the form object including its public URL — `https://forms.pinnacle.sh/{form_id}`. <br>
+
+To also deliver the URL to a recipient over SMS or RCS in a single call, use [`POST /forms/send`](/api-reference/forms/send-form).
 </dd>
 </dl>
 </dd>
@@ -4024,7 +3965,12 @@ List all 10DLC campaigns with optional filtering and pagination. Results are sor
 <dd>
 
 ```ruby
-client.campaigns.dlc.list
+client.forms.create(
+  name: "Contact request",
+  description: "We'll follow up over SMS or RCS.",
+  fields: [],
+  can_update: false
+)
 ```
 </dd>
 </dl>
@@ -4039,7 +3985,7 @@ client.campaigns.dlc.list
 <dl>
 <dd>
 
-**page_index:** `Integer` 
+**request:** `Pinnacle::Types::FormDefinition` 
     
 </dd>
 </dl>
@@ -4047,31 +3993,83 @@ client.campaigns.dlc.list
 <dl>
 <dd>
 
-**page_size:** `Integer` 
+**request_options:** `Pinnacle::Forms::RequestOptions` 
     
 </dd>
 </dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
 
+<details><summary><code>client.forms.<a href="/lib/pinnacle/forms/client.rb">send_</a>(request) -> Pinnacle::Forms::Types::FormsSendResponse</code></summary>
 <dl>
 <dd>
 
-**status:** `Pinnacle::Campaigns::Dlc::Types::ListDlcCampaignsRequestStatus` 
-    
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Send a form to a recipient over SMS or RCS, or mint a standalone submission URL.
+
+Pass `form` as either an existing form id (`form_*`) or an inline `{ fields, ... }` definition to mint a new form for this send.
+
+The delivery channel is inferred from `from`:
+- `from: "agent_*"` → RCS (with optional SMS `fallback`)
+- `from: "+E.164"` → SMS
+
+When `to` is provided, Pinnacle dispatches a message whose body contains the submission URL and the recipient is recorded on the response: `submission.to` echoes the same E.164 number and `message_id` is the id of the outbound SMS/RCS. 
+
+When `to` is omitted, no message is sent — `submission.to` and `message_id` are both `null` — which is useful for embedding the URL in your own outreach.
+
+On completion, a `FORM.SUBMISSION` webhook event is delivered to webhooks subscribed to the sender. See [Receiving Message, Call, and User Events](/guides/messages/receiving).
+</dd>
+</dl>
 </dd>
 </dl>
 
+#### 🔌 Usage
+
 <dl>
 <dd>
 
-**brand_id:** `String` 
-    
+<dl>
+<dd>
+
+```ruby
+client.forms.send_(
+  from: "agent_iM9wQcyBBjYn",
+  to: "+14155551234",
+  form: "form_Oy2n7iUoi9CJwUU6",
+  fallback: {
+    from: "+14155550000"
+  },
+  options: {
+    webview_mode: "FULL"
+  }
+)
+```
+</dd>
+</dl>
 </dd>
 </dl>
 
+#### ⚙️ Parameters
+
 <dl>
 <dd>
 
-**name:** `String` — Filter by campaign name (partial match, case-insensitive).
+<dl>
+<dd>
+
+**request:** `Pinnacle::Types::SendFormParams` 
     
 </dd>
 </dl>
@@ -4079,7 +4077,7 @@ client.campaigns.dlc.list
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
+**request_options:** `Pinnacle::Forms::RequestOptions` 
     
 </dd>
 </dl>
@@ -4091,8 +4089,8 @@ client.campaigns.dlc.list
 </dl>
 </details>
 
-## Campaigns TollFree
-<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">autofill</a>(request) -> Pinnacle::Campaigns::TollFree::Types::TollFreeAutofillResponse</code></summary>
+## Audiences Contacts
+<details><summary><code>client.audiences.contacts.<a href="/lib/pinnacle/audiences/contacts/client.rb">remove</a>(request) -> Pinnacle::Types::AudienceCountOnly</code></summary>
 <dl>
 <dd>
 
@@ -4104,7 +4102,10 @@ client.campaigns.dlc.list
 <dl>
 <dd>
 
-Generate campaign details based off existing campaign and the brand it's connected to.
+Remove contacts from an existing audience. This operation is idempotent.
+
+- Only removes contacts that exist in the audience
+- Contacts not in the audience are ignored
 </dd>
 </dl>
 </dd>
@@ -4119,9 +4120,9 @@ Generate campaign details based off existing campaign and the brand it's connect
 <dd>
 
 ```ruby
-client.campaigns.toll_free.autofill(
-  additional_info: "Please autofill missing campaign fields using my brand profile",
-  campaign_id: "dlc_1234567890"
+client.audiences.contacts.remove(
+  id: "aud_abc123",
+  contacts: %w[+12125551234 co_def456]
 )
 ```
 </dd>
@@ -4137,7 +4138,7 @@ client.campaigns.toll_free.autofill(
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::AutofillCampaignParams` 
+**id:** `String` — Audience ID. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`.
     
 </dd>
 </dl>
@@ -4145,7 +4146,18 @@ client.campaigns.toll_free.autofill(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
+**contacts:** `Internal::Types::Array[String]` 
+
+Array of phone numbers (E.164 format) or contact IDs. <br><br>
+**Limit:** 1 min
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Audiences::Contacts::RequestOptions` 
     
 </dd>
 </dl>
@@ -4157,7 +4169,7 @@ client.campaigns.toll_free.autofill(
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">get</a>(campaign_id) -> Pinnacle::Types::TollFreeCampaignWithExtendedBrandAndStatus</code></summary>
+<details><summary><code>client.audiences.contacts.<a href="/lib/pinnacle/audiences/contacts/client.rb">add</a>(request) -> Pinnacle::Types::AudienceCountOnly</code></summary>
 <dl>
 <dd>
 
@@ -4169,7 +4181,11 @@ client.campaigns.toll_free.autofill(
 <dl>
 <dd>
 
-Retrieve Toll-Free campaign.
+Add contacts to an existing audience. This operation is additive and idempotent.
+
+- Phone numbers that don't exist will be auto-created as contacts
+- Duplicate adds are ignored
+- Contacts already in the audience are ignored
 </dd>
 </dl>
 </dd>
@@ -4184,7 +4200,10 @@ Retrieve Toll-Free campaign.
 <dd>
 
 ```ruby
-client.campaigns.toll_free.get(campaign_id: "tf_1234567890")
+client.audiences.contacts.add(
+  id: "aud_abc123",
+  contacts: %w[+12125551234 co_def456 +13105551234]
+)
 ```
 </dd>
 </dl>
@@ -4199,7 +4218,7 @@ client.campaigns.toll_free.get(campaign_id: "tf_1234567890")
 <dl>
 <dd>
 
-**campaign_id:** `String` — Unique identifier of toll-free campaign. Must begin with the prefix `tf_`.
+**id:** `String` — Audience ID. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`.
     
 </dd>
 </dl>
@@ -4207,7 +4226,18 @@ client.campaigns.toll_free.get(campaign_id: "tf_1234567890")
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
+**contacts:** `Internal::Types::Array[String]` 
+
+Array of phone numbers (E.164 format) or contact IDs. <br><br>
+**Limit:** 1 min
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Audiences::Contacts::RequestOptions` 
     
 </dd>
 </dl>
@@ -4219,7 +4249,8 @@ client.campaigns.toll_free.get(campaign_id: "tf_1234567890")
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">submit</a>(campaign_id) -> Pinnacle::Types::CampaignSubmissionResult</code></summary>
+## Campaigns Dlc
+<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">autofill</a>(request) -> Pinnacle::Types::AutofillDlcCampaignResponse</code></summary>
 <dl>
 <dd>
 
@@ -4231,7 +4262,7 @@ client.campaigns.toll_free.get(campaign_id: "tf_1234567890")
 <dl>
 <dd>
 
-Submit your toll-free campaign for approval and activation with carriers.
+Generate campaign details based off existing campaign and the brand it's connected to.
 </dd>
 </dl>
 </dd>
@@ -4246,7 +4277,10 @@ Submit your toll-free campaign for approval and activation with carriers.
 <dd>
 
 ```ruby
-client.campaigns.toll_free.submit(campaign_id: "tf_1234567890")
+client.campaigns.dlc.autofill(
+  additional_info: "Please autofill missing campaign fields using my brand profile",
+  campaign_id: "dlc_1234567890"
+)
 ```
 </dd>
 </dl>
@@ -4261,7 +4295,7 @@ client.campaigns.toll_free.submit(campaign_id: "tf_1234567890")
 <dl>
 <dd>
 
-**campaign_id:** `String` — Unique identifier of the toll-free campaign to submit. Must begin with the prefix `tf_`.
+**request:** `Pinnacle::Types::AutofillCampaignParams` 
     
 </dd>
 </dl>
@@ -4269,7 +4303,7 @@ client.campaigns.toll_free.submit(campaign_id: "tf_1234567890")
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
+**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
     
 </dd>
 </dl>
@@ -4281,7 +4315,7 @@ client.campaigns.toll_free.submit(campaign_id: "tf_1234567890")
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">upsert</a>(request) -> Pinnacle::Types::TollFreeCampaignWithExtendedBrandAndStatus</code></summary>
+<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">get</a>(campaign_id) -> Pinnacle::Types::DlcCampaignWithExtendedBrandAndStatus</code></summary>
 <dl>
 <dd>
 
@@ -4293,14 +4327,141 @@ client.campaigns.toll_free.submit(campaign_id: "tf_1234567890")
 <dl>
 <dd>
 
-Create a new toll-free campaign or update an existing one.
+Retrieve 10DLC campaign.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.dlc.get(campaign_id: "dlc_1234567890")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**campaign_id:** `String` — Unique identifier of the 10DLC campaign. This identifier is a string that always begins with the prefix `dlc_`, for example: `dlc_1234567890`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">submit</a>(campaign_id) -> Pinnacle::Types::CampaignSubmissionResult</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Submit your 10DLC campaign for approval and activation with carriers.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.dlc.submit(campaign_id: "dlc_1234567890")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**campaign_id:** `String` 
+
+Unique identifier of the 10DLC campaign to submit.
+<br><br> This identifier is a string that always begins with the prefix `dlc_`, for example: `dlc_1234567890`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">upsert</a>(request) -> Pinnacle::Types::DlcCampaignWithExtendedBrandAndStatus</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Create a new 10DLC campaign or update an existing one.
 
 <Note>
 **To create a new campaign:** Omit `campaignId` — one will be generated automatically.
 
 **Before you start:** Create a [brand](/api-reference/brands/upsert) first — you'll need its `id` for the [`brand`](#request.body.brand) field.
 
-All fields are **required** unless specified otherwise, and will be validated when [submitted](/api-reference/campaigns/toll-free/submit).
+All fields are **required** unless specified otherwise, and will be validated when [submitted](/api-reference/campaigns/10-dlc/submit).
 
 **See the response for example values for each field.**
 </Note>
@@ -4318,36 +4479,42 @@ All fields are **required** unless specified otherwise, and will be validated wh
 <dd>
 
 ```ruby
-client.campaigns.toll_free.upsert(
+client.campaigns.dlc.upsert(
+  auto_renew: true,
   brand: "b_1234567890",
-  campaign_id: "tf_1234567890",
+  description: "This campaign sends transactional SMS messages to customers who have opted in, including account notifications, security alerts, and customer care responses. Messages are sent when triggered by account activity such as login attempts, password changes, order updates, or support inquiries. All messages include required STOP/HELP disclosures and comply with TCPA guidelines.",
   keywords: {
     help: {
-      message: "Pinnacle Software Development Inc.: For assistance, visit https://pinnacle.sh/support or email founders@trypinnacle.app. Msg&data rates may apply. Reply STOP to cancel."
+      message: "Pinnacle Software Development Inc.: For assistance, visit https://pinnacle.sh/support or email founders@trypinnacle.app. Msg&data rates may apply. Reply STOP to cancel.",
+      values: %w[HELP SUPPORT INFO]
     },
     opt_in: {
-      message: "Pinnacle Software Development Inc.: You're enrolled in account & security alerts. Msg&data rates may apply. Message frequency varies. Reply HELP for help, STOP to cancel. Terms: https://pinnacle.sh/terms/ Privacy: https://pinnacle.sh/privacy/",
-      keywords: %w[START SUBSCRIBE]
+      message: "Pinnacle Software Development Inc.: You're enrolled in account & security alerts. Msg&data rates may apply. Message frequency varies. Reply HELP for help, STOP to cancel. Terms: https://pinnacle.sh/terms Privacy: https://pinnacle.sh/privacy",
+      values: %w[START YES SUBSCRIBE]
+    },
+    opt_out: {
+      message: "Pinnacle Software Development Inc.: You're unsubscribed and will receive no further texts. For assistance, visit https://pinnacle.sh or call 877-389-0460. Reply START to resubscribe.",
+      values: %w[STOP CANCEL UNSUBSCRIBE]
     }
   },
   links: {
     privacy_policy: "https://www.pinnacle.sh/privacy",
     terms_of_service: "https://www.pinnacle.sh/terms"
   },
-  monthly_volume: "10,000",
-  name: "Pinnacle",
-  opt_in: {
-    method_: "PAPER",
-    url: "https://www.pinnacle.sh/opt-in",
-    workflow_description: "End users opt-in when filling out the in-person intake forms where they will write their phone numbers and check a box indicating that they've opted in to messages. Link to paper form: https://www.pinnacle.sh/opt-in"
-  },
+  message_flow: "The user fills out a paper form during onboarding at [Address] which they learn about at our website (https://pinnacle.sh) in which they provide their phone number and sign their consent. The form includes a disclaimer: \"By signing this form and providing your phone number, you agree to receive SMS Mixed - Account Notification, Customer Care, Security Alert, Delivery Notification from Pinnacle Software Development Inc. Message frequency may vary. Standard Message and Data Rates may apply. Reply STOP to opt out. Reply HELP for help. Consent is not a condition of purchase. Your mobile information will not be sold or shared with third parties for promotional or marketing purposes.\" Once the information is entered into the system, the user receives a confirmation SMS: \"Thank you for signing up for SMS updates from Pinnacle Software Development Inc. Msg freq may vary. Std msg & data rates apply. Reply STOP to opt out, HELP for help.\" Link to paper form: https://www.pinnacle.sh/opt-in",
+  name: "Pinnacle's Account Notifications",
   options: {
-    age_gated: false
+    affiliate_marketing: false,
+    age_gated: false,
+    direct_lending: false,
+    embedded_link: "https://www.pinnacle.sh/example",
+    embedded_phone: false,
+    number_pooling: false
   },
-  production_message_content: "Hi [First Name], your order #[Order ID] has shipped and will arrive [Date]. Track here: [URL]. Reply HELP for help or STOP to unsubscribe.",
+  sample_messages: ["Pinnacle Software Development Inc.: We're here to help. Visit https://pinnacle.sh or call 877-389-0460. Msg&data rates may apply. Reply STOP to cancel.", "Pinnacle Software Development Inc.: You're enrolled in account & security alerts. Msg&data rates may apply. Message frequency varies. Reply HELP for help, STOP to cancel. Terms: https://pinnacle.sh/terms/ Privacy: https://pinnacle.sh/privacy/", "Pinnacle Software Development Inc.: An update has been made to your account. Read it in the portal.", "Pinnacle Software Development Inc.: We received your message. A team member will reply shortly. For immediate help call 877-389-0460. Msg&data rates may apply. Reply STOP to cancel."],
   use_case: {
-    summary: "Customers who have opted into text messages can interact with our automated SMS chatbot to receive transaction-driven notifications (order status, shipping updates, account alerts), ask support questions, share photos with friends, and manage their account details via simple, conversational text flows. All messages are transactional or interactive flows customers opt into. Users can send images (e.g., receipts) and get guided replies.",
-    value: "CHATBOT"
+    sub: %w[ACCOUNT_NOTIFICATION CUSTOMER_CARE SECURITY_ALERT],
+    value: "MIXED"
   }
 )
 ```
@@ -4364,6 +4531,14 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
+**auto_renew:** `Internal::Types::Boolean` — Whether the campaign renews automatically.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **brand:** `String` — Brand id. This identifier is a string that always begins with the prefix `b_`, for example: `b_1234567890`.
     
 </dd>
@@ -4372,7 +4547,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**campaign_id:** `String` — Unique identifier for the campaign. This identifier is a string that always begins with the prefix `tf_`, for example: `tf_1234567890`.
+**campaign_id:** `String` — Unique identifier for the campaign. This identifier is a string that always begins with the prefix `dlc_`, for example: `dlc_1234567890`.
     
 </dd>
 </dl>
@@ -4380,7 +4555,11 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**keywords:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignKeywords` — Keyword response configuration.
+**description:** `String` 
+
+Description of the campaign. Explain the purpose, use case, and types of messages your campaign will send.
+
+**Example:** `This campaign allows users who have specifically opted in to interact with our chatbot for a range of automated services, including order status notifications, shipping updates, security alerts, and help desk support. Users can manage their account, receive transactional SMS prompts, and access interactive support. They may also share images, such as receipts, and receive immediate responses for support or account updates. All messages are strictly transactional or support-related, never unsolicited, and initiated only after clear user consent.`
     
 </dd>
 </dl>
@@ -4388,7 +4567,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**links:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignLinks` — Legal documentation links.
+**keywords:** `Pinnacle::Campaigns::Dlc::Types::DlcCampaignKeywords` — Keyword response configuration.
     
 </dd>
 </dl>
@@ -4396,7 +4575,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**monthly_volume:** `Pinnacle::Types::MessageVolumeEnum` 
+**links:** `Pinnacle::Campaigns::Dlc::Types::DlcCampaignLinks` — Legal documentation links.
     
 </dd>
 </dl>
@@ -4404,7 +4583,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**name:** `String` — Display name of the campaign. This is not sent to carriers for approval and is only used for your reference on the Pinnacle dashboard.
+**message_flow:** `String` — Describe your opt-in workflow. See the [Opt-In Methods and Workflow](/guides/campaigns/opt-in-compliance#opt-in-methods-and-workflow) section for requirements and examples.
     
 </dd>
 </dl>
@@ -4412,7 +4591,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**opt_in:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignOptIn` — Opt-in method and workflow.
+**name:** `String` — Display name of the campaign.
     
 </dd>
 </dl>
@@ -4420,7 +4599,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**options:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignOptions` — Campaign configuration options.
+**options:** `Pinnacle::Campaigns::Dlc::Types::DlcCampaignOptions` — Campaign configuration options.
     
 </dd>
 </dl>
@@ -4428,7 +4607,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**production_message_content:** `String` — Example message(s) that would be sent in production. Should reflect the actual content users will receive, including HELP/STOP disclosures. See the [Production Message Content](/guides/campaigns/opt-in-compliance#production-message-content) section for requirements.
+**sample_messages:** `Internal::Types::Array[String]` — Example messages for the campaign. Include 1-5 messages that represent the types of messages you will send. See the [Sample Messages](/guides/campaigns/opt-in-compliance#sample-messages) section for requirements and examples.
     
 </dd>
 </dl>
@@ -4436,7 +4615,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**use_case:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignUseCase` — Use case classification for the campaign.
+**use_case:** `Pinnacle::Campaigns::Dlc::Types::DlcCampaignUseCase` — Use case for the campaign.
     
 </dd>
 </dl>
@@ -4444,7 +4623,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
+**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
     
 </dd>
 </dl>
@@ -4456,7 +4635,7 @@ client.campaigns.toll_free.upsert(
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">validate</a>(request) -> Pinnacle::Types::CampaignValidationResult</code></summary>
+<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">validate</a>(request) -> Pinnacle::Types::CampaignValidationResult</code></summary>
 <dl>
 <dd>
 
@@ -4468,7 +4647,7 @@ client.campaigns.toll_free.upsert(
 <dl>
 <dd>
 
-Validate your toll-free campaign configuration against carrier requirements and compliance rules.
+Validate your 10DLC campaign configuration against carrier requirements and compliance rules.
 </dd>
 </dl>
 </dd>
@@ -4483,7 +4662,7 @@ Validate your toll-free campaign configuration against carrier requirements and
 <dd>
 
 ```ruby
-client.campaigns.toll_free.validate(
+client.campaigns.dlc.validate(
   additional_info: "Please validate this DLC campaign for 10DLC compliance",
   campaign_id: "dlc_1234567890"
 )
@@ -4509,7 +4688,7 @@ client.campaigns.toll_free.validate(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
+**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
     
 </dd>
 </dl>
@@ -4521,7 +4700,7 @@ client.campaigns.toll_free.validate(
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">list</a>(request) -> Pinnacle::Types::ListTollFreeCampaignsResponse</code></summary>
+<details><summary><code>client.campaigns.dlc.<a href="/lib/pinnacle/campaigns/dlc/client.rb">list</a>(request) -> Pinnacle::Types::ListDlcCampaignsResponse</code></summary>
 <dl>
 <dd>
 
@@ -4533,7 +4712,7 @@ client.campaigns.toll_free.validate(
 <dl>
 <dd>
 
-List all toll-free campaigns with optional filtering and pagination. Results are sorted by creation date, newest first.
+List all 10DLC campaigns with optional filtering and pagination. Results are sorted by creation date, newest first.
 </dd>
 </dl>
 </dd>
@@ -4548,7 +4727,7 @@ List all toll-free campaigns with optional filtering and pagination. Results are
 <dd>
 
 ```ruby
-client.campaigns.toll_free.list
+client.campaigns.dlc.list
 ```
 </dd>
 </dl>
@@ -4579,7 +4758,7 @@ client.campaigns.toll_free.list
 <dl>
 <dd>
 
-**status:** `Pinnacle::Campaigns::TollFree::Types::ListTollFreeCampaignsRequestStatus` 
+**status:** `Pinnacle::Campaigns::Dlc::Types::ListDlcCampaignsRequestStatus` 
     
 </dd>
 </dl>
@@ -4603,7 +4782,7 @@ client.campaigns.toll_free.list
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
+**request_options:** `Pinnacle::Campaigns::Dlc::RequestOptions` 
     
 </dd>
 </dl>
@@ -4615,8 +4794,8 @@ client.campaigns.toll_free.list
 </dl>
 </details>
 
-## Campaigns Rcs
-<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">autofill</a>(request) -> Pinnacle::Campaigns::Rcs::Types::RcsAutofillResponse</code></summary>
+## Campaigns TollFree
+<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">autofill</a>(request) -> Pinnacle::Campaigns::TollFree::Types::TollFreeAutofillResponse</code></summary>
 <dl>
 <dd>
 
@@ -4643,7 +4822,7 @@ Generate campaign details based off existing campaign and the brand it's connect
 <dd>
 
 ```ruby
-client.campaigns.rcs.autofill(
+client.campaigns.toll_free.autofill(
   additional_info: "Please autofill missing campaign fields using my brand profile",
   campaign_id: "dlc_1234567890"
 )
@@ -4669,7 +4848,7 @@ client.campaigns.rcs.autofill(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
     
 </dd>
 </dl>
@@ -4681,7 +4860,7 @@ client.campaigns.rcs.autofill(
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">get</a>(campaign_id) -> Pinnacle::Types::ExtendedRcsCampaign</code></summary>
+<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">get</a>(campaign_id) -> Pinnacle::Types::TollFreeCampaignWithExtendedBrandAndStatus</code></summary>
 <dl>
 <dd>
 
@@ -4693,7 +4872,7 @@ client.campaigns.rcs.autofill(
 <dl>
 <dd>
 
-Retrieve RCS campaign.
+Retrieve Toll-Free campaign.
 </dd>
 </dl>
 </dd>
@@ -4708,7 +4887,7 @@ Retrieve RCS campaign.
 <dd>
 
 ```ruby
-client.campaigns.rcs.get(campaign_id: "rcs_1234567890")
+client.campaigns.toll_free.get(campaign_id: "tf_1234567890")
 ```
 </dd>
 </dl>
@@ -4723,7 +4902,7 @@ client.campaigns.rcs.get(campaign_id: "rcs_1234567890")
 <dl>
 <dd>
 
-**campaign_id:** `String` — Unique identifier of the RCS campaign. Must begin with the prefix `rcs_`.
+**campaign_id:** `String` — Unique identifier of toll-free campaign. Must begin with the prefix `tf_`.
     
 </dd>
 </dl>
@@ -4731,7 +4910,7 @@ client.campaigns.rcs.get(campaign_id: "rcs_1234567890")
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
     
 </dd>
 </dl>
@@ -4743,7 +4922,7 @@ client.campaigns.rcs.get(campaign_id: "rcs_1234567890")
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">submit</a>(campaign_id) -> Pinnacle::Types::CampaignSubmissionResult</code></summary>
+<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">submit</a>(campaign_id) -> Pinnacle::Types::CampaignSubmissionResult</code></summary>
 <dl>
 <dd>
 
@@ -4755,7 +4934,7 @@ client.campaigns.rcs.get(campaign_id: "rcs_1234567890")
 <dl>
 <dd>
 
-Submit your RCS campaign for approval and activation with carriers.
+Submit your toll-free campaign for approval and activation with carriers.
 </dd>
 </dl>
 </dd>
@@ -4770,7 +4949,7 @@ Submit your RCS campaign for approval and activation with carriers.
 <dd>
 
 ```ruby
-client.campaigns.rcs.submit(campaign_id: "rcs_1234567890")
+client.campaigns.toll_free.submit(campaign_id: "tf_1234567890")
 ```
 </dd>
 </dl>
@@ -4785,7 +4964,7 @@ client.campaigns.rcs.submit(campaign_id: "rcs_1234567890")
 <dl>
 <dd>
 
-**campaign_id:** `String` — Unique identifier of the RCS campaign to retrieve. Must begin with the prefix `rcs_`.
+**campaign_id:** `String` — Unique identifier of the toll-free campaign to submit. Must begin with the prefix `tf_`.
     
 </dd>
 </dl>
@@ -4793,7 +4972,7 @@ client.campaigns.rcs.submit(campaign_id: "rcs_1234567890")
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
     
 </dd>
 </dl>
@@ -4805,7 +4984,7 @@ client.campaigns.rcs.submit(campaign_id: "rcs_1234567890")
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">upsert</a>(request) -> Pinnacle::Types::ExtendedRcsCampaign</code></summary>
+<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">upsert</a>(request) -> Pinnacle::Types::TollFreeCampaignWithExtendedBrandAndStatus</code></summary>
 <dl>
 <dd>
 
@@ -4817,14 +4996,16 @@ client.campaigns.rcs.submit(campaign_id: "rcs_1234567890")
 <dl>
 <dd>
 
-Create a new RCS campaign or update an existing one.
+Create a new toll-free campaign or update an existing one.
 
 <Note>
 **To create a new campaign:** Omit `campaignId` — one will be generated automatically.
 
 **Before you start:** Create a [brand](/api-reference/brands/upsert) first — you'll need its `id` for the [`brand`](#request.body.brand) field.
 
-All fields are **required** unless specified otherwise, and will be validated when [submitted](/api-reference/campaigns/rcs/submit).
+All fields are **required** unless specified otherwise, and will be validated when [submitted](/api-reference/campaigns/toll-free/submit).
+
+**See the response for example values for each field.**
 </Note>
 </dd>
 </dl>
@@ -4840,65 +5021,174 @@ All fields are **required** unless specified otherwise, and will be validated wh
 <dd>
 
 ```ruby
-client.campaigns.rcs.upsert(
-  agent: {
-    color: "#000000",
-    description: "Experience the power of RCS messaging with interactive demos. Test rich features like carousels, suggested replies, and media sharing. Get started with our developer-friendly APIs.",
-    emails: [{
-      email: "founders@trypinnacle.app",
-      label: "Email Us"
-    }],
-    hero_url: "https://pncl.to/D6pDSqGxqgfbCfQmw4gXdnlHu4uSB4",
-    icon_url: "https://pncl.to/mq_tdIDenRb5eYpJiM8-3THCaUBrZP",
-    name: "Pinnacle - RCS Demo",
-    phones: [{
-      label: "Contact us directly",
-      phone: "+14154467821"
-    }],
-    websites: [{
-      label: "Get started with Pinnacle",
-      url: "https://www.trypinnacle.app/"
-    }]
-  },
+client.campaigns.toll_free.upsert(
   brand: "b_1234567890",
-  campaign_id: "rcs_1234567890",
-  expected_agent_responses: ["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: {
-    privacy_policy: "“https://www.trypinnacle.app/privacy”",
-    terms_of_service: "“https://www.trypinnacle.app/terms”"
-  },
-  use_case_description: "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 “onboarding guide” for new customers and a “best-practices coach” for existing teams exploring higher-value RCS workflows like rich cards, carousels, and suggested actions.<br>
-  The agent delivers a mix of operational updates and educational content (2–6 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.
-  ",
-  messaging_type: "OTP",
-  cta_media: "“https://www.pinnacle.sh/send”",
-  opt_in_method: "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>
-  Users 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.
-  ",
+  campaign_id: "tf_1234567890",
   keywords: {
     help: {
-      message: "Email founders@trypinnacle.app for support.",
-      keywords: %w[HELP SUPPORT]
+      message: "Pinnacle Software Development Inc.: For assistance, visit https://pinnacle.sh/support or email founders@trypinnacle.app. Msg&data rates may apply. Reply STOP to cancel."
     },
     opt_in: {
-      message: "Welcome back to Pinnacle!<br>
-      🔔 You're now subscribed to Pinnacle - RCS Demo and will continue receiving important updates and news. Feel free to contact this us at any time for help.<br>
-      
-      Reply STOP to opt out and HELP for support. Message & rates may apply.
-      ",
+      message: "Pinnacle Software Development Inc.: You're enrolled in account & security alerts. Msg&data rates may apply. Message frequency varies. Reply HELP for help, STOP to cancel. Terms: https://pinnacle.sh/terms/ Privacy: https://pinnacle.sh/privacy/",
       keywords: %w[START SUBSCRIBE]
-    },
-    opt_out: {
-      message: "You've been unsubscribed from Pinnacle - RCS Demo and will no longer receive notifications. If you ever change your mind, reply START or SUBSCRIBE to rejoin anytime.",
-      keywords: %w[STOP UNSUBSCRIBE END]
     }
   },
-  traffic: {
-    monthly_website: 10000,
-    monthly_rcs_estimate: 10000
+  links: {
+    privacy_policy: "https://www.pinnacle.sh/privacy",
+    terms_of_service: "https://www.pinnacle.sh/terms"
   },
-  cta_language: "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.",
-  demo_trigger: "Text \"START\" to trigger the flow."
+  monthly_volume: "10,000",
+  name: "Pinnacle",
+  opt_in: {
+    method_: "PAPER",
+    url: "https://www.pinnacle.sh/opt-in",
+    workflow_description: "End users opt-in when filling out the in-person intake forms where they will write their phone numbers and check a box indicating that they've opted in to messages. Link to paper form: https://www.pinnacle.sh/opt-in"
+  },
+  options: {
+    age_gated: false
+  },
+  production_message_content: "Hi [First Name], your order #[Order ID] has shipped and will arrive [Date]. Track here: [URL]. Reply HELP for help or STOP to unsubscribe.",
+  use_case: {
+    summary: "Customers who have opted into text messages can interact with our automated SMS chatbot to receive transaction-driven notifications (order status, shipping updates, account alerts), ask support questions, share photos with friends, and manage their account details via simple, conversational text flows. All messages are transactional or interactive flows customers opt into. Users can send images (e.g., receipts) and get guided replies.",
+    value: "CHATBOT"
+  }
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**brand:** `String` — Brand id. This identifier is a string that always begins with the prefix `b_`, for example: `b_1234567890`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**campaign_id:** `String` — Unique identifier for the campaign. This identifier is a string that always begins with the prefix `tf_`, for example: `tf_1234567890`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**keywords:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignKeywords` — Keyword response configuration.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**links:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignLinks` — Legal documentation links.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**monthly_volume:** `Pinnacle::Types::MessageVolumeEnum` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**name:** `String` — Display name of the campaign. This is not sent to carriers for approval and is only used for your reference on the Pinnacle dashboard.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**opt_in:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignOptIn` — Opt-in method and workflow.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**options:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignOptions` — Campaign configuration options.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**production_message_content:** `String` — Example message(s) that would be sent in production. Should reflect the actual content users will receive, including HELP/STOP disclosures. See the [Production Message Content](/guides/campaigns/opt-in-compliance#production-message-content) section for requirements.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**use_case:** `Pinnacle::Campaigns::TollFree::Types::TollFreeCampaignUseCase` — Use case classification for the campaign.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">validate</a>(request) -> Pinnacle::Types::CampaignValidationResult</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Validate your toll-free campaign configuration against carrier requirements and compliance rules.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.toll_free.validate(
+  additional_info: "Please validate this DLC campaign for 10DLC compliance",
+  campaign_id: "dlc_1234567890"
 )
 ```
 </dd>
@@ -4906,7 +5196,725 @@ client.campaigns.rcs.upsert(
 </dd>
 </dl>
 
-#### ⚙️ Parameters
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `Pinnacle::Types::ValidateCampaignParams` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.campaigns.toll_free.<a href="/lib/pinnacle/campaigns/toll_free/client.rb">list</a>(request) -> Pinnacle::Types::ListTollFreeCampaignsResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+List all toll-free campaigns with optional filtering and pagination. Results are sorted by creation date, newest first.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.toll_free.list
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**page_index:** `Integer` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**page_size:** `Integer` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**status:** `Pinnacle::Campaigns::TollFree::Types::ListTollFreeCampaignsRequestStatus` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**brand_id:** `String` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**name:** `String` — Filter by campaign name (partial match, case-insensitive).
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::TollFree::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+## Campaigns Rcs
+<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">autofill</a>(request) -> Pinnacle::Campaigns::Rcs::Types::RcsAutofillResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Generate campaign details based off existing campaign and the brand it's connected to.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.rcs.autofill(
+  additional_info: "Please autofill missing campaign fields using my brand profile",
+  campaign_id: "dlc_1234567890"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `Pinnacle::Types::AutofillCampaignParams` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">get</a>(campaign_id) -> Pinnacle::Types::ExtendedRcsCampaign</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Retrieve RCS campaign.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.rcs.get(campaign_id: "rcs_1234567890")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**campaign_id:** `String` — Unique identifier of the RCS campaign. Must begin with the prefix `rcs_`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">submit</a>(campaign_id) -> Pinnacle::Types::CampaignSubmissionResult</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Submit your RCS campaign for approval and activation with carriers.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.rcs.submit(campaign_id: "rcs_1234567890")
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**campaign_id:** `String` — Unique identifier of the RCS campaign to retrieve. Must begin with the prefix `rcs_`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">upsert</a>(request) -> Pinnacle::Types::ExtendedRcsCampaign</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Create a new RCS campaign or update an existing one.
+
+<Note>
+**To create a new campaign:** Omit `campaignId` — one will be generated automatically.
+
+**Before you start:** Create a [brand](/api-reference/brands/upsert) first — you'll need its `id` for the [`brand`](#request.body.brand) field.
+
+All fields are **required** unless specified otherwise, and will be validated when [submitted](/api-reference/campaigns/rcs/submit).
+</Note>
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.rcs.upsert(
+  agent: {
+    color: "#000000",
+    description: "Experience the power of RCS messaging with interactive demos. Test rich features like carousels, suggested replies, and media sharing. Get started with our developer-friendly APIs.",
+    emails: [{
+      email: "founders@trypinnacle.app",
+      label: "Email Us"
+    }],
+    hero_url: "https://pncl.to/D6pDSqGxqgfbCfQmw4gXdnlHu4uSB4",
+    icon_url: "https://pncl.to/mq_tdIDenRb5eYpJiM8-3THCaUBrZP",
+    name: "Pinnacle - RCS Demo",
+    phones: [{
+      label: "Contact us directly",
+      phone: "+14154467821"
+    }],
+    websites: [{
+      label: "Get started with Pinnacle",
+      url: "https://www.trypinnacle.app/"
+    }]
+  },
+  brand: "b_1234567890",
+  campaign_id: "rcs_1234567890",
+  expected_agent_responses: ["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: {
+    privacy_policy: "“https://www.trypinnacle.app/privacy”",
+    terms_of_service: "“https://www.trypinnacle.app/terms”"
+  },
+  use_case_description: "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 “onboarding guide” for new customers and a “best-practices coach” for existing teams exploring higher-value RCS workflows like rich cards, carousels, and suggested actions.<br>
+  The agent delivers a mix of operational updates and educational content (2–6 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.
+  ",
+  messaging_type: "OTP",
+  cta_media: "“https://www.pinnacle.sh/send”",
+  opt_in_method: "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>
+  Users 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.
+  ",
+  keywords: {
+    help: {
+      message: "Email founders@trypinnacle.app for support.",
+      keywords: %w[HELP SUPPORT]
+    },
+    opt_in: {
+      message: "Welcome back to Pinnacle!<br>
+      🔔 You're now subscribed to Pinnacle - RCS Demo and will continue receiving important updates and news. Feel free to contact this us at any time for help.<br>
+      
+      Reply STOP to opt out and HELP for support. Message & rates may apply.
+      ",
+      keywords: %w[START SUBSCRIBE]
+    },
+    opt_out: {
+      message: "You've been unsubscribed from Pinnacle - RCS Demo and will no longer receive notifications. If you ever change your mind, reply START or SUBSCRIBE to rejoin anytime.",
+      keywords: %w[STOP UNSUBSCRIBE END]
+    }
+  },
+  traffic: {
+    monthly_website: 10000,
+    monthly_rcs_estimate: 10000
+  },
+  cta_language: "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.",
+  demo_trigger: "Text \"START\" to trigger the flow."
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**agent:** `Pinnacle::Campaigns::Rcs::Types::RcsAgent` — Create an agent for the campaign.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**brand:** `String` — Unique identifier for the brand.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**campaign_id:** `String` — Unique identifier for the campaign.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**expected_agent_responses:** `Internal::Types::Array[String]` 
+
+List of what the agent might say to users. See the [Expected Agent Responses](/guides/campaigns/rcs-compliance#expected-agent-responses) section for requirements. <br><br>
+**Limit:** 1 to 5
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**links:** `Pinnacle::Campaigns::Rcs::Types::RcsLinks` — Legal documentation links.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**use_case_description:** `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.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**messaging_type:** `Pinnacle::Types::RcsMessagingTypeEnum` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**cta_media:** `String` — URL to the opt-in form or a URL to a screenshot of the opt-in CTA.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**opt_in_method:** `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.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**keywords:** `Pinnacle::Campaigns::Rcs::Types::RcsCampaignKeywords` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**traffic:** `Pinnacle::Campaigns::Rcs::Types::RcsCampaignTraffic` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**cta_language:** `String` — 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.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**demo_trigger:** `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.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">validate</a>(request) -> Pinnacle::Types::CampaignValidationResult</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Validate your RCS campaign configuration against carrier requirements and compliance rules.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.rcs.validate(
+  additional_info: "Please validate this DLC campaign for 10DLC compliance",
+  campaign_id: "dlc_1234567890"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `Pinnacle::Types::ValidateCampaignParams` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">list</a>(request) -> Pinnacle::Types::ListRcsCampaignsResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+List all RCS campaigns with optional filtering and pagination. Results are sorted by creation date, newest first.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.campaigns.rcs.list
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**page_index:** `Integer` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**page_size:** `Integer` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**status:** `Pinnacle::Campaigns::Rcs::Types::ListRcsCampaignsRequestStatus` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**brand_id:** `String` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**name:** `String` — Filter by campaign name (partial match, case-insensitive).
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+## Forms Submissions
+<details><summary><code>client.forms.submissions.<a href="/lib/pinnacle/forms/submissions/client.rb">list</a>(id, request) -> Pinnacle::Types::ListFormSubmissionsResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Paginated list of completed submissions for a form, newest first. Each row includes the submitted `data` keyed by field `key`, the sender/recipient, IP, user-agent, and timestamps.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
 
 <dl>
 <dd>
@@ -4914,15 +5922,30 @@ client.campaigns.rcs.upsert(
 <dl>
 <dd>
 
-**agent:** `Pinnacle::Campaigns::Rcs::Types::RcsAgent` — Create an agent for the campaign.
-    
+```ruby
+client.forms.submissions.list(
+  id: "form_Oy2n7iUoi9CJwUU6",
+  page_index: 0,
+  page_size: 20
+)
+```
+</dd>
+</dl>
 </dd>
 </dl>
 
+#### ⚙️ Parameters
+
 <dl>
 <dd>
 
-**brand:** `String` — Unique identifier for the brand.
+<dl>
+<dd>
+
+**id:** `String` 
+
+The unique identifier of the form whose submissions you want to list.
+<br><br> This identifier is a string that always begins with the prefix `form_`, for example: `form_Oy2n7iUoi9CJwUU6`.
     
 </dd>
 </dl>
@@ -4930,7 +5953,7 @@ client.campaigns.rcs.upsert(
 <dl>
 <dd>
 
-**campaign_id:** `String` — Unique identifier for the campaign.
+**page_index:** `Integer` — Zero-based page index.
     
 </dd>
 </dl>
@@ -4938,10 +5961,7 @@ client.campaigns.rcs.upsert(
 <dl>
 <dd>
 
-**expected_agent_responses:** `Internal::Types::Array[String]` 
-
-List of what the agent might say to users. See the [Expected Agent Responses](/guides/campaigns/rcs-compliance#expected-agent-responses) section for requirements. <br><br>
-**Limit:** 1 to 5
+**page_size:** `Integer` — Number of submissions to return in a single page. Max 100.
     
 </dd>
 </dl>
@@ -4949,47 +5969,66 @@ List of what the agent might say to users. See the [Expected Agent Responses](/g
 <dl>
 <dd>
 
-**links:** `Pinnacle::Campaigns::Rcs::Types::RcsLinks` — Legal documentation links.
+**request_options:** `Pinnacle::Forms::Submissions::RequestOptions` 
     
 </dd>
 </dl>
+</dd>
+</dl>
 
-<dl>
-<dd>
 
-**use_case_description:** `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.
-    
 </dd>
 </dl>
+</details>
 
+## Messages Sms
+<details><summary><code>client.messages.sms.<a href="/lib/pinnacle/messages/sms/client.rb">send_</a>(request) -> Pinnacle::Messages::Sms::Types::SmsSendResponse</code></summary>
 <dl>
 <dd>
 
-**messaging_type:** `Pinnacle::Types::RcsMessagingTypeEnum` 
-    
-</dd>
-</dl>
+#### 📝 Description
 
 <dl>
 <dd>
 
-**cta_media:** `String` — URL to the opt-in form or a URL to a screenshot of the opt-in CTA.
-    
+<dl>
+<dd>
+
+Send a SMS message immediately or schedule it for future delivery.
 </dd>
 </dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
 
 <dl>
 <dd>
 
-**opt_in_method:** `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.
-    
+<dl>
+<dd>
+
+```ruby
+client.messages.sms.send_(
+  from: "+14155164736",
+  text: "Hey!",
+  to: "+14154746461"
+)
+```
 </dd>
 </dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
 
 <dl>
 <dd>
 
-**keywords:** `Pinnacle::Campaigns::Rcs::Types::RcsCampaignKeywords` 
+<dl>
+<dd>
+
+**from:** `String` — Phone number that sends the message in E.164 format.
     
 </dd>
 </dl>
@@ -4997,7 +6036,7 @@ List of what the agent might say to users. See the [Expected Agent Responses](/g
 <dl>
 <dd>
 
-**traffic:** `Pinnacle::Campaigns::Rcs::Types::RcsCampaignTraffic` 
+**options:** `Pinnacle::Messages::Sms::Types::SendSmsOptions` — Additional settings to customize SMS delivery.
     
 </dd>
 </dl>
@@ -5005,7 +6044,7 @@ List of what the agent might say to users. See the [Expected Agent Responses](/g
 <dl>
 <dd>
 
-**cta_language:** `String` — 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.
+**text:** `String` — Message content.
     
 </dd>
 </dl>
@@ -5013,7 +6052,7 @@ List of what the agent might say to users. See the [Expected Agent Responses](/g
 <dl>
 <dd>
 
-**demo_trigger:** `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.
+**to:** `String` — Recipient's phone number in E.164 format.
     
 </dd>
 </dl>
@@ -5021,7 +6060,7 @@ List of what the agent might say to users. See the [Expected Agent Responses](/g
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Sms::RequestOptions` 
     
 </dd>
 </dl>
@@ -5033,7 +6072,7 @@ List of what the agent might say to users. See the [Expected Agent Responses](/g
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">validate</a>(request) -> Pinnacle::Types::CampaignValidationResult</code></summary>
+<details><summary><code>client.messages.sms.<a href="/lib/pinnacle/messages/sms/client.rb">validate</a>(request) -> Pinnacle::Types::SmsValidationResult</code></summary>
 <dl>
 <dd>
 
@@ -5045,7 +6084,7 @@ List of what the agent might say to users. See the [Expected Agent Responses](/g
 <dl>
 <dd>
 
-Validate your RCS campaign configuration against carrier requirements and compliance rules.
+Validate SMS message content without sending it.
 </dd>
 </dl>
 </dd>
@@ -5060,10 +6099,7 @@ Validate your RCS campaign configuration against carrier requirements and compli
 <dd>
 
 ```ruby
-client.campaigns.rcs.validate(
-  additional_info: "Please validate this DLC campaign for 10DLC compliance",
-  campaign_id: "dlc_1234567890"
-)
+client.messages.sms.validate(text: "Hello from Pinnacle")
 ```
 </dd>
 </dl>
@@ -5078,7 +6114,7 @@ client.campaigns.rcs.validate(
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::ValidateCampaignParams` 
+**request:** `Pinnacle::Types::SmsContent` 
     
 </dd>
 </dl>
@@ -5086,7 +6122,7 @@ client.campaigns.rcs.validate(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Sms::RequestOptions` 
     
 </dd>
 </dl>
@@ -5098,7 +6134,8 @@ client.campaigns.rcs.validate(
 </dl>
 </details>
 
-<details><summary><code>client.campaigns.rcs.<a href="/lib/pinnacle/campaigns/rcs/client.rb">list</a>(request) -> Pinnacle::Types::ListRcsCampaignsResponse</code></summary>
+## Messages Mms
+<details><summary><code>client.messages.mms.<a href="/lib/pinnacle/messages/mms/client.rb">send_</a>(request) -> Pinnacle::Messages::Mms::Types::MmsSendResponse</code></summary>
 <dl>
 <dd>
 
@@ -5110,7 +6147,7 @@ client.campaigns.rcs.validate(
 <dl>
 <dd>
 
-List all RCS campaigns with optional filtering and pagination. Results are sorted by creation date, newest first.
+Send a MMS immediately or schedule it for future delivery.
 </dd>
 </dl>
 </dd>
@@ -5125,7 +6162,16 @@ List all RCS campaigns with optional filtering and pagination. Results are sorte
 <dd>
 
 ```ruby
-client.campaigns.rcs.list
+client.messages.mms.send_(
+  from: "+14155164736",
+  media_urls: ["https://fastly.picsum.photos/id/941/300/300.jpg?hmac=mDxM9PWSqRDjecwSCEpzU4bj35gqnG7yA25OL29uNv0"],
+  options: {
+    multiple_messages: true,
+    validate: true
+  },
+  text: "Check out this image!",
+  to: "+14154746461"
+)
 ```
 </dd>
 </dl>
@@ -5140,7 +6186,7 @@ client.campaigns.rcs.list
 <dl>
 <dd>
 
-**page_index:** `Integer` 
+**from:** `String` — Phone number you want to send the message from in E.164 format.
     
 </dd>
 </dl>
@@ -5148,7 +6194,11 @@ client.campaigns.rcs.list
 <dl>
 <dd>
 
-**page_size:** `Integer` 
+**media_urls:** `Internal::Types::Array[String]` 
+
+Media file URLs to send.<br>
+
+ See [supported media types](https://app.pinnacle.sh/supported-file-types?type=MMS).
     
 </dd>
 </dl>
@@ -5156,7 +6206,7 @@ client.campaigns.rcs.list
 <dl>
 <dd>
 
-**status:** `Pinnacle::Campaigns::Rcs::Types::ListRcsCampaignsRequestStatus` 
+**options:** `Pinnacle::Messages::Mms::Types::SendMmsOptions` — Control how your MMS is processed and delivered.
     
 </dd>
 </dl>
@@ -5164,7 +6214,7 @@ client.campaigns.rcs.list
 <dl>
 <dd>
 
-**brand_id:** `String` 
+**text:** `String` — Message text to accompany the media.
     
 </dd>
 </dl>
@@ -5172,7 +6222,7 @@ client.campaigns.rcs.list
 <dl>
 <dd>
 
-**name:** `String` — Filter by campaign name (partial match, case-insensitive).
+**to:** `String` — Recipient's phone number in E.164 format.
     
 </dd>
 </dl>
@@ -5180,7 +6230,7 @@ client.campaigns.rcs.list
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Campaigns::Rcs::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Mms::RequestOptions` 
     
 </dd>
 </dl>
@@ -5192,8 +6242,7 @@ client.campaigns.rcs.list
 </dl>
 </details>
 
-## Forms Submissions
-<details><summary><code>client.forms.submissions.<a href="/lib/pinnacle/forms/submissions/client.rb">list</a>(id, request) -> Pinnacle::Types::ListFormSubmissionsResponse</code></summary>
+<details><summary><code>client.messages.mms.<a href="/lib/pinnacle/messages/mms/client.rb">validate</a>(request) -> Pinnacle::Types::MmsValidationResult</code></summary>
 <dl>
 <dd>
 
@@ -5205,7 +6254,7 @@ client.campaigns.rcs.list
 <dl>
 <dd>
 
-Paginated list of completed submissions for a form, newest first. Each row includes the submitted `data` keyed by field `key`, the sender/recipient, IP, user-agent, and timestamps.
+Validate MMS message content without sending it.
 </dd>
 </dl>
 </dd>
@@ -5220,10 +6269,9 @@ Paginated list of completed submissions for a form, newest first. Each row inclu
 <dd>
 
 ```ruby
-client.forms.submissions.list(
-  id: "form_Oy2n7iUoi9CJwUU6",
-  page_index: 0,
-  page_size: 20
+client.messages.mms.validate(
+  media_urls: %w[https://upload.wikimedia.org/wikipedia/commons/b/b9/Pizigani_1367_Chart_1MB.jpg https://fastly.picsum.photos/id/528/1000/1000.jpg?hmac=aTG0xNif9KbNryFN0ZNZ_nFK6aEpZxqUGCZF1KjOT8w https://file-examples.com/storage/fefdd7ab126835e7993bb1a/2017/10/file_example_JPG_500kB.jpg],
+  text: "Check out these images!"
 )
 ```
 </dd>
@@ -5239,10 +6287,7 @@ client.forms.submissions.list(
 <dl>
 <dd>
 
-**id:** `String` 
-
-The unique identifier of the form whose submissions you want to list.
-<br><br> This identifier is a string that always begins with the prefix `form_`, for example: `form_Oy2n7iUoi9CJwUU6`.
+**request:** `Pinnacle::Types::MmsContent` 
     
 </dd>
 </dl>
@@ -5250,15 +6295,68 @@ The unique identifier of the form whose submissions you want to list.
 <dl>
 <dd>
 
-**page_index:** `Integer` — Zero-based page index.
+**request_options:** `Pinnacle::Messages::Mms::RequestOptions` 
     
 </dd>
 </dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+## Messages Rcs
+<details><summary><code>client.messages.rcs.<a href="/lib/pinnacle/messages/rcs/client.rb">send_</a>(request) -> Pinnacle::Messages::Rcs::Types::SendRichMessageResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Send a RCS message immediately or schedule it for future delivery. <br>
+
+Requires an active RCS agent and recipient devices that support RCS Business Messaging.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
 
 <dl>
 <dd>
 
-**page_size:** `Integer` — Number of submissions to return in a single page. Max 100.
+<dl>
+<dd>
+
+```ruby
+client.messages.rcs.send_(
+  from: "from",
+  to: "to",
+  text: "text"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `Pinnacle::Types::RichMessage` 
     
 </dd>
 </dl>
@@ -5266,7 +6364,7 @@ The unique identifier of the form whose submissions you want to list.
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Forms::Submissions::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Rcs::RequestOptions` 
     
 </dd>
 </dl>
@@ -5278,8 +6376,7 @@ The unique identifier of the form whose submissions you want to list.
 </dl>
 </details>
 
-## Messages Sms
-<details><summary><code>client.messages.sms.<a href="/lib/pinnacle/messages/sms/client.rb">send_</a>(request) -> Pinnacle::Messages::Sms::Types::SmsSendResponse</code></summary>
+<details><summary><code>client.messages.rcs.<a href="/lib/pinnacle/messages/rcs/client.rb">send_typing</a>(request) -> Pinnacle::Types::SendTypingIndicatorResponse</code></summary>
 <dl>
 <dd>
 
@@ -5291,7 +6388,17 @@ The unique identifier of the form whose submissions you want to list.
 <dl>
 <dd>
 
-Send a SMS message immediately or schedule it for future delivery.
+Send a typing indicator from an RCS agent to a recipient.
+
+This endpoint allows RCS agents to display a typing indicator to recipients. The indicator is a message bubble with animated typing dots like this: <img src="https://server.trypinnacle.app/storage/v1/object/public/pinnacle-public-assets/ios-typing-indicator.png" alt="Typing Indicator" style="display: inline; height: 1.5em; vertical-align: middle; margin: 0 4px;" />
+
+**Use Case:** Typing indicators are especially useful for providing feedback to users while the agent is thinking or generating a response that may take some time, creating a more engaging conversational experience.
+
+**Expiration:** Typing indicators automatically expire after around 20 seconds or when the agent sends a message, whichever comes first.
+
+**Frequency:** You can send typing indicators as many times as needed, though only one will be displayed at a time. Sending multiple typing indicators will extend the duration of the current indicator.
+
+> **Note:** Typing indicators are best-effort hints, not delivery-guaranteed state. The platform is allowed to coalesce or drop them, and the client UI decides when to show/hide.
 </dd>
 </dl>
 </dd>
@@ -5306,9 +6413,8 @@ Send a SMS message immediately or schedule it for future delivery.
 <dd>
 
 ```ruby
-client.messages.sms.send_(
-  from: "+14155164736",
-  text: "Hey!",
+client.messages.rcs.send_typing(
+  agent_id: "agent_pinnacle",
   to: "+14154746461"
 )
 ```
@@ -5325,15 +6431,11 @@ client.messages.sms.send_(
 <dl>
 <dd>
 
-**from:** `String` — Phone number that sends the message in E.164 format.
-    
-</dd>
-</dl>
+**agent_id:** `String` 
 
-<dl>
-<dd>
+The unique identifier of the RCS agent sending the typing indicator. <br>
 
-**options:** `Pinnacle::Messages::Sms::Types::SendSmsOptions` — Additional settings to customize SMS delivery.
+Format: `agent_` followed by alphanumeric characters (e.g., `agent_pinnacle`).
     
 </dd>
 </dl>
@@ -5341,15 +6443,11 @@ client.messages.sms.send_(
 <dl>
 <dd>
 
-**text:** `String` — Message content.
-    
-</dd>
-</dl>
+**to:** `String` 
 
-<dl>
-<dd>
+The recipient's phone number in E.164 format. <br>
 
-**to:** `String` — Recipient's phone number in E.164 format.
+Must include country code with a leading plus sign (e.g., `+14155551234`).
     
 </dd>
 </dl>
@@ -5357,7 +6455,7 @@ client.messages.sms.send_(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Sms::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Rcs::RequestOptions` 
     
 </dd>
 </dl>
@@ -5369,7 +6467,7 @@ client.messages.sms.send_(
 </dl>
 </details>
 
-<details><summary><code>client.messages.sms.<a href="/lib/pinnacle/messages/sms/client.rb">validate</a>(request) -> Pinnacle::Types::SmsValidationResult</code></summary>
+<details><summary><code>client.messages.rcs.<a href="/lib/pinnacle/messages/rcs/client.rb">validate</a>(request) -> Pinnacle::Types::RcsValidationResult</code></summary>
 <dl>
 <dd>
 
@@ -5381,7 +6479,7 @@ client.messages.sms.send_(
 <dl>
 <dd>
 
-Validate SMS message content without sending it.
+Validate RCS message content without sending it.
 </dd>
 </dl>
 </dd>
@@ -5396,7 +6494,7 @@ Validate SMS message content without sending it.
 <dd>
 
 ```ruby
-client.messages.sms.validate(text: "Hello from Pinnacle")
+client.messages.rcs.validate(text: "text")
 ```
 </dd>
 </dl>
@@ -5411,7 +6509,7 @@ client.messages.sms.validate(text: "Hello from Pinnacle")
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::SmsContent` 
+**request:** `Pinnacle::Types::RcsValidateContent` 
     
 </dd>
 </dl>
@@ -5419,7 +6517,7 @@ client.messages.sms.validate(text: "Hello from Pinnacle")
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Sms::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Rcs::RequestOptions` 
     
 </dd>
 </dl>
@@ -5431,8 +6529,8 @@ client.messages.sms.validate(text: "Hello from Pinnacle")
 </dl>
 </details>
 
-## Messages Mms
-<details><summary><code>client.messages.mms.<a href="/lib/pinnacle/messages/mms/client.rb">send_</a>(request) -> Pinnacle::Messages::Mms::Types::MmsSendResponse</code></summary>
+## Messages Blast
+<details><summary><code>client.messages.blast.<a href="/lib/pinnacle/messages/blast/client.rb">sms</a>(request) -> Pinnacle::Messages::Blast::Types::BlastSmsResponse</code></summary>
 <dl>
 <dd>
 
@@ -5444,7 +6542,11 @@ client.messages.sms.validate(text: "Hello from Pinnacle")
 <dl>
 <dd>
 
-Send a MMS immediately or schedule it for future delivery.
+Send an SMS message to all contacts in an audience. <br>
+
+Messages are distributed evenly across the provided sender phone numbers. <br>
+
+Use the optional `schedule` parameter in `options` to schedule the blast for future delivery. When scheduled, the response will contain a `scheduleId` instead of blast details.
 </dd>
 </dl>
 </dd>
@@ -5459,15 +6561,12 @@ Send a MMS immediately or schedule it for future delivery.
 <dd>
 
 ```ruby
-client.messages.mms.send_(
-  from: "+14155164736",
-  media_urls: ["https://fastly.picsum.photos/id/941/300/300.jpg?hmac=mDxM9PWSqRDjecwSCEpzU4bj35gqnG7yA25OL29uNv0"],
-  options: {
-    multiple_messages: true,
-    validate: true
-  },
-  text: "Check out this image!",
-  to: "+14154746461"
+client.messages.blast.sms(
+  audience_id: "aud_abc123",
+  senders: %w[+14155164736 +14155164737],
+  message: {
+    text: "Hello from Pinnacle!"
+  }
 )
 ```
 </dd>
@@ -5483,7 +6582,11 @@ client.messages.mms.send_(
 <dl>
 <dd>
 
-**from:** `String` — Phone number you want to send the message from in E.164 format.
+**audience_id:** `String` 
+
+The audience ID to send the blast to. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`. <br>
+
+You can create an audience via [the dashboard](https://app.pinnacle.sh/dashboard/audiences) or [API](/api-reference/audiences/create).
     
 </dd>
 </dl>
@@ -5491,19 +6594,15 @@ client.messages.mms.send_(
 <dl>
 <dd>
 
-**media_urls:** `Internal::Types::Array[String]` 
+**senders:** `Internal::Types::Array[String]` 
 
-Media file URLs to send.<br>
+Array of phone numbers to send from in E.164 format. <br>
 
- See [supported media types](https://app.pinnacle.sh/supported-file-types?type=MMS).
-    
-</dd>
-</dl>
+Messages will be distributed evenly across these senders.
 
-<dl>
-<dd>
+> **Note:** Sandbox numbers cannot be used for blasts.
 
-**options:** `Pinnacle::Messages::Mms::Types::SendMmsOptions` — Control how your MMS is processed and delivered.
+**Limit:** 1 min
     
 </dd>
 </dl>
@@ -5511,7 +6610,7 @@ Media file URLs to send.<br>
 <dl>
 <dd>
 
-**text:** `String` — Message text to accompany the media.
+**message:** `Pinnacle::Types::SmsContent` 
     
 </dd>
 </dl>
@@ -5519,7 +6618,7 @@ Media file URLs to send.<br>
 <dl>
 <dd>
 
-**to:** `String` — Recipient's phone number in E.164 format.
+**options:** `Pinnacle::Messages::Blast::Types::BlastSmsOptions` — Additional settings to customize SMS blast delivery.
     
 </dd>
 </dl>
@@ -5527,7 +6626,7 @@ Media file URLs to send.<br>
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Mms::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Blast::RequestOptions` 
     
 </dd>
 </dl>
@@ -5539,7 +6638,7 @@ Media file URLs to send.<br>
 </dl>
 </details>
 
-<details><summary><code>client.messages.mms.<a href="/lib/pinnacle/messages/mms/client.rb">validate</a>(request) -> Pinnacle::Types::MmsValidationResult</code></summary>
+<details><summary><code>client.messages.blast.<a href="/lib/pinnacle/messages/blast/client.rb">mms</a>(request) -> Pinnacle::Messages::Blast::Types::BlastMmsResponse</code></summary>
 <dl>
 <dd>
 
@@ -5551,7 +6650,11 @@ Media file URLs to send.<br>
 <dl>
 <dd>
 
-Validate MMS message content without sending it.
+Send an MMS message to all contacts in an audience. <br>
+
+Messages are distributed evenly across the provided sender phone numbers. <br>
+
+Use the optional `schedule` parameter in `options` to schedule the blast for future delivery. When scheduled, the response will contain a `scheduleId` instead of blast details.
 </dd>
 </dl>
 </dd>
@@ -5566,9 +6669,16 @@ Validate MMS message content without sending it.
 <dd>
 
 ```ruby
-client.messages.mms.validate(
-  media_urls: %w[https://upload.wikimedia.org/wikipedia/commons/b/b9/Pizigani_1367_Chart_1MB.jpg https://fastly.picsum.photos/id/528/1000/1000.jpg?hmac=aTG0xNif9KbNryFN0ZNZ_nFK6aEpZxqUGCZF1KjOT8w https://file-examples.com/storage/fefdd7ab126835e7993bb1a/2017/10/file_example_JPG_500kB.jpg],
-  text: "Check out these images!"
+client.messages.blast.mms(
+  audience_id: "aud_abc123",
+  senders: %w[+14155164736 +14155164737],
+  message: {
+    media_urls: ["https://fastly.picsum.photos/id/941/300/300.jpg"],
+    text: "Check out this image!"
+  },
+  options: {
+    validate: true
+  }
 )
 ```
 </dd>
@@ -5584,76 +6694,43 @@ client.messages.mms.validate(
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::MmsContent` 
-    
-</dd>
-</dl>
+**audience_id:** `String` 
 
-<dl>
-<dd>
+The audience ID to send the blast to. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`. <br>
 
-**request_options:** `Pinnacle::Messages::Mms::RequestOptions` 
+You can create an audience via [the dashboard](https://app.pinnacle.sh/dashboard/audiences) or [API](/api-reference/audiences/create).
     
 </dd>
 </dl>
-</dd>
-</dl>
-
-
-</dd>
-</dl>
-</details>
 
-## Messages Rcs
-<details><summary><code>client.messages.rcs.<a href="/lib/pinnacle/messages/rcs/client.rb">send_</a>(request) -> Pinnacle::Messages::Rcs::Types::SendRichMessageResponse</code></summary>
 <dl>
 <dd>
 
-#### 📝 Description
+**senders:** `Internal::Types::Array[String]` 
 
-<dl>
-<dd>
+Array of phone numbers to send from in E.164 format. <br>
 
-<dl>
-<dd>
+Messages will be distributed evenly across these senders.
 
-Send a RCS message immediately or schedule it for future delivery. <br>
+> **Note:** Sandbox numbers cannot be used for blasts.
 
-Requires an active RCS agent and recipient devices that support RCS Business Messaging.
-</dd>
-</dl>
+**Limit:** 1 min
+    
 </dd>
 </dl>
 
-#### 🔌 Usage
-
-<dl>
-<dd>
-
 <dl>
 <dd>
 
-```ruby
-client.messages.rcs.send_(
-  from: "from",
-  to: "to",
-  text: "text"
-)
-```
-</dd>
-</dl>
+**message:** `Pinnacle::Types::MmsContent` 
+    
 </dd>
 </dl>
 
-#### ⚙️ Parameters
-
-<dl>
-<dd>
-
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::RichMessage` 
+**options:** `Pinnacle::Messages::Blast::Types::BlastMmsOptions` — Additional settings to customize MMS blast delivery.
     
 </dd>
 </dl>
@@ -5661,7 +6738,7 @@ client.messages.rcs.send_(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Rcs::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Blast::RequestOptions` 
     
 </dd>
 </dl>
@@ -5673,7 +6750,7 @@ client.messages.rcs.send_(
 </dl>
 </details>
 
-<details><summary><code>client.messages.rcs.<a href="/lib/pinnacle/messages/rcs/client.rb">send_typing</a>(request) -> Pinnacle::Types::SendTypingIndicatorResponse</code></summary>
+<details><summary><code>client.messages.blast.<a href="/lib/pinnacle/messages/blast/client.rb">rcs</a>(request) -> Pinnacle::Messages::Blast::Types::BlastRcsResponse</code></summary>
 <dl>
 <dd>
 
@@ -5685,17 +6762,11 @@ client.messages.rcs.send_(
 <dl>
 <dd>
 
-Send a typing indicator from an RCS agent to a recipient.
-
-This endpoint allows RCS agents to display a typing indicator to recipients. The indicator is a message bubble with animated typing dots like this: <img src="https://server.trypinnacle.app/storage/v1/object/public/pinnacle-public-assets/ios-typing-indicator.png" alt="Typing Indicator" style="display: inline; height: 1.5em; vertical-align: middle; margin: 0 4px;" />
-
-**Use Case:** Typing indicators are especially useful for providing feedback to users while the agent is thinking or generating a response that may take some time, creating a more engaging conversational experience.
-
-**Expiration:** Typing indicators automatically expire after around 20 seconds or when the agent sends a message, whichever comes first.
+Send an RCS message to all contacts in an audience. <br>
 
-**Frequency:** You can send typing indicators as many times as needed, though only one will be displayed at a time. Sending multiple typing indicators will extend the duration of the current indicator.
+Messages are distributed evenly across the provided RCS agents for load balancing. Requires active RCS agents and recipient devices that support RCS Business Messaging. <br>
 
-> **Note:** Typing indicators are best-effort hints, not delivery-guaranteed state. The platform is allowed to coalesce or drop them, and the client UI decides when to show/hide.
+Use the optional `schedule` parameter in `options` to schedule the blast for future delivery. When scheduled, the response will contain a `scheduleId` instead of blast details.
 </dd>
 </dl>
 </dd>
@@ -5710,9 +6781,21 @@ This endpoint allows RCS agents to display a typing indicator to recipients. The
 <dd>
 
 ```ruby
-client.messages.rcs.send_typing(
-  agent_id: "agent_pinnacle",
-  to: "+14154746461"
+client.messages.blast.rcs(
+  audience_id: "aud_abc123",
+  senders: %w[agent_pinnacle agent_pinnacle2],
+  message: {
+    quick_replies: [],
+    text: "Hello from Pinnacle RCS!"
+  },
+  fallback: {
+    from: "+14155164736",
+    text: "Hello from Pinnacle! Reply LEARN to learn more."
+  },
+  options: {
+    transcode: true,
+    validate: true
+  }
 )
 ```
 </dd>
@@ -5728,11 +6811,11 @@ client.messages.rcs.send_typing(
 <dl>
 <dd>
 
-**agent_id:** `String` 
+**audience_id:** `String` 
 
-The unique identifier of the RCS agent sending the typing indicator. <br>
+The audience ID to send the blast to. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`. <br>
 
-Format: `agent_` followed by alphanumeric characters (e.g., `agent_pinnacle`).
+You can create an audience via [the dashboard](https://app.pinnacle.sh/dashboard/audiences) or [API](/api-reference/audiences/create).
     
 </dd>
 </dl>
@@ -5740,11 +6823,13 @@ Format: `agent_` followed by alphanumeric characters (e.g., `agent_pinnacle`).
 <dl>
 <dd>
 
-**to:** `String` 
+**senders:** `Internal::Types::Array[String]` 
 
-The recipient's phone number in E.164 format. <br>
+Array of RCS agent IDs to send from. Each must be prefixed with `agent_`. <br>
 
-Must include country code with a leading plus sign (e.g., `+14155551234`).
+Messages will be evenly distributed across these agents.
+
+**Limit:** 1 min
     
 </dd>
 </dl>
@@ -5752,7 +6837,31 @@ Must include country code with a leading plus sign (e.g., `+14155551234`).
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Rcs::RequestOptions` 
+**message:** `Pinnacle::Types::RcsValidateContent` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**fallback:** `Pinnacle::Types::FallbackMessage` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**options:** `Pinnacle::Messages::Blast::Types::BlastRcsOptions` — Configure how your RCS blast is sent and tracked.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Messages::Blast::RequestOptions` 
     
 </dd>
 </dl>
@@ -5764,7 +6873,8 @@ Must include country code with a leading plus sign (e.g., `+14155551234`).
 </dl>
 </details>
 
-<details><summary><code>client.messages.rcs.<a href="/lib/pinnacle/messages/rcs/client.rb">validate</a>(request) -> Pinnacle::Types::RcsValidationResult</code></summary>
+## Messages Schedule
+<details><summary><code>client.messages.schedule.<a href="/lib/pinnacle/messages/schedule/client.rb">cancel</a>(id) -> Pinnacle::Types::ScheduleCancelResult</code></summary>
 <dl>
 <dd>
 
@@ -5776,7 +6886,9 @@ Must include country code with a leading plus sign (e.g., `+14155551234`).
 <dl>
 <dd>
 
-Validate RCS message content without sending it.
+Cancel a scheduled message or blast. <br>
+
+Works for both individual scheduled messages and scheduled blasts. Use the `scheduleId` returned when the message or blast was scheduled.
 </dd>
 </dl>
 </dd>
@@ -5791,7 +6903,7 @@ Validate RCS message content without sending it.
 <dd>
 
 ```ruby
-client.messages.rcs.validate(text: "text")
+client.messages.schedule.cancel(id: "id")
 ```
 </dd>
 </dl>
@@ -5806,7 +6918,7 @@ client.messages.rcs.validate(text: "text")
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::RcsValidateContent` 
+**id:** `String` — Unique identifier of the scheduled message. This identifier is a string that always begins with the prefix `msg_sched_`, for example: `msg_sched_1234567890`.
     
 </dd>
 </dl>
@@ -5814,7 +6926,7 @@ client.messages.rcs.validate(text: "text")
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Rcs::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Schedule::RequestOptions` 
     
 </dd>
 </dl>
@@ -5826,8 +6938,8 @@ client.messages.rcs.validate(text: "text")
 </dl>
 </details>
 
-## Messages Blast
-<details><summary><code>client.messages.blast.<a href="/lib/pinnacle/messages/blast/client.rb">sms</a>(request) -> Pinnacle::Messages::Blast::Types::BlastSmsResponse</code></summary>
+## Messages Schedules
+<details><summary><code>client.messages.schedules.<a href="/lib/pinnacle/messages/schedules/client.rb">list</a>(request) -> Pinnacle::Types::ListScheduledMessagesResponse</code></summary>
 <dl>
 <dd>
 
@@ -5839,11 +6951,7 @@ client.messages.rcs.validate(text: "text")
 <dl>
 <dd>
 
-Send an SMS message to all contacts in an audience. <br>
-
-Messages are distributed evenly across the provided sender phone numbers. <br>
-
-Use the optional `schedule` parameter in `options` to schedule the blast for future delivery. When scheduled, the response will contain a `scheduleId` instead of blast details.
+List all scheduled messages with optional filtering and pagination. Results are sorted by creation date, newest first.
 </dd>
 </dl>
 </dd>
@@ -5858,13 +6966,7 @@ Use the optional `schedule` parameter in `options` to schedule the blast for fut
 <dd>
 
 ```ruby
-client.messages.blast.sms(
-  audience_id: "aud_abc123",
-  senders: %w[+14155164736 +14155164737],
-  message: {
-    text: "Hello from Pinnacle!"
-  }
-)
+client.messages.schedules.list
 ```
 </dd>
 </dl>
@@ -5879,11 +6981,7 @@ client.messages.blast.sms(
 <dl>
 <dd>
 
-**audience_id:** `String` 
-
-The audience ID to send the blast to. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`. <br>
-
-You can create an audience via [the dashboard](https://app.pinnacle.sh/dashboard/audiences) or [API](/api-reference/audiences/create).
+**page_index:** `Integer` 
     
 </dd>
 </dl>
@@ -5891,15 +6989,15 @@ You can create an audience via [the dashboard](https://app.pinnacle.sh/dashboard
 <dl>
 <dd>
 
-**senders:** `Internal::Types::Array[String]` 
-
-Array of phone numbers to send from in E.164 format. <br>
-
-Messages will be distributed evenly across these senders.
+**page_size:** `Integer` 
+    
+</dd>
+</dl>
 
-> **Note:** Sandbox numbers cannot be used for blasts.
+<dl>
+<dd>
 
-**Limit:** 1 min
+**status:** `Pinnacle::Messages::Schedules::Types::ListScheduledMessagesRequestStatus` 
     
 </dd>
 </dl>
@@ -5907,7 +7005,7 @@ Messages will be distributed evenly across these senders.
 <dl>
 <dd>
 
-**message:** `Pinnacle::Types::SmsContent` 
+**schedule_type:** `Pinnacle::Messages::Schedules::Types::ListScheduledMessagesRequestScheduleType` — Filter by schedule type — "MESSAGE" for individual messages, "BLAST" for bulk sends.
     
 </dd>
 </dl>
@@ -5915,7 +7013,7 @@ Messages will be distributed evenly across these senders.
 <dl>
 <dd>
 
-**options:** `Pinnacle::Messages::Blast::Types::BlastSmsOptions` — Additional settings to customize SMS blast delivery.
+**content:** `String` — Search scheduled message content (partial match, case-insensitive).
     
 </dd>
 </dl>
@@ -5923,7 +7021,7 @@ Messages will be distributed evenly across these senders.
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Blast::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Schedules::RequestOptions` 
     
 </dd>
 </dl>
@@ -5935,7 +7033,8 @@ Messages will be distributed evenly across these senders.
 </dl>
 </details>
 
-<details><summary><code>client.messages.blast.<a href="/lib/pinnacle/messages/blast/client.rb">mms</a>(request) -> Pinnacle::Messages::Blast::Types::BlastMmsResponse</code></summary>
+## Messages Blasts
+<details><summary><code>client.messages.blasts.<a href="/lib/pinnacle/messages/blasts/client.rb">list</a>(request) -> Pinnacle::Types::ListBlastsResponse</code></summary>
 <dl>
 <dd>
 
@@ -5947,11 +7046,7 @@ Messages will be distributed evenly across these senders.
 <dl>
 <dd>
 
-Send an MMS message to all contacts in an audience. <br>
-
-Messages are distributed evenly across the provided sender phone numbers. <br>
-
-Use the optional `schedule` parameter in `options` to schedule the blast for future delivery. When scheduled, the response will contain a `scheduleId` instead of blast details.
+List all blasts with optional filtering and pagination. Results are sorted by creation date, newest first.
 </dd>
 </dl>
 </dd>
@@ -5966,17 +7061,7 @@ Use the optional `schedule` parameter in `options` to schedule the blast for fut
 <dd>
 
 ```ruby
-client.messages.blast.mms(
-  audience_id: "aud_abc123",
-  senders: %w[+14155164736 +14155164737],
-  message: {
-    media_urls: ["https://fastly.picsum.photos/id/941/300/300.jpg"],
-    text: "Check out this image!"
-  },
-  options: {
-    validate: true
-  }
-)
+client.messages.blasts.list
 ```
 </dd>
 </dl>
@@ -5991,11 +7076,7 @@ client.messages.blast.mms(
 <dl>
 <dd>
 
-**audience_id:** `String` 
-
-The audience ID to send the blast to. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`. <br>
-
-You can create an audience via [the dashboard](https://app.pinnacle.sh/dashboard/audiences) or [API](/api-reference/audiences/create).
+**page_index:** `Integer` 
     
 </dd>
 </dl>
@@ -6003,15 +7084,15 @@ You can create an audience via [the dashboard](https://app.pinnacle.sh/dashboard
 <dl>
 <dd>
 
-**senders:** `Internal::Types::Array[String]` 
-
-Array of phone numbers to send from in E.164 format. <br>
-
-Messages will be distributed evenly across these senders.
+**page_size:** `Integer` 
+    
+</dd>
+</dl>
 
-> **Note:** Sandbox numbers cannot be used for blasts.
+<dl>
+<dd>
 
-**Limit:** 1 min
+**audience_id:** `String` — Filter blasts by audience ID.
     
 </dd>
 </dl>
@@ -6019,7 +7100,7 @@ Messages will be distributed evenly across these senders.
 <dl>
 <dd>
 
-**message:** `Pinnacle::Types::MmsContent` 
+**sender:** `String` — Filter blasts that include this sender (phone number or agent ID).
     
 </dd>
 </dl>
@@ -6027,7 +7108,7 @@ Messages will be distributed evenly across these senders.
 <dl>
 <dd>
 
-**options:** `Pinnacle::Messages::Blast::Types::BlastMmsOptions` — Additional settings to customize MMS blast delivery.
+**content:** `String` — Search blast content (partial match, case-insensitive).
     
 </dd>
 </dl>
@@ -6035,7 +7116,7 @@ Messages will be distributed evenly across these senders.
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Blast::RequestOptions` 
+**request_options:** `Pinnacle::Messages::Blasts::RequestOptions` 
     
 </dd>
 </dl>
@@ -6047,7 +7128,8 @@ Messages will be distributed evenly across these senders.
 </dl>
 </details>
 
-<details><summary><code>client.messages.blast.<a href="/lib/pinnacle/messages/blast/client.rb">rcs</a>(request) -> Pinnacle::Messages::Blast::Types::BlastRcsResponse</code></summary>
+## Messages Simulate
+<details><summary><code>client.messages.simulate.<a href="/lib/pinnacle/messages/simulate/client.rb">user</a>(request) -> Pinnacle::Types::SimulateUserResponse</code></summary>
 <dl>
 <dd>
 
@@ -6059,11 +7141,7 @@ Messages will be distributed evenly across these senders.
 <dl>
 <dd>
 
-Send an RCS message to all contacts in an audience. <br>
-
-Messages are distributed evenly across the provided RCS agents for load balancing. Requires active RCS agents and recipient devices that support RCS Business Messaging. <br>
-
-Use the optional `schedule` parameter in `options` to schedule the blast for future delivery. When scheduled, the response will contain a `scheduleId` instead of blast details.
+Simulate inbound messages and button presses from a user.
 </dd>
 </dl>
 </dd>
@@ -6078,20 +7156,11 @@ Use the optional `schedule` parameter in `options` to schedule the blast for fut
 <dd>
 
 ```ruby
-client.messages.blast.rcs(
-  audience_id: "aud_abc123",
-  senders: %w[agent_pinnacle agent_pinnacle2],
+client.messages.simulate.user(
+  from: "+14155551234",
+  to: "+14155555678",
   message: {
-    quick_replies: [],
-    text: "Hello from Pinnacle RCS!"
-  },
-  fallback: {
-    from: "+14155164736",
-    text: "Hello from Pinnacle! Reply LEARN to learn more."
-  },
-  options: {
-    transcode: true,
-    validate: true
+    text: "Hello from the test user!"
   }
 )
 ```
@@ -6108,41 +7177,77 @@ client.messages.blast.rcs(
 <dl>
 <dd>
 
-**audience_id:** `String` 
+**request:** `Pinnacle::Types::SimulateUserParams` 
+    
+</dd>
+</dl>
 
-The audience ID to send the blast to. This identifier is a string that always begins with the prefix `aud_`, for example: `aud_abc123`. <br>
+<dl>
+<dd>
 
-You can create an audience via [the dashboard](https://app.pinnacle.sh/dashboard/audiences) or [API](/api-reference/audiences/create).
+**request_options:** `Pinnacle::Messages::Simulate::RequestOptions` 
     
 </dd>
 </dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
 
+## Network SimSwap
+<details><summary><code>client.network.sim_swap.<a href="/lib/pinnacle/network/sim_swap/client.rb">check</a>(request) -> Pinnacle::Types::SimSwapResponse</code></summary>
 <dl>
 <dd>
 
-**senders:** `Internal::Types::Array[String]` 
+#### 📝 Description
 
-Array of RCS agent IDs to send from. Each must be prefixed with `agent_`. <br>
+<dl>
+<dd>
 
-Messages will be evenly distributed across these agents.
+<dl>
+<dd>
 
-**Limit:** 1 min
-    
+Check whether a phone number's SIM was changed during a recent lookback window. Use this to flag account takeover risk before sign-in, password reset, payment, or other sensitive actions.
+
+<Note>
+  Limited availability. Contact [founders@pinnacle.sh](mailto:founders@pinnacle.sh) to request access.
+</Note>
+</dd>
+</dl>
 </dd>
 </dl>
 
+#### 🔌 Usage
+
 <dl>
 <dd>
 
-**message:** `Pinnacle::Types::RcsValidateContent` 
-    
+<dl>
+<dd>
+
+```ruby
+client.network.sim_swap.check(
+  phone_number: "+14155550123",
+  period_hours: 240
+)
+```
+</dd>
+</dl>
 </dd>
 </dl>
 
+#### ⚙️ Parameters
+
 <dl>
 <dd>
 
-**fallback:** `Pinnacle::Types::FallbackMessage` 
+<dl>
+<dd>
+
+**phone_number:** `String` 
     
 </dd>
 </dl>
@@ -6150,7 +7255,7 @@ Messages will be evenly distributed across these agents.
 <dl>
 <dd>
 
-**options:** `Pinnacle::Messages::Blast::Types::BlastRcsOptions` — Configure how your RCS blast is sent and tracked.
+**period_hours:** `Integer` — Lookback window, in hours, for detecting a recent SIM change. Must be from 1 to 2400. Defaults to 240.
     
 </dd>
 </dl>
@@ -6158,7 +7263,7 @@ Messages will be evenly distributed across these agents.
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Blast::RequestOptions` 
+**request_options:** `Pinnacle::Network::SimSwap::RequestOptions` 
     
 </dd>
 </dl>
@@ -6170,8 +7275,8 @@ Messages will be evenly distributed across these agents.
 </dl>
 </details>
 
-## Messages Schedule
-<details><summary><code>client.messages.schedule.<a href="/lib/pinnacle/messages/schedule/client.rb">cancel</a>(id) -> Pinnacle::Types::ScheduleCancelResult</code></summary>
+## Network SubscriberMatch
+<details><summary><code>client.network.subscriber_match.<a href="/lib/pinnacle/network/subscriber_match/client.rb">check</a>(request) -> Pinnacle::Types::SubscriberMatchResponse</code></summary>
 <dl>
 <dd>
 
@@ -6183,9 +7288,11 @@ Messages will be evenly distributed across these agents.
 <dl>
 <dd>
 
-Cancel a scheduled message or blast. <br>
+Compare user-provided identity details against the carrier's subscriber record. Results return match strength per attribute, so you can use partial signals without receiving carrier PII.
 
-Works for both individual scheduled messages and scheduled blasts. Use the `scheduleId` returned when the message or blast was scheduled.
+<Note>
+  Limited availability. Contact [founders@pinnacle.sh](mailto:founders@pinnacle.sh) to request access.
+</Note>
 </dd>
 </dl>
 </dd>
@@ -6200,7 +7307,20 @@ Works for both individual scheduled messages and scheduled blasts. Use the `sche
 <dd>
 
 ```ruby
-client.messages.schedule.cancel(id: "id")
+client.network.subscriber_match.check(
+  phone_number: "+14155550123",
+  attributes: {
+    given_name: "Jane",
+    family_name: "Doe",
+    street_name: "Market Street",
+    street_number: "123",
+    postal_code: "94105",
+    locality: "San Francisco",
+    region: "CA",
+    country: "US",
+    birthdate: "1990-01-31"
+  }
+)
 ```
 </dd>
 </dl>
@@ -6215,7 +7335,7 @@ client.messages.schedule.cancel(id: "id")
 <dl>
 <dd>
 
-**id:** `String` — Unique identifier of the scheduled message. This identifier is a string that always begins with the prefix `msg_sched_`, for example: `msg_sched_1234567890`.
+**phone_number:** `String` 
     
 </dd>
 </dl>
@@ -6223,7 +7343,15 @@ client.messages.schedule.cancel(id: "id")
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Schedule::RequestOptions` 
+**attributes:** `Pinnacle::Types::SubscriberMatchAttributes` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Network::SubscriberMatch::RequestOptions` 
     
 </dd>
 </dl>
@@ -6235,8 +7363,8 @@ client.messages.schedule.cancel(id: "id")
 </dl>
 </details>
 
-## Messages Schedules
-<details><summary><code>client.messages.schedules.<a href="/lib/pinnacle/messages/schedules/client.rb">list</a>(request) -> Pinnacle::Types::ListScheduledMessagesResponse</code></summary>
+## Network SilentAuth
+<details><summary><code>client.network.silent_auth.<a href="/lib/pinnacle/network/silent_auth/client.rb">start</a>(request) -> Pinnacle::Types::SilentAuthResponse</code></summary>
 <dl>
 <dd>
 
@@ -6248,7 +7376,13 @@ client.messages.schedule.cancel(id: "id")
 <dl>
 <dd>
 
-List all scheduled messages with optional filtering and pagination. Results are sorted by creation date, newest first.
+Start a Silent Authentication session to verify that the user controls the device attached to a phone number. Omit `format` to receive a `browserUrl` for the hosted browser/WebView flow, or set `format: "json"` to receive a `jsonUrl` for a native mobile app or custom client-side flow. The device check must run from the user's cellular device, not your server.
+
+The returned URL expires 60 seconds after creation. Open or fetch it immediately and use `expiresAt` to detect when a new Silent Auth session is required.
+
+<Note>
+  Limited availability. Contact [founders@pinnacle.sh](mailto:founders@pinnacle.sh) to request access.
+</Note>
 </dd>
 </dl>
 </dd>
@@ -6263,7 +7397,10 @@ List all scheduled messages with optional filtering and pagination. Results are
 <dd>
 
 ```ruby
-client.messages.schedules.list
+client.network.silent_auth.start(
+  phone_number: "+14155550123",
+  client_ref: "user_123"
+)
 ```
 </dd>
 </dl>
@@ -6278,7 +7415,7 @@ client.messages.schedules.list
 <dl>
 <dd>
 
-**page_index:** `Integer` 
+**phone_number:** `String` 
     
 </dd>
 </dl>
@@ -6286,7 +7423,7 @@ client.messages.schedules.list
 <dl>
 <dd>
 
-**page_size:** `Integer` 
+**client_ref:** `String` — Your correlation ID, such as a user ID, session ID, or case ID.
     
 </dd>
 </dl>
@@ -6294,7 +7431,7 @@ client.messages.schedules.list
 <dl>
 <dd>
 
-**status:** `Pinnacle::Messages::Schedules::Types::ListScheduledMessagesRequestStatus` 
+**format:** `String` — Set to `json` when you want to fetch `jsonUrl` directly from your app and receive a JSON response. Omit this field for the hosted browser/WebView flow.
     
 </dd>
 </dl>
@@ -6302,15 +7439,70 @@ client.messages.schedules.list
 <dl>
 <dd>
 
-**schedule_type:** `Pinnacle::Messages::Schedules::Types::ListScheduledMessagesRequestScheduleType` — Filter by schedule type — "MESSAGE" for individual messages, "BLAST" for bulk sends.
+**request_options:** `Pinnacle::Network::SilentAuth::RequestOptions` 
     
 </dd>
 </dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
 
+<details><summary><code>client.network.silent_auth.<a href="/lib/pinnacle/network/silent_auth/client.rb">check</a>(request_id, request) -> Pinnacle::Types::SilentAuthCheckResponse</code></summary>
 <dl>
 <dd>
 
-**content:** `String` — Search scheduled message content (partial match, case-insensitive).
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Complete a Silent Authentication request by exchanging the code returned from the JSON flow. Call this from your server after the user's mobile app fetches `jsonUrl`.
+
+This endpoint returns a terminal verification result. To inspect pending lifecycle states such as `started` or `challenge-issued`, use [Get Network Request](/api-reference/network/get-network-request).
+
+<Note>
+  Limited availability. Contact [founders@pinnacle.sh](mailto:founders@pinnacle.sh) to request access.
+</Note>
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.network.silent_auth.check(
+  request_id: "nar_1234567890ABCDEF",
+  code: "abc123"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request_id:** `String` — Silent Authentication request ID returned by `POST /network/silent-auth`.
     
 </dd>
 </dl>
@@ -6318,7 +7510,15 @@ client.messages.schedules.list
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Schedules::RequestOptions` 
+**code:** `String` — Code returned by the JSON Silent Auth device flow.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Pinnacle::Network::SilentAuth::RequestOptions` 
     
 </dd>
 </dl>
@@ -6330,8 +7530,8 @@ client.messages.schedules.list
 </dl>
 </details>
 
-## Messages Blasts
-<details><summary><code>client.messages.blasts.<a href="/lib/pinnacle/messages/blasts/client.rb">list</a>(request) -> Pinnacle::Types::ListBlastsResponse</code></summary>
+## Network Requests
+<details><summary><code>client.network.requests.<a href="/lib/pinnacle/network/requests/client.rb">list</a>(request) -> Pinnacle::Types::ListNetworkRequestsResponse</code></summary>
 <dl>
 <dd>
 
@@ -6343,7 +7543,11 @@ client.messages.schedules.list
 <dl>
 <dd>
 
-List all blasts with optional filtering and pagination. Results are sorted by creation date, newest first.
+List Network API request records for your team, sorted newest first. Use filters to audit recent checks by type, status, or your own `clientRef`.
+
+<Note>
+  Limited availability. Contact [founders@pinnacle.sh](mailto:founders@pinnacle.sh) to request access.
+</Note>
 </dd>
 </dl>
 </dd>
@@ -6358,7 +7562,13 @@ List all blasts with optional filtering and pagination. Results are sorted by cr
 <dd>
 
 ```ruby
-client.messages.blasts.list
+client.network.requests.list(
+  page_index: 0,
+  page_size: 20,
+  type: "silent-auth",
+  status: "completed",
+  client_ref: "user_123"
+)
 ```
 </dd>
 </dl>
@@ -6373,7 +7583,7 @@ client.messages.blasts.list
 <dl>
 <dd>
 
-**page_index:** `Integer` 
+**page_index:** `Integer` — Zero-based page index. Use 0 for the first page.
     
 </dd>
 </dl>
@@ -6381,7 +7591,7 @@ client.messages.blasts.list
 <dl>
 <dd>
 
-**page_size:** `Integer` 
+**page_size:** `Integer` — Number of records to return, from 1 to 100.
     
 </dd>
 </dl>
@@ -6389,7 +7599,7 @@ client.messages.blasts.list
 <dl>
 <dd>
 
-**audience_id:** `String` — Filter blasts by audience ID.
+**type:** `Pinnacle::Types::NetworkRequestType` 
     
 </dd>
 </dl>
@@ -6397,7 +7607,7 @@ client.messages.blasts.list
 <dl>
 <dd>
 
-**sender:** `String` — Filter blasts that include this sender (phone number or agent ID).
+**status:** `Pinnacle::Types::NetworkRequestStatus` 
     
 </dd>
 </dl>
@@ -6405,7 +7615,7 @@ client.messages.blasts.list
 <dl>
 <dd>
 
-**content:** `String` — Search blast content (partial match, case-insensitive).
+**client_ref:** `String` — Filter by your correlation ID. Must be 1 to 40 characters when provided.
     
 </dd>
 </dl>
@@ -6413,7 +7623,7 @@ client.messages.blasts.list
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Blasts::RequestOptions` 
+**request_options:** `Pinnacle::Network::Requests::RequestOptions` 
     
 </dd>
 </dl>
@@ -6425,8 +7635,7 @@ client.messages.blasts.list
 </dl>
 </details>
 
-## Messages Simulate
-<details><summary><code>client.messages.simulate.<a href="/lib/pinnacle/messages/simulate/client.rb">user</a>(request) -> Pinnacle::Types::SimulateUserResponse</code></summary>
+<details><summary><code>client.network.requests.<a href="/lib/pinnacle/network/requests/client.rb">get</a>(request_id) -> Pinnacle::Types::NetworkRequestSummary</code></summary>
 <dl>
 <dd>
 
@@ -6438,7 +7647,11 @@ client.messages.blasts.list
 <dl>
 <dd>
 
-Simulate inbound messages and button presses from a user.
+Retrieve one Network API request by ID. The response includes lifecycle timestamps, request status, your `clientRef`, and result fields from the original check.
+
+<Note>
+  Limited availability. Contact [founders@pinnacle.sh](mailto:founders@pinnacle.sh) to request access.
+</Note>
 </dd>
 </dl>
 </dd>
@@ -6453,13 +7666,7 @@ Simulate inbound messages and button presses from a user.
 <dd>
 
 ```ruby
-client.messages.simulate.user(
-  from: "+14155551234",
-  to: "+14155555678",
-  message: {
-    text: "Hello from the test user!"
-  }
-)
+client.network.requests.get(request_id: "nar_1234567890ABCDEF")
 ```
 </dd>
 </dl>
@@ -6474,7 +7681,7 @@ client.messages.simulate.user(
 <dl>
 <dd>
 
-**request:** `Pinnacle::Types::SimulateUserParams` 
+**request_id:** `String` — Network API request ID returned by a Network API endpoint.
     
 </dd>
 </dl>
@@ -6482,7 +7689,7 @@ client.messages.simulate.user(
 <dl>
 <dd>
 
-**request_options:** `Pinnacle::Messages::Simulate::RequestOptions` 
+**request_options:** `Pinnacle::Network::Requests::RequestOptions` 
     
 </dd>
 </dl>