rcs-js 2.0.1-rc.1 → 2.0.2

package/dist/cjs/api/resources/rcs/client/Client.d.ts

@@ -55,23 +55,27 @@ export declare class Rcs {
      *
      * ## Overview
      * During development and testing, RCS agents can only send messages to whitelisted phone numbers.
-     * Use this endpoint to add test devices to your agent's whitelist before sending test messages.
+     * Use this endpoint to whitelist specific phone numbers to send and receive messages from the test agent.
      *
      * ## Verification Process
      * After whitelisting a number, you'll need to complete verification:
      *
-     * 1. Check the test device for an "RBM Tester Management" request
-     * 2. Accept the request on the device
-     * 3. Enter the 4-digit verification code in the Pinnacle dashboard at:
+     * 1. Check the test device for message from "RBM Tester Management"
+     * 2. Click the "Make me a tester" button
+     * 3. Enter the separate 4-digit verification SMS code in the Pinnacle dashboard at:
      *    ```
      *    https://app.pinnacle.sh/dashboard/brands/{brandId}?campaignId={campaignId}&campaignType=RCS
      *    ```
      *
+     *  > **⚠️ Important: Re-whitelisting Numbers**
+     * >
+     * > If you whitelist a number that's already whitelisted, you'll receive a new message from "RBM Tester Management". **You must click the "Make me a tester" button again to continue sending and receiving messages.**
+     *
      * > **Important Notes**
      * >
-     * > - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number
-     * > - **AT&T limitation:** Whitelisting may currently fail for AT&T numbers
-     * > - **Verification required:** The whitelist request isn't complete until you verify the device.
+     * > - **Verification required:** Messages cannot be sent nor received until you have clicked the "Make me a tester" button on the test device.
+     * > - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number.
+     * > - **Network limitations:** Whitelisting may be temporarily unavailable for some carriers but are usually restored shortly.
      *
      * @param {Pinnacle.RcsWhitelistRequest} request
      * @param {Rcs.RequestOptions} requestOptions - Request-specific configuration.

package/dist/cjs/api/resources/rcs/client/Client.js

@@ -136,23 +136,27 @@ class Rcs {
      *
      * ## Overview
      * During development and testing, RCS agents can only send messages to whitelisted phone numbers.
-     * Use this endpoint to add test devices to your agent's whitelist before sending test messages.
+     * Use this endpoint to whitelist specific phone numbers to send and receive messages from the test agent.
      *
      * ## Verification Process
      * After whitelisting a number, you'll need to complete verification:
      *
-     * 1. Check the test device for an "RBM Tester Management" request
-     * 2. Accept the request on the device
-     * 3. Enter the 4-digit verification code in the Pinnacle dashboard at:
+     * 1. Check the test device for message from "RBM Tester Management"
+     * 2. Click the "Make me a tester" button
+     * 3. Enter the separate 4-digit verification SMS code in the Pinnacle dashboard at:
      *    ```
      *    https://app.pinnacle.sh/dashboard/brands/{brandId}?campaignId={campaignId}&campaignType=RCS
      *    ```
      *
+     *  > **⚠️ Important: Re-whitelisting Numbers**
+     * >
+     * > If you whitelist a number that's already whitelisted, you'll receive a new message from "RBM Tester Management". **You must click the "Make me a tester" button again to continue sending and receiving messages.**
+     *
      * > **Important Notes**
      * >
-     * > - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number
-     * > - **AT&T limitation:** Whitelisting may currently fail for AT&T numbers
-     * > - **Verification required:** The whitelist request isn't complete until you verify the device.
+     * > - **Verification required:** Messages cannot be sent nor received until you have clicked the "Make me a tester" button on the test device.
+     * > - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number.
+     * > - **Network limitations:** Whitelisting may be temporarily unavailable for some carriers but are usually restored shortly.
      *
      * @param {Pinnacle.RcsWhitelistRequest} request
      * @param {Rcs.RequestOptions} requestOptions - Request-specific configuration.

package/dist/cjs/api/resources/tools/resources/file/client/Client.d.ts

@@ -45,6 +45,7 @@ export declare class File_ {
      *         size: 1024,
      *         name: "test.jpg",
      *         options: {
+     *             deleteAt: "2025-12-31T23:59:59Z",
      *             download: {
      *                 expiresAt: "2025-06-30T12:00:00.000Z"
      *             }

package/dist/cjs/api/resources/tools/resources/file/client/Client.js

@@ -71,6 +71,7 @@ class File_ {
      *         size: 1024,
      *         name: "test.jpg",
      *         options: {
+     *             deleteAt: "2025-12-31T23:59:59Z",
      *             download: {
      *                 expiresAt: "2025-06-30T12:00:00.000Z"
      *             }

package/dist/cjs/api/resources/tools/resources/file/client/requests/UploadFileParams.d.ts

@@ -8,6 +8,7 @@
  *         size: 1024,
  *         name: "test.jpg",
  *         options: {
+ *             deleteAt: "2025-12-31T23:59:59Z",
  *             download: {
  *                 expiresAt: "2025-06-30T12:00:00.000Z"
  *             }
@@ -37,6 +38,12 @@ export declare namespace UploadFileParams {
      * Additional configurations for your file.
      */
     interface Options {
+        /**
+         * Set a deletion date for your file in ISO 8601 format. After this date, the file will be automatically deleted from our storage.<br>
+         *
+         * If this field is not provided, the file will not be deleted. You can still schedule deletion or delete the file manually in the Storage page in the dashboard.
+         */
+        deleteAt?: string;
         /** Configure download settings for your uploaded file. */
         download?: Options.Download;
     }

package/dist/cjs/api/types/ButtonClickedData.d.ts

@@ -8,7 +8,7 @@ import * as Pinnacle from "../index.js";
 export interface ButtonClickedData {
     /** Information about the button that was clicked. */
     button: ButtonClickedData.Button;
-    /** ID of the message this button was attached to, or null if not available. To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint. */
+    /** ID of the message this button was sent in, or null if not available. To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint. */
     messageId: string | null;
 }
 export declare namespace ButtonClickedData {

package/dist/cjs/api/types/MessageEvent.d.ts

@@ -22,8 +22,7 @@ export interface MessageEvent {
      * Null if not yet delivered or for inbound messages.
      */
     deliveredAt?: string | null;
-    /** Message details including ID and content. */
-    message: MessageEvent.Message;
+    message: Pinnacle.MessageEventContent;
 }
 export declare namespace MessageEvent {
     /**
@@ -48,15 +47,4 @@ export declare namespace MessageEvent {
         readonly Inbound: "INBOUND";
         readonly Outbound: "OUTBOUND";
     };
-    /**
-     * Message details including ID and content.
-     */
-    interface Message {
-        /**
-         * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
-         * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
-         */
-        id: string;
-        content: Pinnacle.MessageContent;
-    }
 }

package/dist/cjs/api/types/MessageEventContent.d.ts

@@ -0,0 +1,29 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.js";
+/**
+ * Content of an incoming or outgoing message. Discriminated by the `type` field.
+ */
+export type MessageEventContent = 
+/**
+ * SMS message containing plain text only. Has type `SMS`. */
+Pinnacle.MessageEventSmsContent
+/**
+ * MMS message with text and/or media files from a phone number. Has type `MMS`. */
+ | Pinnacle.MessageEventMmsContent
+/**
+ * RCS message containing longer text content with optional quick reply buttons. Has type `RCS_TEXT`. */
+ | Pinnacle.MessageEventRcsTextContent
+/**
+ * RCS message containing media file with optional quick reply buttons. Has type `RCS_MEDIA`. */
+ | Pinnacle.MessageEventRcsMediaContent
+/**
+ * RCS message containing cards with titles, subtitles, and buttons. Has type `RCS_CARDS`. */
+ | Pinnacle.MessageEventRcsCardsContent
+/**
+ * RCS button click data. Sent when user clicks any button. Has type `RCS_BUTTON_DATA`. */
+ | Pinnacle.MessageEventRcsButtonData
+/**
+ * RCS location sharing data. Sent when user shares their location via a `requestUserLocation` button. Has type `RCS_LOCATION_DATA`. */
+ | Pinnacle.MessageEventRcsLocationData;

package/dist/cjs/api/types/MessageEventContent.js

@@ -0,0 +1,5 @@
+"use strict";
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/cjs/api/types/MessageEventMmsContent.d.ts

@@ -0,0 +1,23 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+/**
+ * MMS message with text and/or media files from a phone number.
+ */
+export interface MessageEventMmsContent {
+    /** Message type identifier. */
+    type: "MMS";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    /**
+     * URLs of media files in this message. <br>
+     *
+     * See [supported media types](https://app.pinnacle.sh/supported-file-types?type=MMS).
+     */
+    mediaUrls: string[];
+    /** Text content that may accompany the media files. */
+    text?: string;
+}

package/dist/cjs/api/types/MessageEventMmsContent.js

@@ -0,0 +1,5 @@
+"use strict";
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/cjs/api/types/MessageEventRcsButtonData.d.ts

@@ -0,0 +1,18 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.js";
+/**
+ * Button click event data received when a user clicks on an RCS button or quick reply (excluding `requestUserLocation` buttons).
+ *
+ * This event contains information about which button was clicked, how many times it's been clicked, and any payload or metadata attached to the button. Use this data to handle user interactions with your RCS messages.
+ */
+export interface MessageEventRcsButtonData extends Pinnacle.ButtonClickedData {
+    /** Message type identifier. */
+    type: "RCS_BUTTON_DATA";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+}

package/dist/cjs/api/types/MessageEventRcsButtonData.js

@@ -0,0 +1,5 @@
+"use strict";
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/cjs/api/types/MessageEventRcsCardsContent.d.ts

@@ -0,0 +1,39 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.js";
+/**
+ * RCS message containing cards, each with its own title, subtitle, and/or buttons. Quick replies can also be added. <br>
+ *
+ * See [supported file types](https://app.pinnacle.sh/supported-file-types?type=RCS-CARD).
+ */
+export interface MessageEventRcsCardsContent {
+    /** Message type identifier. */
+    type: "RCS_CARDS";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    /** Collection of cards attached to the message. */
+    cards: MessageEventRcsCardsContent.Cards.Item[];
+    /** List of interactive quick reply buttons in the message. */
+    quickReplies: Pinnacle.RichButton[];
+}
+export declare namespace MessageEventRcsCardsContent {
+    type Cards = Cards.Item[];
+    namespace Cards {
+        /**
+         * Individual card containing title, optional media, and action buttons.
+         */
+        interface Item {
+            /** Action buttons attached to the card. */
+            buttons: Pinnacle.RichButton[];
+            media?: Pinnacle.RcsMediaDetailsContent;
+            /** Secondary text displayed below the title for additional context. */
+            subtitle?: string;
+            /** Title displayed on the card. */
+            title: string;
+        }
+    }
+}

package/dist/cjs/api/types/MessageEventRcsCardsContent.js

@@ -0,0 +1,5 @@
+"use strict";
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/cjs/api/types/MessageEventRcsLocationData.d.ts

@@ -0,0 +1,18 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.js";
+/**
+ * Location sharing event data received when a user responds to a `requestUserLocation` button and shares their current location.
+ *
+ * This event contains the geographic coordinates (latitude/longitude) and human-readable address of the location the user chose to share. Use this data to process location-based requests or provide location-specific services.
+ */
+export interface MessageEventRcsLocationData extends Pinnacle.LocationShareAction {
+    /** Message type identifier. */
+    type: "RCS_LOCATION_DATA";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+}

package/dist/cjs/api/types/MessageEventRcsLocationData.js

@@ -0,0 +1,5 @@
+"use strict";
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/cjs/api/types/MessageEventRcsMediaContent.d.ts

@@ -0,0 +1,21 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.js";
+/**
+ * RCS message containing a media file with optional quick reply buttons. <br>
+ *
+ * See [supported file types](https://app.pinnacle.sh/supported-file-types?type=RCS-MEDIA).
+ */
+export interface MessageEventRcsMediaContent {
+    /** Message type identifier. */
+    type: "RCS_MEDIA";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    media: Pinnacle.RcsMediaDetailsContent;
+    /** List of interactive quick reply buttons in the message. */
+    quickReplies: Pinnacle.RichButton[];
+}

package/dist/cjs/api/types/MessageEventRcsMediaContent.js

@@ -0,0 +1,5 @@
+"use strict";
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/cjs/api/types/MessageEventRcsTextContent.d.ts

@@ -0,0 +1,20 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.js";
+/**
+ * RCS message containing longer text content with optional quick reply buttons.
+ */
+export interface MessageEventRcsTextContent {
+    /** Message type identifier. */
+    type: "RCS_TEXT";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    /** List of interactive quick reply buttons in the message. */
+    quickReplies: Pinnacle.RichButton[];
+    /** Text content of the RCS message. */
+    text: string;
+}

package/dist/cjs/api/types/MessageEventRcsTextContent.js

@@ -0,0 +1,5 @@
+"use strict";
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/cjs/api/types/MessageEventSmsContent.d.ts

@@ -0,0 +1,17 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+/**
+ * SMS message containing plain text only.
+ */
+export interface MessageEventSmsContent {
+    /** Message type identifier. */
+    type: "SMS";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    /** Message content. */
+    text: string;
+}

package/dist/cjs/api/types/MessageEventSmsContent.js

@@ -0,0 +1,5 @@
+"use strict";
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/cjs/api/types/UploadResults.d.ts

@@ -20,5 +20,11 @@ export declare namespace UploadResults {
          * Null indicates that `download.expiresAt` was not provided and the expiration time is defaulted to one hour after uploading.
          */
         expiresAt: string | null;
+        /**
+         * Deletion date for the file in ISO 8601 format. After this date, the file will be automatically deleted from our storage.<br>
+         *
+         * If this field is not provided, the file will not be deleted. You can still schedule deletion or delete the file manually in the Storage page in the dashboard.
+         */
+        deleteAt?: string | null;
     }
 }

package/dist/cjs/api/types/index.d.ts

@@ -132,5 +132,13 @@ export * from "./VCardData.js";
 export * from "./VcardResource.js";
 export * from "./Webhooks.js";
 export * from "./WebhookResult.js";
+export * from "./MessageEventSmsContent.js";
+export * from "./MessageEventMmsContent.js";
+export * from "./MessageEventRcsTextContent.js";
+export * from "./MessageEventRcsMediaContent.js";
+export * from "./MessageEventRcsCardsContent.js";
+export * from "./MessageEventRcsButtonData.js";
+export * from "./MessageEventRcsLocationData.js";
+export * from "./MessageEventContent.js";
 export * from "./MessageEvent.js";
 export * from "./UserEvent.js";

package/dist/cjs/api/types/index.js

@@ -148,5 +148,13 @@ __exportStar(require("./VCardData.js"), exports);
 __exportStar(require("./VcardResource.js"), exports);
 __exportStar(require("./Webhooks.js"), exports);
 __exportStar(require("./WebhookResult.js"), exports);
+__exportStar(require("./MessageEventSmsContent.js"), exports);
+__exportStar(require("./MessageEventMmsContent.js"), exports);
+__exportStar(require("./MessageEventRcsTextContent.js"), exports);
+__exportStar(require("./MessageEventRcsMediaContent.js"), exports);
+__exportStar(require("./MessageEventRcsCardsContent.js"), exports);
+__exportStar(require("./MessageEventRcsButtonData.js"), exports);
+__exportStar(require("./MessageEventRcsLocationData.js"), exports);
+__exportStar(require("./MessageEventContent.js"), exports);
 __exportStar(require("./MessageEvent.js"), exports);
 __exportStar(require("./UserEvent.js"), exports);

package/dist/esm/api/resources/rcs/client/Client.d.mts

@@ -55,23 +55,27 @@ export declare class Rcs {
      *
      * ## Overview
      * During development and testing, RCS agents can only send messages to whitelisted phone numbers.
-     * Use this endpoint to add test devices to your agent's whitelist before sending test messages.
+     * Use this endpoint to whitelist specific phone numbers to send and receive messages from the test agent.
      *
      * ## Verification Process
      * After whitelisting a number, you'll need to complete verification:
      *
-     * 1. Check the test device for an "RBM Tester Management" request
-     * 2. Accept the request on the device
-     * 3. Enter the 4-digit verification code in the Pinnacle dashboard at:
+     * 1. Check the test device for message from "RBM Tester Management"
+     * 2. Click the "Make me a tester" button
+     * 3. Enter the separate 4-digit verification SMS code in the Pinnacle dashboard at:
      *    ```
      *    https://app.pinnacle.sh/dashboard/brands/{brandId}?campaignId={campaignId}&campaignType=RCS
      *    ```
      *
+     *  > **⚠️ Important: Re-whitelisting Numbers**
+     * >
+     * > If you whitelist a number that's already whitelisted, you'll receive a new message from "RBM Tester Management". **You must click the "Make me a tester" button again to continue sending and receiving messages.**
+     *
      * > **Important Notes**
      * >
-     * > - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number
-     * > - **AT&T limitation:** Whitelisting may currently fail for AT&T numbers
-     * > - **Verification required:** The whitelist request isn't complete until you verify the device.
+     * > - **Verification required:** Messages cannot be sent nor received until you have clicked the "Make me a tester" button on the test device.
+     * > - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number.
+     * > - **Network limitations:** Whitelisting may be temporarily unavailable for some carriers but are usually restored shortly.
      *
      * @param {Pinnacle.RcsWhitelistRequest} request
      * @param {Rcs.RequestOptions} requestOptions - Request-specific configuration.

package/dist/esm/api/resources/rcs/client/Client.mjs

@@ -100,23 +100,27 @@ export class Rcs {
      *
      * ## Overview
      * During development and testing, RCS agents can only send messages to whitelisted phone numbers.
-     * Use this endpoint to add test devices to your agent's whitelist before sending test messages.
+     * Use this endpoint to whitelist specific phone numbers to send and receive messages from the test agent.
      *
      * ## Verification Process
      * After whitelisting a number, you'll need to complete verification:
      *
-     * 1. Check the test device for an "RBM Tester Management" request
-     * 2. Accept the request on the device
-     * 3. Enter the 4-digit verification code in the Pinnacle dashboard at:
+     * 1. Check the test device for message from "RBM Tester Management"
+     * 2. Click the "Make me a tester" button
+     * 3. Enter the separate 4-digit verification SMS code in the Pinnacle dashboard at:
      *    ```
      *    https://app.pinnacle.sh/dashboard/brands/{brandId}?campaignId={campaignId}&campaignType=RCS
      *    ```
      *
+     *  > **⚠️ Important: Re-whitelisting Numbers**
+     * >
+     * > If you whitelist a number that's already whitelisted, you'll receive a new message from "RBM Tester Management". **You must click the "Make me a tester" button again to continue sending and receiving messages.**
+     *
      * > **Important Notes**
      * >
-     * > - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number
-     * > - **AT&T limitation:** Whitelisting may currently fail for AT&T numbers
-     * > - **Verification required:** The whitelist request isn't complete until you verify the device.
+     * > - **Verification required:** Messages cannot be sent nor received until you have clicked the "Make me a tester" button on the test device.
+     * > - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number.
+     * > - **Network limitations:** Whitelisting may be temporarily unavailable for some carriers but are usually restored shortly.
      *
      * @param {Pinnacle.RcsWhitelistRequest} request
      * @param {Rcs.RequestOptions} requestOptions - Request-specific configuration.

package/dist/esm/api/resources/tools/resources/file/client/Client.d.mts

@@ -45,6 +45,7 @@ export declare class File_ {
      *         size: 1024,
      *         name: "test.jpg",
      *         options: {
+     *             deleteAt: "2025-12-31T23:59:59Z",
      *             download: {
      *                 expiresAt: "2025-06-30T12:00:00.000Z"
      *             }

package/dist/esm/api/resources/tools/resources/file/client/Client.mjs

@@ -35,6 +35,7 @@ export class File_ {
      *         size: 1024,
      *         name: "test.jpg",
      *         options: {
+     *             deleteAt: "2025-12-31T23:59:59Z",
      *             download: {
      *                 expiresAt: "2025-06-30T12:00:00.000Z"
      *             }

package/dist/esm/api/resources/tools/resources/file/client/requests/UploadFileParams.d.mts

@@ -8,6 +8,7 @@
  *         size: 1024,
  *         name: "test.jpg",
  *         options: {
+ *             deleteAt: "2025-12-31T23:59:59Z",
  *             download: {
  *                 expiresAt: "2025-06-30T12:00:00.000Z"
  *             }
@@ -37,6 +38,12 @@ export declare namespace UploadFileParams {
      * Additional configurations for your file.
      */
     interface Options {
+        /**
+         * Set a deletion date for your file in ISO 8601 format. After this date, the file will be automatically deleted from our storage.<br>
+         *
+         * If this field is not provided, the file will not be deleted. You can still schedule deletion or delete the file manually in the Storage page in the dashboard.
+         */
+        deleteAt?: string;
         /** Configure download settings for your uploaded file. */
         download?: Options.Download;
     }

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

@@ -8,7 +8,7 @@ import * as Pinnacle from "../index.mjs";
 export interface ButtonClickedData {
     /** Information about the button that was clicked. */
     button: ButtonClickedData.Button;
-    /** ID of the message this button was attached to, or null if not available. To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint. */
+    /** ID of the message this button was sent in, or null if not available. To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint. */
     messageId: string | null;
 }
 export declare namespace ButtonClickedData {

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

@@ -22,8 +22,7 @@ export interface MessageEvent {
      * Null if not yet delivered or for inbound messages.
      */
     deliveredAt?: string | null;
-    /** Message details including ID and content. */
-    message: MessageEvent.Message;
+    message: Pinnacle.MessageEventContent;
 }
 export declare namespace MessageEvent {
     /**
@@ -48,15 +47,4 @@ export declare namespace MessageEvent {
         readonly Inbound: "INBOUND";
         readonly Outbound: "OUTBOUND";
     };
-    /**
-     * Message details including ID and content.
-     */
-    interface Message {
-        /**
-         * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
-         * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
-         */
-        id: string;
-        content: Pinnacle.MessageContent;
-    }
 }

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

@@ -0,0 +1,29 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.mjs";
+/**
+ * Content of an incoming or outgoing message. Discriminated by the `type` field.
+ */
+export type MessageEventContent = 
+/**
+ * SMS message containing plain text only. Has type `SMS`. */
+Pinnacle.MessageEventSmsContent
+/**
+ * MMS message with text and/or media files from a phone number. Has type `MMS`. */
+ | Pinnacle.MessageEventMmsContent
+/**
+ * RCS message containing longer text content with optional quick reply buttons. Has type `RCS_TEXT`. */
+ | Pinnacle.MessageEventRcsTextContent
+/**
+ * RCS message containing media file with optional quick reply buttons. Has type `RCS_MEDIA`. */
+ | Pinnacle.MessageEventRcsMediaContent
+/**
+ * RCS message containing cards with titles, subtitles, and buttons. Has type `RCS_CARDS`. */
+ | Pinnacle.MessageEventRcsCardsContent
+/**
+ * RCS button click data. Sent when user clicks any button. Has type `RCS_BUTTON_DATA`. */
+ | Pinnacle.MessageEventRcsButtonData
+/**
+ * RCS location sharing data. Sent when user shares their location via a `requestUserLocation` button. Has type `RCS_LOCATION_DATA`. */
+ | Pinnacle.MessageEventRcsLocationData;

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

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

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

@@ -0,0 +1,23 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+/**
+ * MMS message with text and/or media files from a phone number.
+ */
+export interface MessageEventMmsContent {
+    /** Message type identifier. */
+    type: "MMS";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    /**
+     * URLs of media files in this message. <br>
+     *
+     * See [supported media types](https://app.pinnacle.sh/supported-file-types?type=MMS).
+     */
+    mediaUrls: string[];
+    /** Text content that may accompany the media files. */
+    text?: string;
+}

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

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

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

@@ -0,0 +1,18 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.mjs";
+/**
+ * Button click event data received when a user clicks on an RCS button or quick reply (excluding `requestUserLocation` buttons).
+ *
+ * This event contains information about which button was clicked, how many times it's been clicked, and any payload or metadata attached to the button. Use this data to handle user interactions with your RCS messages.
+ */
+export interface MessageEventRcsButtonData extends Pinnacle.ButtonClickedData {
+    /** Message type identifier. */
+    type: "RCS_BUTTON_DATA";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+}

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

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

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

@@ -0,0 +1,39 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.mjs";
+/**
+ * RCS message containing cards, each with its own title, subtitle, and/or buttons. Quick replies can also be added. <br>
+ *
+ * See [supported file types](https://app.pinnacle.sh/supported-file-types?type=RCS-CARD).
+ */
+export interface MessageEventRcsCardsContent {
+    /** Message type identifier. */
+    type: "RCS_CARDS";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    /** Collection of cards attached to the message. */
+    cards: MessageEventRcsCardsContent.Cards.Item[];
+    /** List of interactive quick reply buttons in the message. */
+    quickReplies: Pinnacle.RichButton[];
+}
+export declare namespace MessageEventRcsCardsContent {
+    type Cards = Cards.Item[];
+    namespace Cards {
+        /**
+         * Individual card containing title, optional media, and action buttons.
+         */
+        interface Item {
+            /** Action buttons attached to the card. */
+            buttons: Pinnacle.RichButton[];
+            media?: Pinnacle.RcsMediaDetailsContent;
+            /** Secondary text displayed below the title for additional context. */
+            subtitle?: string;
+            /** Title displayed on the card. */
+            title: string;
+        }
+    }
+}

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

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

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

@@ -0,0 +1,18 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.mjs";
+/**
+ * Location sharing event data received when a user responds to a `requestUserLocation` button and shares their current location.
+ *
+ * This event contains the geographic coordinates (latitude/longitude) and human-readable address of the location the user chose to share. Use this data to process location-based requests or provide location-specific services.
+ */
+export interface MessageEventRcsLocationData extends Pinnacle.LocationShareAction {
+    /** Message type identifier. */
+    type: "RCS_LOCATION_DATA";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+}

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

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

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

@@ -0,0 +1,21 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.mjs";
+/**
+ * RCS message containing a media file with optional quick reply buttons. <br>
+ *
+ * See [supported file types](https://app.pinnacle.sh/supported-file-types?type=RCS-MEDIA).
+ */
+export interface MessageEventRcsMediaContent {
+    /** Message type identifier. */
+    type: "RCS_MEDIA";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    media: Pinnacle.RcsMediaDetailsContent;
+    /** List of interactive quick reply buttons in the message. */
+    quickReplies: Pinnacle.RichButton[];
+}

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

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

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

@@ -0,0 +1,20 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+import * as Pinnacle from "../index.mjs";
+/**
+ * RCS message containing longer text content with optional quick reply buttons.
+ */
+export interface MessageEventRcsTextContent {
+    /** Message type identifier. */
+    type: "RCS_TEXT";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    /** List of interactive quick reply buttons in the message. */
+    quickReplies: Pinnacle.RichButton[];
+    /** Text content of the RCS message. */
+    text: string;
+}

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

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

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

@@ -0,0 +1,17 @@
+/**
+ * This file was auto-generated by Fern from our API Definition.
+ */
+/**
+ * SMS message containing plain text only.
+ */
+export interface MessageEventSmsContent {
+    /** Message type identifier. */
+    type: "SMS";
+    /**
+     * Unique identifier of the message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br>
+     * To get the message details, use the [GET /messages/{id}](/api-reference/messages/get) endpoint.
+     */
+    id: string;
+    /** Message content. */
+    text: string;
+}

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

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

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

@@ -20,5 +20,11 @@ export declare namespace UploadResults {
          * Null indicates that `download.expiresAt` was not provided and the expiration time is defaulted to one hour after uploading.
          */
         expiresAt: string | null;
+        /**
+         * Deletion date for the file in ISO 8601 format. After this date, the file will be automatically deleted from our storage.<br>
+         *
+         * If this field is not provided, the file will not be deleted. You can still schedule deletion or delete the file manually in the Storage page in the dashboard.
+         */
+        deleteAt?: string | null;
     }
 }

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

@@ -132,5 +132,13 @@ export * from "./VCardData.mjs";
 export * from "./VcardResource.mjs";
 export * from "./Webhooks.mjs";
 export * from "./WebhookResult.mjs";
+export * from "./MessageEventSmsContent.mjs";
+export * from "./MessageEventMmsContent.mjs";
+export * from "./MessageEventRcsTextContent.mjs";
+export * from "./MessageEventRcsMediaContent.mjs";
+export * from "./MessageEventRcsCardsContent.mjs";
+export * from "./MessageEventRcsButtonData.mjs";
+export * from "./MessageEventRcsLocationData.mjs";
+export * from "./MessageEventContent.mjs";
 export * from "./MessageEvent.mjs";
 export * from "./UserEvent.mjs";

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

@@ -132,5 +132,13 @@ export * from "./VCardData.mjs";
 export * from "./VcardResource.mjs";
 export * from "./Webhooks.mjs";
 export * from "./WebhookResult.mjs";
+export * from "./MessageEventSmsContent.mjs";
+export * from "./MessageEventMmsContent.mjs";
+export * from "./MessageEventRcsTextContent.mjs";
+export * from "./MessageEventRcsMediaContent.mjs";
+export * from "./MessageEventRcsCardsContent.mjs";
+export * from "./MessageEventRcsButtonData.mjs";
+export * from "./MessageEventRcsLocationData.mjs";
+export * from "./MessageEventContent.mjs";
 export * from "./MessageEvent.mjs";
 export * from "./UserEvent.mjs";

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "rcs-js",
-    "version": "2.0.1-rc.1",
+    "version": "2.0.2",
     "private": false,
     "repository": "github:pinnacle-dev/rcs-js",
     "type": "commonjs",
@@ -33,10 +33,10 @@
         "build": "yarn build:cjs && yarn build:esm",
         "build:cjs": "tsc --project ./tsconfig.cjs.json",
         "build:esm": "tsc --project ./tsconfig.esm.json && node scripts/rename-to-esm-files.js dist/esm",
-        "test": "jest --config jest.config.mjs",
+        "test": "jest --selectProjects unit && NODE_OPTIONS=--experimental-vm-modules jest --selectProjects wire",
         "test:unit": "jest --selectProjects unit",
         "test:browser": "jest --selectProjects browser",
-        "test:wire": "jest --selectProjects wire"
+        "test:wire": "NODE_OPTIONS=--experimental-vm-modules jest --selectProjects wire"
     },
     "dependencies": {
         "mime-types": "^3.0.1"

package/reference.md

@@ -1361,24 +1361,28 @@ Whitelist a phone number for testing with your test RCS agent.
 ## Overview
 
 During development and testing, RCS agents can only send messages to whitelisted phone numbers.
-Use this endpoint to add test devices to your agent's whitelist before sending test messages.
+Use this endpoint to whitelist specific phone numbers to send and receive messages from the test agent.
 
 ## Verification Process
 
 After whitelisting a number, you'll need to complete verification:
 
-1. Check the test device for an "RBM Tester Management" request
-2. Accept the request on the device
-3. Enter the 4-digit verification code in the Pinnacle dashboard at:
+1. Check the test device for message from "RBM Tester Management"
+2. Click the "Make me a tester" button
+3. Enter the separate 4-digit verification SMS code in the Pinnacle dashboard at:
     ```
     https://app.pinnacle.sh/dashboard/brands/{brandId}?campaignId={campaignId}&campaignType=RCS
     ```
 
+> **⚠️ Important: Re-whitelisting Numbers**
+>
+> If you whitelist a number that's already whitelisted, you'll receive a new message from "RBM Tester Management". **You must click the "Make me a tester" button again to continue sending and receiving messages.**
+
 > **Important Notes**
 >
-> - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number
-> - **AT&T limitation:** Whitelisting may currently fail for AT&T numbers
-> - **Verification required:** The whitelist request isn't complete until you verify the device.
+> - **Verification required:** Messages cannot be sent nor received until you have clicked the "Make me a tester" button on the test device.
+> - **Testing only:** This is only required for test agents. Production agents can message any RCS-enabled number.
+> - **Network limitations:** Whitelisting may be temporarily unavailable for some carriers but are usually restored shortly.
 
 </dd>
 </dl>
@@ -3948,6 +3952,7 @@ await client.tools.file.upload({
     size: 1024,
     name: "test.jpg",
     options: {
+        deleteAt: "2025-12-31T23:59:59Z",
         download: {
             expiresAt: "2025-06-30T12:00:00.000Z",
         },