@getlatedev/node 0.2.1392 → 0.2.1394
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.
- package/dist/index.d.mts +11 -2
- package/dist/index.d.ts +11 -2
- package/dist/index.js +1 -1
- package/dist/index.mjs +1 -1
- package/package.json +1 -1
- package/src/generated/sdk.gen.ts +1 -1
- package/src/generated/types.gen.ts +11 -2
package/dist/index.d.mts
CHANGED
|
@@ -27811,9 +27811,9 @@ type GetAccountHealthResponse = ({
|
|
|
27811
27811
|
message?: string;
|
|
27812
27812
|
} | null;
|
|
27813
27813
|
/**
|
|
27814
|
-
* From the phone number's Meta health_status.
|
|
27814
|
+
* From the phone number's Meta health_status, overridden to `false` when subscribing the number's WhatsApp Business Account to Zernio's webhooks failed at connect.
|
|
27815
27815
|
*
|
|
27816
|
-
* - `false`: Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered, though the number is CONNECTED and can still send.
|
|
27816
|
+
* - `false`: Meta says Zernio is not subscribed to the message webhook for this number, or the subscribe failed when the number was connected, so inbound messages are not delivered, though the number is CONNECTED and can still send.
|
|
27817
27817
|
* - `false`, fix: re-subscribe (reconnect the number). If it stays `false`, the number is routed to a different WhatsApp Business Account (typically after linking it to a Facebook Page).
|
|
27818
27818
|
* - `true`: Meta reports no such problem.
|
|
27819
27819
|
* - `null`: Meta did not report it (read failed or no health_status); not evidence either way.
|
|
@@ -48254,6 +48254,8 @@ type CreateCommentAutomationData = {
|
|
|
48254
48254
|
template?: (CommentAutomationTemplate);
|
|
48255
48255
|
/**
|
|
48256
48256
|
* Public reply to the comment. Optional on Instagram and Facebook; required on TikTok, Threads, LinkedIn and YouTube, where it is the automation's only action.
|
|
48257
|
+
*
|
|
48258
|
+
* On LinkedIn, mention with `@[Name](urn:li:person:ID)` or `@[Name](urn:li:organization:ID)`, getting the URN from `GET /v1/accounts/{accountId}/linkedin-mentions`. The name must match the person's or Page's LinkedIn name exactly, or the mention renders as plain text. Profile or company URL mentions are not resolved here and are sent as plain text.
|
|
48257
48259
|
*/
|
|
48258
48260
|
commentReply?: string;
|
|
48259
48261
|
/**
|
|
@@ -48262,6 +48264,8 @@ type CreateCommentAutomationData = {
|
|
|
48262
48264
|
dmMessageVariations?: Array<(string)>;
|
|
48263
48265
|
/**
|
|
48264
48266
|
* Optional alternate public replies, rotated at random alongside commentReply (picked independently of the DM). Up to 5.
|
|
48267
|
+
*
|
|
48268
|
+
* LinkedIn mentions follow the commentReply rules.
|
|
48265
48269
|
*/
|
|
48266
48270
|
commentReplyVariations?: Array<(string)>;
|
|
48267
48271
|
/**
|
|
@@ -48513,6 +48517,9 @@ type UpdateCommentAutomationData = {
|
|
|
48513
48517
|
* Product card sent instead of the plain dmMessage bubble. Pass null to clear it and fall back to dmMessage. Mutually exclusive with buttons, including with the buttons already stored on the automation.
|
|
48514
48518
|
*/
|
|
48515
48519
|
template?: (CommentAutomationTemplate | null);
|
|
48520
|
+
/**
|
|
48521
|
+
* On LinkedIn, mention with `@[Name](urn:li:person:ID)` or `@[Name](urn:li:organization:ID)`, getting the URN from `GET /v1/accounts/{accountId}/linkedin-mentions`. The name must match the person's or Page's LinkedIn name exactly, or the mention renders as plain text. Profile or company URL mentions are not resolved here and are sent as plain text.
|
|
48522
|
+
*/
|
|
48516
48523
|
commentReply?: string;
|
|
48517
48524
|
/**
|
|
48518
48525
|
* Alternate DM texts for random rotation (see create). Pass [] to clear.
|
|
@@ -48520,6 +48527,8 @@ type UpdateCommentAutomationData = {
|
|
|
48520
48527
|
dmMessageVariations?: Array<(string)>;
|
|
48521
48528
|
/**
|
|
48522
48529
|
* Alternate public replies for random rotation. Pass [] to clear.
|
|
48530
|
+
*
|
|
48531
|
+
* LinkedIn mentions follow the commentReply rules.
|
|
48523
48532
|
*/
|
|
48524
48533
|
commentReplyVariations?: Array<(string)>;
|
|
48525
48534
|
/**
|
package/dist/index.d.ts
CHANGED
|
@@ -27811,9 +27811,9 @@ type GetAccountHealthResponse = ({
|
|
|
27811
27811
|
message?: string;
|
|
27812
27812
|
} | null;
|
|
27813
27813
|
/**
|
|
27814
|
-
* From the phone number's Meta health_status.
|
|
27814
|
+
* From the phone number's Meta health_status, overridden to `false` when subscribing the number's WhatsApp Business Account to Zernio's webhooks failed at connect.
|
|
27815
27815
|
*
|
|
27816
|
-
* - `false`: Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered, though the number is CONNECTED and can still send.
|
|
27816
|
+
* - `false`: Meta says Zernio is not subscribed to the message webhook for this number, or the subscribe failed when the number was connected, so inbound messages are not delivered, though the number is CONNECTED and can still send.
|
|
27817
27817
|
* - `false`, fix: re-subscribe (reconnect the number). If it stays `false`, the number is routed to a different WhatsApp Business Account (typically after linking it to a Facebook Page).
|
|
27818
27818
|
* - `true`: Meta reports no such problem.
|
|
27819
27819
|
* - `null`: Meta did not report it (read failed or no health_status); not evidence either way.
|
|
@@ -48254,6 +48254,8 @@ type CreateCommentAutomationData = {
|
|
|
48254
48254
|
template?: (CommentAutomationTemplate);
|
|
48255
48255
|
/**
|
|
48256
48256
|
* Public reply to the comment. Optional on Instagram and Facebook; required on TikTok, Threads, LinkedIn and YouTube, where it is the automation's only action.
|
|
48257
|
+
*
|
|
48258
|
+
* On LinkedIn, mention with `@[Name](urn:li:person:ID)` or `@[Name](urn:li:organization:ID)`, getting the URN from `GET /v1/accounts/{accountId}/linkedin-mentions`. The name must match the person's or Page's LinkedIn name exactly, or the mention renders as plain text. Profile or company URL mentions are not resolved here and are sent as plain text.
|
|
48257
48259
|
*/
|
|
48258
48260
|
commentReply?: string;
|
|
48259
48261
|
/**
|
|
@@ -48262,6 +48264,8 @@ type CreateCommentAutomationData = {
|
|
|
48262
48264
|
dmMessageVariations?: Array<(string)>;
|
|
48263
48265
|
/**
|
|
48264
48266
|
* Optional alternate public replies, rotated at random alongside commentReply (picked independently of the DM). Up to 5.
|
|
48267
|
+
*
|
|
48268
|
+
* LinkedIn mentions follow the commentReply rules.
|
|
48265
48269
|
*/
|
|
48266
48270
|
commentReplyVariations?: Array<(string)>;
|
|
48267
48271
|
/**
|
|
@@ -48513,6 +48517,9 @@ type UpdateCommentAutomationData = {
|
|
|
48513
48517
|
* Product card sent instead of the plain dmMessage bubble. Pass null to clear it and fall back to dmMessage. Mutually exclusive with buttons, including with the buttons already stored on the automation.
|
|
48514
48518
|
*/
|
|
48515
48519
|
template?: (CommentAutomationTemplate | null);
|
|
48520
|
+
/**
|
|
48521
|
+
* On LinkedIn, mention with `@[Name](urn:li:person:ID)` or `@[Name](urn:li:organization:ID)`, getting the URN from `GET /v1/accounts/{accountId}/linkedin-mentions`. The name must match the person's or Page's LinkedIn name exactly, or the mention renders as plain text. Profile or company URL mentions are not resolved here and are sent as plain text.
|
|
48522
|
+
*/
|
|
48516
48523
|
commentReply?: string;
|
|
48517
48524
|
/**
|
|
48518
48525
|
* Alternate DM texts for random rotation (see create). Pass [] to clear.
|
|
@@ -48520,6 +48527,8 @@ type UpdateCommentAutomationData = {
|
|
|
48520
48527
|
dmMessageVariations?: Array<(string)>;
|
|
48521
48528
|
/**
|
|
48522
48529
|
* Alternate public replies for random rotation. Pass [] to clear.
|
|
48530
|
+
*
|
|
48531
|
+
* LinkedIn mentions follow the commentReply rules.
|
|
48523
48532
|
*/
|
|
48524
48533
|
commentReplyVariations?: Array<(string)>;
|
|
48525
48534
|
/**
|
package/dist/index.js
CHANGED
|
@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
|
|
|
36
36
|
// package.json
|
|
37
37
|
var package_default = {
|
|
38
38
|
name: "@getlatedev/node",
|
|
39
|
-
version: "0.2.
|
|
39
|
+
version: "0.2.1394",
|
|
40
40
|
description: "The official Node.js library for the Zernio API",
|
|
41
41
|
main: "dist/index.js",
|
|
42
42
|
module: "dist/index.mjs",
|
package/dist/index.mjs
CHANGED
|
@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
|
|
|
5
5
|
// package.json
|
|
6
6
|
var package_default = {
|
|
7
7
|
name: "@getlatedev/node",
|
|
8
|
-
version: "0.2.
|
|
8
|
+
version: "0.2.1394",
|
|
9
9
|
description: "The official Node.js library for the Zernio API",
|
|
10
10
|
main: "dist/index.js",
|
|
11
11
|
module: "dist/index.mjs",
|
package/package.json
CHANGED
package/src/generated/sdk.gen.ts
CHANGED
|
@@ -2288,7 +2288,7 @@ export const verifyWhatsAppNumber = <ThrowOnError extends boolean = false>(optio
|
|
|
2288
2288
|
* The OAuth token can be perfectly valid while Meta refuses to serve the phone-number object (for example after a phone-side coexistence disconnect). So `tokenStatus` alone is not a liveness signal for WhatsApp.
|
|
2289
2289
|
*
|
|
2290
2290
|
* - When the Meta link is dead, `platformConnection.status` is `disconnected` and the overall `status` is `error`.
|
|
2291
|
-
* - When Meta reports that the number's inbound message webhook does not reach Zernio, `platformConnection.inboundWebhookSubscribed` is `false`, an entry is added to `issues`, and the overall `status` is at least `warning`.
|
|
2291
|
+
* - When Meta reports that the number's inbound message webhook does not reach Zernio, or subscribing the number's WhatsApp Business Account to Zernio's webhooks failed at connect, `platformConnection.inboundWebhookSubscribed` is `false`, an entry is added to `issues`, and the overall `status` is at least `warning`.
|
|
2292
2292
|
*
|
|
2293
2293
|
* ### Standalone ads connections (`googleads`, `redditads`)
|
|
2294
2294
|
*
|
|
@@ -26819,9 +26819,9 @@ export type GetAccountHealthResponse = ({
|
|
|
26819
26819
|
message?: string;
|
|
26820
26820
|
} | null;
|
|
26821
26821
|
/**
|
|
26822
|
-
* From the phone number's Meta health_status.
|
|
26822
|
+
* From the phone number's Meta health_status, overridden to `false` when subscribing the number's WhatsApp Business Account to Zernio's webhooks failed at connect.
|
|
26823
26823
|
*
|
|
26824
|
-
* - `false`: Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered, though the number is CONNECTED and can still send.
|
|
26824
|
+
* - `false`: Meta says Zernio is not subscribed to the message webhook for this number, or the subscribe failed when the number was connected, so inbound messages are not delivered, though the number is CONNECTED and can still send.
|
|
26825
26825
|
* - `false`, fix: re-subscribe (reconnect the number). If it stays `false`, the number is routed to a different WhatsApp Business Account (typically after linking it to a Facebook Page).
|
|
26826
26826
|
* - `true`: Meta reports no such problem.
|
|
26827
26827
|
* - `null`: Meta did not report it (read failed or no health_status); not evidence either way.
|
|
@@ -48899,6 +48899,8 @@ export type CreateCommentAutomationData = {
|
|
|
48899
48899
|
template?: (CommentAutomationTemplate);
|
|
48900
48900
|
/**
|
|
48901
48901
|
* Public reply to the comment. Optional on Instagram and Facebook; required on TikTok, Threads, LinkedIn and YouTube, where it is the automation's only action.
|
|
48902
|
+
*
|
|
48903
|
+
* On LinkedIn, mention with `@[Name](urn:li:person:ID)` or `@[Name](urn:li:organization:ID)`, getting the URN from `GET /v1/accounts/{accountId}/linkedin-mentions`. The name must match the person's or Page's LinkedIn name exactly, or the mention renders as plain text. Profile or company URL mentions are not resolved here and are sent as plain text.
|
|
48902
48904
|
*/
|
|
48903
48905
|
commentReply?: string;
|
|
48904
48906
|
/**
|
|
@@ -48907,6 +48909,8 @@ export type CreateCommentAutomationData = {
|
|
|
48907
48909
|
dmMessageVariations?: Array<(string)>;
|
|
48908
48910
|
/**
|
|
48909
48911
|
* Optional alternate public replies, rotated at random alongside commentReply (picked independently of the DM). Up to 5.
|
|
48912
|
+
*
|
|
48913
|
+
* LinkedIn mentions follow the commentReply rules.
|
|
48910
48914
|
*/
|
|
48911
48915
|
commentReplyVariations?: Array<(string)>;
|
|
48912
48916
|
/**
|
|
@@ -49164,6 +49168,9 @@ export type UpdateCommentAutomationData = {
|
|
|
49164
49168
|
* Product card sent instead of the plain dmMessage bubble. Pass null to clear it and fall back to dmMessage. Mutually exclusive with buttons, including with the buttons already stored on the automation.
|
|
49165
49169
|
*/
|
|
49166
49170
|
template?: (CommentAutomationTemplate | null);
|
|
49171
|
+
/**
|
|
49172
|
+
* On LinkedIn, mention with `@[Name](urn:li:person:ID)` or `@[Name](urn:li:organization:ID)`, getting the URN from `GET /v1/accounts/{accountId}/linkedin-mentions`. The name must match the person's or Page's LinkedIn name exactly, or the mention renders as plain text. Profile or company URL mentions are not resolved here and are sent as plain text.
|
|
49173
|
+
*/
|
|
49167
49174
|
commentReply?: string;
|
|
49168
49175
|
/**
|
|
49169
49176
|
* Alternate DM texts for random rotation (see create). Pass [] to clear.
|
|
@@ -49171,6 +49178,8 @@ export type UpdateCommentAutomationData = {
|
|
|
49171
49178
|
dmMessageVariations?: Array<(string)>;
|
|
49172
49179
|
/**
|
|
49173
49180
|
* Alternate public replies for random rotation. Pass [] to clear.
|
|
49181
|
+
*
|
|
49182
|
+
* LinkedIn mentions follow the commentReply rules.
|
|
49174
49183
|
*/
|
|
49175
49184
|
commentReplyVariations?: Array<(string)>;
|
|
49176
49185
|
/**
|