@linqapp/sdk 0.37.1 → 0.38.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (55) hide show
  1. package/CHANGELOG.md +14 -0
  2. package/client.d.mts +27 -0
  3. package/client.d.mts.map +1 -1
  4. package/client.d.ts +27 -0
  5. package/client.d.ts.map +1 -1
  6. package/client.js +27 -0
  7. package/client.js.map +1 -1
  8. package/client.mjs +27 -0
  9. package/client.mjs.map +1 -1
  10. package/package.json +1 -1
  11. package/resources/available-number.d.mts +9 -0
  12. package/resources/available-number.d.mts.map +1 -1
  13. package/resources/available-number.d.ts +9 -0
  14. package/resources/available-number.d.ts.map +1 -1
  15. package/resources/available-number.js +9 -0
  16. package/resources/available-number.js.map +1 -1
  17. package/resources/available-number.mjs +9 -0
  18. package/resources/available-number.mjs.map +1 -1
  19. package/resources/chats/chats.d.mts +26 -12
  20. package/resources/chats/chats.d.mts.map +1 -1
  21. package/resources/chats/chats.d.ts +26 -12
  22. package/resources/chats/chats.d.ts.map +1 -1
  23. package/resources/chats/chats.js.map +1 -1
  24. package/resources/chats/chats.mjs.map +1 -1
  25. package/resources/phone-numbers.d.mts +9 -0
  26. package/resources/phone-numbers.d.mts.map +1 -1
  27. package/resources/phone-numbers.d.ts +9 -0
  28. package/resources/phone-numbers.d.ts.map +1 -1
  29. package/resources/phone-numbers.js +9 -0
  30. package/resources/phone-numbers.js.map +1 -1
  31. package/resources/phone-numbers.mjs +9 -0
  32. package/resources/phone-numbers.mjs.map +1 -1
  33. package/resources/phonenumbers.d.mts +9 -0
  34. package/resources/phonenumbers.d.mts.map +1 -1
  35. package/resources/phonenumbers.d.ts +9 -0
  36. package/resources/phonenumbers.d.ts.map +1 -1
  37. package/resources/phonenumbers.js +9 -0
  38. package/resources/phonenumbers.js.map +1 -1
  39. package/resources/phonenumbers.mjs +9 -0
  40. package/resources/phonenumbers.mjs.map +1 -1
  41. package/resources/webhooks.d.mts +39 -18
  42. package/resources/webhooks.d.mts.map +1 -1
  43. package/resources/webhooks.d.ts +39 -18
  44. package/resources/webhooks.d.ts.map +1 -1
  45. package/src/client.ts +27 -0
  46. package/src/resources/available-number.ts +9 -0
  47. package/src/resources/chats/chats.ts +26 -12
  48. package/src/resources/phone-numbers.ts +9 -0
  49. package/src/resources/phonenumbers.ts +9 -0
  50. package/src/resources/webhooks.ts +39 -18
  51. package/src/version.ts +1 -1
  52. package/version.d.mts +1 -1
  53. package/version.d.ts +1 -1
  54. package/version.js +1 -1
  55. package/version.mjs +1 -1
