@getlatedev/node 0.2.1216 → 0.2.1217

package/dist/index.d.mts

@@ -12342,6 +12342,22 @@ type SocialAccount = {
      *
      */
     enabled?: boolean;
+    /**
+     * End of the account's publishing cooldown. Compare it with the current time: a value
+     * in the past means the cooldown has ended (the field is cleared on the next successful
+     * publish), null means no cooldown since the last successful publish. A cooldown starts
+     * when a post to the account fails with `errorCategory` `user_abuse` (spam, abuse or
+     * rate-limit errors), or when 10 or more posts to it fail within an hour with
+     * `user_content`, `platform_error`, `platform_rate_limit` or `unknown`. It doubles with
+     * each start inside a 24-hour window that opens at the first one (10, 20, 40, 80 minutes
+     * and so on, capped at 24 hours). On a YouTube account with a recorded successful upload
+     * it instead runs until 24 hours after that upload, or 1 hour when that upload is older
+     * than 24 hours. While it is in the future, POST /v1/posts (drafts excepted) and
+     * POST /v1/posts/{postId}/retry return 429 for this account, and this account's pending
+     * targets on posts scheduled before the cooldown ends are failed when it starts.
+     *
+     */
+    rateLimitedUntil?: (string) | null;
     /**
      * Platform-specific metadata. Fields vary by platform. For WhatsApp accounts, includes:
      * - qualityRating: Phone number quality rating from Meta (GREEN, YELLOW, RED, or UNKNOWN)

package/dist/index.d.ts

@@ -12342,6 +12342,22 @@ type SocialAccount = {
      *
      */
     enabled?: boolean;
+    /**
+     * End of the account's publishing cooldown. Compare it with the current time: a value
+     * in the past means the cooldown has ended (the field is cleared on the next successful
+     * publish), null means no cooldown since the last successful publish. A cooldown starts
+     * when a post to the account fails with `errorCategory` `user_abuse` (spam, abuse or
+     * rate-limit errors), or when 10 or more posts to it fail within an hour with
+     * `user_content`, `platform_error`, `platform_rate_limit` or `unknown`. It doubles with
+     * each start inside a 24-hour window that opens at the first one (10, 20, 40, 80 minutes
+     * and so on, capped at 24 hours). On a YouTube account with a recorded successful upload
+     * it instead runs until 24 hours after that upload, or 1 hour when that upload is older
+     * than 24 hours. While it is in the future, POST /v1/posts (drafts excepted) and
+     * POST /v1/posts/{postId}/retry return 429 for this account, and this account's pending
+     * targets on posts scheduled before the cooldown ends are failed when it starts.
+     *
+     */
+    rateLimitedUntil?: (string) | null;
     /**
      * Platform-specific metadata. Fields vary by platform. For WhatsApp accounts, includes:
      * - qualityRating: Phone number quality rating from Meta (GREEN, YELLOW, RED, or UNKNOWN)

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@getlatedev/node",
-  version: "0.2.1216",
+  version: "0.2.1217",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/dist/index.mjs

@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
 // package.json
 var package_default = {
   name: "@getlatedev/node",
-  version: "0.2.1216",
+  version: "0.2.1217",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getlatedev/node",
-  "version": "0.2.1216",
+  "version": "0.2.1217",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/types.gen.ts

@@ -10799,6 +10799,22 @@ export type SocialAccount = {
      *
      */
     enabled?: boolean;
+    /**
+     * End of the account's publishing cooldown. Compare it with the current time: a value
+     * in the past means the cooldown has ended (the field is cleared on the next successful
+     * publish), null means no cooldown since the last successful publish. A cooldown starts
+     * when a post to the account fails with `errorCategory` `user_abuse` (spam, abuse or
+     * rate-limit errors), or when 10 or more posts to it fail within an hour with
+     * `user_content`, `platform_error`, `platform_rate_limit` or `unknown`. It doubles with
+     * each start inside a 24-hour window that opens at the first one (10, 20, 40, 80 minutes
+     * and so on, capped at 24 hours). On a YouTube account with a recorded successful upload
+     * it instead runs until 24 hours after that upload, or 1 hour when that upload is older
+     * than 24 hours. While it is in the future, POST /v1/posts (drafts excepted) and
+     * POST /v1/posts/{postId}/retry return 429 for this account, and this account's pending
+     * targets on posts scheduled before the cooldown ends are failed when it starts.
+     *
+     */
+    rateLimitedUntil?: (string) | null;
     /**
      * Platform-specific metadata. Fields vary by platform. For WhatsApp accounts, includes:
      * - qualityRating: Phone number quality rating from Meta (GREEN, YELLOW, RED, or UNKNOWN)