@linqapp/sdk 0.33.0 → 0.34.0

package/src/resources/webhook-events.ts

@@ -159,6 +159,15 @@ export type WebhookEventType =
   | 'message.edited'
   | 'reaction.added'
   | 'reaction.removed'
+  | 'poll.received'
+  | 'poll.failed'
+  | 'poll.sent'
+  | 'poll.delivered'
+  | 'poll.read'
+  | 'poll.updated'
+  | 'poll.vote.added'
+  | 'poll.vote.removed'
+  | 'poll.reaction.added'
   | 'participant.added'
   | 'participant.removed'
   | 'chat.created'

package/src/resources/webhooks.ts

@@ -186,15 +186,19 @@ export namespace MessageEventV2 {
        * to react. `doc_url` deep-links to the relevant section.
        *
        * `OPTED_OUT` is terminal — the recipient sent `STOP`, `UNSUBSCRIBE`, `OPTOUT`,
-       * `CANCEL`, `END`, or `QUIT`, and you should send nothing further on this chat.
-       * The keyword must be the whole trimmed message, never part of a longer one:
-       * `STOP` counts, `please stop` does not. Most keywords must match exactly,
-       * including case. `OPT OUT` is the exception — it matches in any casing, with or
-       * without the space or a hyphen, so `opt out`, `Opt-Out` and `optout` all count.
-       * It clears if they later send `START`, `OPTIN`, or `UNSTOP`, or if they keep
-       * replying on the chat — sustained two-way conversation is treated as a sign the
-       * stop keyword was a false positive. Suppressing sends to opted-out recipients is
-       * your responsibility — Linq surfaces the status but does not block the send.
+       * `CANCEL`, `END`, or `QUIT`. The keyword must be the whole trimmed message, never
+       * part of a longer one: `STOP` counts, `please stop` does not. Most keywords must
+       * match exactly, including case. `OPT OUT` is the exception — it matches in any
+       * casing, with or without the space or a hyphen, so `opt out`, `Opt-Out` and
+       * `optout` all count. It clears if they later send `START`, `OPTIN`, or `UNSTOP`,
+       * or if they keep replying on the chat — sustained two-way conversation is treated
+       * as a sign the stop keyword was a false positive.
+       *
+       * Linq enforces this: while a recipient is opted out, every send to them is
+       * rejected with `403` (error code `2024`) before the message is queued, across
+       * every chat and every line on your account. Nothing is delivered, including a
+       * final courtesy message — to send one, set `override_optout: true` on that single
+       * request.
        */
       status: 'HEALTHY' | 'AT_RISK' | 'CRITICAL' | 'OPTED_OUT';
 
@@ -1198,15 +1202,19 @@ export namespace MessageEditedWebhookEvent {
          * to react. `doc_url` deep-links to the relevant section.
          *
          * `OPTED_OUT` is terminal — the recipient sent `STOP`, `UNSUBSCRIBE`, `OPTOUT`,
-         * `CANCEL`, `END`, or `QUIT`, and you should send nothing further on this chat.
-         * The keyword must be the whole trimmed message, never part of a longer one:
-         * `STOP` counts, `please stop` does not. Most keywords must match exactly,
-         * including case. `OPT OUT` is the exception — it matches in any casing, with or
-         * without the space or a hyphen, so `opt out`, `Opt-Out` and `optout` all count.
-         * It clears if they later send `START`, `OPTIN`, or `UNSTOP`, or if they keep
-         * replying on the chat — sustained two-way conversation is treated as a sign the
-         * stop keyword was a false positive. Suppressing sends to opted-out recipients is
-         * your responsibility — Linq surfaces the status but does not block the send.
+         * `CANCEL`, `END`, or `QUIT`. The keyword must be the whole trimmed message, never
+         * part of a longer one: `STOP` counts, `please stop` does not. Most keywords must
+         * match exactly, including case. `OPT OUT` is the exception — it matches in any
+         * casing, with or without the space or a hyphen, so `opt out`, `Opt-Out` and
+         * `optout` all count. It clears if they later send `START`, `OPTIN`, or `UNSTOP`,
+         * or if they keep replying on the chat — sustained two-way conversation is treated
+         * as a sign the stop keyword was a false positive.
+         *
+         * Linq enforces this: while a recipient is opted out, every send to them is
+         * rejected with `403` (error code `2024`) before the message is queued, across
+         * every chat and every line on your account. Nothing is delivered, including a
+         * final courtesy message — to send one, set `override_optout: true` on that single
+         * request.
          */
         status: 'HEALTHY' | 'AT_RISK' | 'CRITICAL' | 'OPTED_OUT';
 
@@ -1631,15 +1639,19 @@ export namespace ChatCreatedWebhookEvent {
        * to react. `doc_url` deep-links to the relevant section.
        *
        * `OPTED_OUT` is terminal — the recipient sent `STOP`, `UNSUBSCRIBE`, `OPTOUT`,
-       * `CANCEL`, `END`, or `QUIT`, and you should send nothing further on this chat.
-       * The keyword must be the whole trimmed message, never part of a longer one:
-       * `STOP` counts, `please stop` does not. Most keywords must match exactly,
-       * including case. `OPT OUT` is the exception — it matches in any casing, with or
-       * without the space or a hyphen, so `opt out`, `Opt-Out` and `optout` all count.
-       * It clears if they later send `START`, `OPTIN`, or `UNSTOP`, or if they keep
-       * replying on the chat — sustained two-way conversation is treated as a sign the
-       * stop keyword was a false positive. Suppressing sends to opted-out recipients is
-       * your responsibility — Linq surfaces the status but does not block the send.
+       * `CANCEL`, `END`, or `QUIT`. The keyword must be the whole trimmed message, never
+       * part of a longer one: `STOP` counts, `please stop` does not. Most keywords must
+       * match exactly, including case. `OPT OUT` is the exception — it matches in any
+       * casing, with or without the space or a hyphen, so `opt out`, `Opt-Out` and
+       * `optout` all count. It clears if they later send `START`, `OPTIN`, or `UNSTOP`,
+       * or if they keep replying on the chat — sustained two-way conversation is treated
+       * as a sign the stop keyword was a false positive.
+       *
+       * Linq enforces this: while a recipient is opted out, every send to them is
+       * rejected with `403` (error code `2024`) before the message is queued, across
+       * every chat and every line on your account. Nothing is delivered, including a
+       * final courtesy message — to send one, set `override_optout: true` on that single
+       * request.
        */
       status: 'HEALTHY' | 'AT_RISK' | 'CRITICAL' | 'OPTED_OUT';
 
@@ -2133,6 +2145,15 @@ export interface PhoneNumberStatusUpdatedWebhookEvent {
     | 'message.edited'
     | 'reaction.added'
     | 'reaction.removed'
+    | 'poll.received'
+    | 'poll.failed'
+    | 'poll.sent'
+    | 'poll.delivered'
+    | 'poll.read'
+    | 'poll.updated'
+    | 'poll.vote.added'
+    | 'poll.vote.removed'
+    | 'poll.reaction.added'
     | 'participant.added'
     | 'participant.removed'
     | 'chat.created'

package/src/version.ts

@@ -1 +1 @@
-export const VERSION = '0.33.0'; // x-release-please-version
+export const VERSION = '0.34.0'; // x-release-please-version

package/version.d.mts

@@ -1,2 +1,2 @@
-export declare const VERSION = "0.33.0";
+export declare const VERSION = "0.34.0";
 //# sourceMappingURL=version.d.mts.map

package/version.d.ts

@@ -1,2 +1,2 @@
-export declare const VERSION = "0.33.0";
+export declare const VERSION = "0.34.0";
 //# sourceMappingURL=version.d.ts.map

package/version.js

@@ -1,5 +1,5 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.VERSION = void 0;
-exports.VERSION = '0.33.0'; // x-release-please-version
+exports.VERSION = '0.34.0'; // x-release-please-version
 //# sourceMappingURL=version.js.map

package/version.mjs

@@ -1,2 +1,2 @@
-export const VERSION = '0.33.0'; // x-release-please-version
+export const VERSION = '0.34.0'; // x-release-please-version
 //# sourceMappingURL=version.mjs.map