@@ -140,9 +140,10 @@ export namespace MessageEventV2 {
140
140
  * `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line
141
141
  * flagging.
142
142
  *
143
- * Switch on `status` to gate sends or surface line health in your UI — the enum is
144
- * the long-term contract. Each status carries a `doc_url` that deep-links to the
145
- * relevant section of the Chat Health guide.
143
+ * Switch on `status` to surface chat and line health in your UI — the enum is the
144
+ * long-term contract. Each status carries a `doc_url` that deep-links to the
145
+ * relevant section of the Chat Health guide. To gate a send, act on the response
146
+ * rather than the status: a `403` is the authoritative answer.
146
147
  *
147
148
  * See the [Chat Health guide](/guides/chats/chat-health) for what each status
148
149
  * means and how to react.
@@ -167,9 +168,10 @@ export namespace MessageEventV2 {
167
168
  * `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line
168
169
  * flagging.
169
170
  *
170
- * Switch on `status` to gate sends or surface line health in your UI — the enum is
171
- * the long-term contract. Each status carries a `doc_url` that deep-links to the
172
- * relevant section of the Chat Health guide.
171
+ * Switch on `status` to surface chat and line health in your UI — the enum is the
172
+ * long-term contract. Each status carries a `doc_url` that deep-links to the
173
+ * relevant section of the Chat Health guide. To gate a send, act on the response
174
+ * rather than the status: a `403` is the authoritative answer.
173
175
  *
174
176
  * See the [Chat Health guide](/guides/chats/chat-health) for what each status
175
177
  * means and how to react.
@@ -194,6 +196,11 @@ export namespace MessageEventV2 {
194
196
  * is not itself an opt-out keyword opts them back in immediately — a reply in any
195
197
  * conversation with you counts, the same way the block does.
196
198
  *
199
+ * `OPTED_OUT` marks only the conversation the keyword arrived in. The block below
200
+ * is wider than the mark, so a conversation still reading `HEALTHY` can be blocked
201
+ * as well — gate on the `403`, not on the status. Group threads are never marked
202
+ * and are never blocked.
203
+ *
197
204
  * Linq enforces this: while a recipient is opted out, every send to them is
198
205
  * rejected with `403` (error code `2024`) before the message is queued, across
199
206
  * every chat and every line on your account. Nothing is delivered, including a
@@ -1176,9 +1183,10 @@ export namespace MessageEditedWebhookEvent {
1176
1183
  * `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line
1177
1184
  * flagging.
1178
1185
  *
1179
- * Switch on `status` to gate sends or surface line health in your UI — the enum is
1180
- * the long-term contract. Each status carries a `doc_url` that deep-links to the
1181
- * relevant section of the Chat Health guide.
1186
+ * Switch on `status` to surface chat and line health in your UI — the enum is the
1187
+ * long-term contract. Each status carries a `doc_url` that deep-links to the
1188
+ * relevant section of the Chat Health guide. To gate a send, act on the response
1189
+ * rather than the status: a `403` is the authoritative answer.
1182
1190
  *
1183
1191
  * See the [Chat Health guide](/guides/chats/chat-health) for what each status
1184
1192
  * means and how to react.
@@ -1203,9 +1211,10 @@ export namespace MessageEditedWebhookEvent {
1203
1211
  * `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line
1204
1212
  * flagging.
1205
1213
  *
1206
- * Switch on `status` to gate sends or surface line health in your UI — the enum is
1207
- * the long-term contract. Each status carries a `doc_url` that deep-links to the
1208
- * relevant section of the Chat Health guide.
1214
+ * Switch on `status` to surface chat and line health in your UI — the enum is the
1215
+ * long-term contract. Each status carries a `doc_url` that deep-links to the
1216
+ * relevant section of the Chat Health guide. To gate a send, act on the response
1217
+ * rather than the status: a `403` is the authoritative answer.
1209
1218
  *
1210
1219
  * See the [Chat Health guide](/guides/chats/chat-health) for what each status
1211
1220
  * means and how to react.
@@ -1230,6 +1239,11 @@ export namespace MessageEditedWebhookEvent {
1230
1239
  * is not itself an opt-out keyword opts them back in immediately — a reply in any
1231
1240
  * conversation with you counts, the same way the block does.
1232
1241
  *
1242
+ * `OPTED_OUT` marks only the conversation the keyword arrived in. The block below
1243
+ * is wider than the mark, so a conversation still reading `HEALTHY` can be blocked
1244
+ * as well — gate on the `403`, not on the status. Group threads are never marked
1245
+ * and are never blocked.
1246
+ *
1233
1247
  * Linq enforces this: while a recipient is opted out, every send to them is
1234
1248
  * rejected with `403` (error code `2024`) before the message is queued, across
1235
1249
  * every chat and every line on your account. Nothing is delivered, including a
@@ -1608,9 +1622,10 @@ export namespace ChatCreatedWebhookEvent {
1608
1622
  * `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line
1609
1623
  * flagging.
1610
1624
  *
1611
- * Switch on `status` to gate sends or surface line health in your UI — the enum is
1612
- * the long-term contract. Each status carries a `doc_url` that deep-links to the
1613
- * relevant section of the Chat Health guide.
1625
+ * Switch on `status` to surface chat and line health in your UI — the enum is the
1626
+ * long-term contract. Each status carries a `doc_url` that deep-links to the
1627
+ * relevant section of the Chat Health guide. To gate a send, act on the response
1628
+ * rather than the status: a `403` is the authoritative answer.
1614
1629
  *
1615
1630
  * See the [Chat Health guide](/guides/chats/chat-health) for what each status
1616
1631
  * means and how to react.
@@ -1640,9 +1655,10 @@ export namespace ChatCreatedWebhookEvent {
1640
1655
  * `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line
1641
1656
  * flagging.
1642
1657
  *
1643
- * Switch on `status` to gate sends or surface line health in your UI — the enum is
1644
- * the long-term contract. Each status carries a `doc_url` that deep-links to the
1645
- * relevant section of the Chat Health guide.
1658
+ * Switch on `status` to surface chat and line health in your UI — the enum is the
1659
+ * long-term contract. Each status carries a `doc_url` that deep-links to the
1660
+ * relevant section of the Chat Health guide. To gate a send, act on the response
1661
+ * rather than the status: a `403` is the authoritative answer.
1646
1662
  *
1647
1663
  * See the [Chat Health guide](/guides/chats/chat-health) for what each status
1648
1664
  * means and how to react.
@@ -1667,6 +1683,11 @@ export namespace ChatCreatedWebhookEvent {
1667
1683
  * is not itself an opt-out keyword opts them back in immediately — a reply in any
1668
1684
  * conversation with you counts, the same way the block does.
1669
1685
  *
1686
+ * `OPTED_OUT` marks only the conversation the keyword arrived in. The block below
1687
+ * is wider than the mark, so a conversation still reading `HEALTHY` can be blocked
1688
+ * as well — gate on the `403`, not on the status. Group threads are never marked
1689
+ * and are never blocked.
1690
+ *
1670
1691
  * Linq enforces this: while a recipient is opted out, every send to them is
1671
1692
  * rejected with `403` (error code `2024`) before the message is queued, across
1672
1693
  * every chat and every line on your account. Nothing is delivered, including a
package/src/version.ts CHANGED
@@ -1 +1 @@
1
- export const VERSION = '0.37.1'; // x-release-please-version
1
+ export const VERSION = '0.38.1'; // x-release-please-version
package/version.d.mts CHANGED
@@ -1,2 +1,2 @@
1
- export declare const VERSION = "0.37.1";
1
+ export declare const VERSION = "0.38.1";
2
2
  //# sourceMappingURL=version.d.mts.map
package/version.d.ts CHANGED
@@ -1,2 +1,2 @@
1
- export declare const VERSION = "0.37.1";
1
+ export declare const VERSION = "0.38.1";
2
2
  //# sourceMappingURL=version.d.ts.map
package/version.js CHANGED
@@ -1,5 +1,5 @@
1
1
  "use strict";
2
2
  Object.defineProperty(exports, "__esModule", { value: true });
3
3
  exports.VERSION = void 0;
4
- exports.VERSION = '0.37.1'; // x-release-please-version
4
+ exports.VERSION = '0.38.1'; // x-release-please-version
5
5
  //# sourceMappingURL=version.js.map
package/version.mjs CHANGED
@@ -1,2 +1,2 @@
1
- export const VERSION = '0.37.1'; // x-release-please-version
1
+ export const VERSION = '0.38.1'; // x-release-please-version
2
2
  //# sourceMappingURL=version.mjs.map