zernio-sdk 0.0.1418 → 0.0.1420

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 138b9a4b60bc83d923356d85b01d5f68a00dff5b8c92575746a1a501534706ec
-  data.tar.gz: 625d71d4effe3637997e7ff6c279b3b55721d3cdcd1920206f67539a1f4995ad
+  metadata.gz: 9a4a34cbbf3413a7d998f3f5f61a2e40ddd0676136ff10dfd74746951d49b415
+  data.tar.gz: b54a52e1d2ee3c0ca355024dbc6b0a01b23c4da5d84c1e9e949d93fab7138d82
 SHA512:
-  metadata.gz: c86ef3f6fb5dca382376811d0a6e2060bcbb1b143bf2babd77eb9b837b85311362f22657f2de41c6f8c55d876afb5e6e19581e599b2d6adeeb142eeb555d9a34
-  data.tar.gz: d461bf41425a27f5b00607458adb44d9b6a6f3c219a16d89f0589aa9a7e3ebefa39fcb39f73188f0035324205d149e207efb11737b9327ecac31f91f3f9c3796
+  metadata.gz: a51aff46df177a3e4050cc30ac39b2fa4995ef650d7c79c389b03e2a0e3cb00cc1542bf4576f04f7cd9308d5232d00f6569b0253cc48d76a894600c7832adf53
+  data.tar.gz: d8e8dd4659b9cf06f1d954f61dc7f002b483646a7f9cc70a7deba8601b91329eced99546b81d58a8f24da72c4de9ad5c1083670accc2a01e95f1d5c260fe6d88

data/README.md

@@ -21,7 +21,7 @@ send is reused as that id.
 
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
-- API version: 1.285.1
+- API version: 1.286.2
 - Package version: 0.1.0
 - Generator version: 7.19.0
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen

data/docs/CommentAutomationsApi.md

@@ -18,7 +18,7 @@ All URIs are relative to *https://zernio.com/api*
 
 Create comment-to-DM automation
 
-Create a keyword-triggered automation. On Instagram and Facebook, when someone comments a matching keyword (or, with `trigger: story_reply`, replies to your Instagram story with one), they automatically receive a DM.  Platforms:   * `instagram`, `facebook`: the full DM automation (private reply, buttons,     product card, audience rules, follow gate) plus the optional public reply.   * `tiktok`, `threads`, `linkedin`, `youtube`: public reply only. These     platforms have no private reply to a comment, so the automation answers a     matching comment with `commentReply` and nothing else. `commentReply` is     required and the DM fields (`dmMessage`, `dmMessageVariations`, `buttons`,     `template`, `quickReplies`, `alsoMatchInDms`, `audience`, `followGate`,     `dmDelaySeconds`, `commentReplyDelaySeconds`) are rejected with a 400 naming the     field. TikTok comments arrive by webhook (TikTok business accounts only); the     others are read by the comment poll, so a reply follows the comment by up to the     poll interval (10 minutes on posts from the last 24 hours, longer on older posts).     `repeatPolicy` applies there too: with the default `once`, a person gets one public     reply per automation, and their later comments get none.   * X accounts are refused with a 400 (`platform_not_supported`): X comment polling is     off, so an X automation could never fire.  To continue into a specific workflow after the recipient taps a button, use `{\"type\":\"postback\",\"title\":\"Send it\",\"payload\":\"zernio:workflow:<workflowId>\"}`. The target must be active and belong to the same account and profile. This also works for product-card buttons. The tap starts that workflow directly, without matching its keyword or first-message condition. A tap on a workflow that is waiting on `wait_for_reply` in that conversation answers that wait and resumes the run. A tap on a different active workflow starts it and exits the other live runs. Stale or invalid targets still do nothing. The initial comment DM alone does not start the workflow: the recipient must tap.  Triggers (`trigger`):   * `comment` (default): fires on keyword comments on a post or reel.   * `story_reply`: fires when someone replies to your Instagram story with a keyword,     and answers them with a DM. Set `platformPostId` to a story media id to scope to     one story, or omit it to match replies to any story.   * `live_comment` (Instagram only): fires on keyword comments made during one of     your Instagram live broadcasts and answers them with a private reply. `comment`     automations never fire on live comments, and `live_comment` ones never fire on     post comments. Meta only accepts the private reply while the broadcast is live.   * `story_mention` (Instagram only): fires when someone mentions your account in     their story, and answers them with a DM. A mention carries no text and Meta does     not identify the story, so `keywords` must be empty and `platformPostId` omitted.  Comments on Instagram and Facebook arrive by webhook. Every 10 minutes Zernio also reads the latest comments and replies back (the bound post, or the 5 newest posts for an account-wide automation, up to 20 Graph reads per account per run; a post not fully read is picked up again on the next run) and runs any comment the webhook did not deliver, so a dropped webhook still fires. A comment is answered at most once whichever path sees it first.  Targeting (comment trigger):   * Per-post: set `platformPostId` to scope to one specific post (only one active     per-post automation is allowed per post).   * Account-wide (\"any post\"): omit `platformPostId` (and `postId`). The automation     evaluates every comment on every post on the account. You can stack unlimited     account-wide automations, each with its own keyword set, and they all run     independently. Per-post automations take priority on their post.  Audience (`audience`, Instagram only): restrict the automation to followers or non-followers, and/or to accounts above a follower count. Instagram only reveals the follow relationship for people who have messaged the account, so `audience.whenUnknown` decides what happens for everyone else - including `verify`, which sends a one-tap confirmation DM (`followGate`) and then delivers the real DM automatically. People we already know follow you skip the tap entirely. Set `audience.tapToUnlock: true` instead to send that button DM to every commenter and deliver the real DM on the tap with no follow check.  Set `alsoMatchInDms: true` on a `comment` automation to also answer people who send a keyword as a direct message instead of commenting it. One automation then covers both doors, and each door is deduplicated separately (someone who already got the DM from their comment still gets it if they later DM the keyword). Requires at least one keyword.  Links in the DM's buttons can be click-tracked (`linkTracking`, on by default) and clickers optionally tagged (`clickTag`) for segmentation. Stats returned include delivered, read, and link clicks.  Personalisation: `{{first_name}}`, `{{name}}` and `{{username}}` in `dmMessage`, `commentReply`, their variations and button titles resolve from the commenter (first word of the display name, the display name, the platform username). A value the platform does not give us resolves to an empty string.  Behaviour: `repeatPolicy` decides whether a person can get the DM again, `dedupeSameTextHours` stops two automations sending the same text to one person, `publicReplyPolicy` decides whether the public reply waits for the DM, and `actions` likes or hides the matched comment. 
+Create a keyword-triggered automation. On Instagram and Facebook, when someone comments a matching keyword (or, with `trigger: story_reply`, replies to your Instagram story with one), they automatically receive a DM.  Platforms:   * `instagram`, `facebook`: the full DM automation (private reply, buttons,     product card, audience rules, follow gate) plus the optional public reply.   * `tiktok`, `threads`, `linkedin`, `youtube`: public reply only. These     platforms have no private reply to a comment, so the automation answers a     matching comment with `commentReply` and nothing else. `commentReply` is     required and the DM fields (`dmMessage`, `dmMessageVariations`, `buttons`,     `template`, `quickReplies`, `alsoMatchInDms`, `audience`, `followGate`,     `dmDelaySeconds`, `commentReplyDelaySeconds`) are rejected with a 400 naming the     field. TikTok comments arrive by webhook (TikTok business accounts only); the     others are read by the comment poll, so a reply follows the comment by up to the     poll interval (10 minutes on posts from the last 24 hours, longer on older posts).     `repeatPolicy` applies there too: with the default `once`, a person gets one public     reply per automation, and their later comments get none.   * X accounts are refused with a 400 (`platform_not_supported`): X comment polling is     off, so an X automation could never fire.  To continue into a specific workflow after the recipient taps a button, use `{\"type\":\"postback\",\"title\":\"Send it\",\"payload\":\"zernio:workflow:<workflowId>\"}`. The target must be active and belong to the same account and profile. This also works for product-card buttons. The tap starts that workflow directly, without matching its keyword or first-message condition. A tap on a workflow that is waiting on `wait_for_reply` in that conversation answers that wait and resumes the run. A tap on a different active workflow starts it and exits the other live runs. Stale or invalid targets still do nothing. The initial comment DM alone does not start the workflow: the recipient must tap.  Triggers (`trigger`):   * `comment` (default): fires on keyword comments on a post or reel.   * `story_reply`: fires when someone replies to your Instagram story with a keyword,     and answers them with a DM. Set `platformPostId` to a story media id to scope to     one story, or omit it to match replies to any story.   * `live_comment` (Instagram only): fires on keyword comments made during one of     your Instagram live broadcasts and answers them with a private reply. `comment`     automations never fire on live comments, and `live_comment` ones never fire on     post comments. Meta only accepts the private reply while the broadcast is live.   * `story_mention` (Instagram only): fires when someone mentions your account in     their story, and answers them with a DM. A mention carries no text and Meta does     not identify the story, so `keywords` must be empty and `platformPostId` omitted.  Comments on Instagram and Facebook arrive by webhook. Every 10 minutes Zernio also reads the latest comments and replies back (the bound post, or the 5 newest posts for an account-wide automation, up to 20 Graph reads per account per run; a post not fully read is picked up again on the next run) and runs any comment the webhook did not deliver, so a dropped webhook still fires. A comment is answered at most once whichever path sees it first.  Targeting (comment trigger):   * Per-post: set `platformPostId` to scope to one specific post (only one active     per-post automation is allowed per post).   * Account-wide (\"any post\"): omit `platformPostId` (and `postId`). The automation     evaluates every comment on every post on the account. You can stack unlimited     account-wide automations, each with its own keyword set, and they all run     independently. Per-post automations take priority on their post.  Audience (`audience`, Instagram only): restrict the automation to followers or non-followers, and/or to accounts above a follower count. Instagram only reveals the follow relationship for people who have messaged the account, so `audience.whenUnknown` decides what happens for everyone else - including `verify`, which sends a one-tap confirmation DM (`followGate`) and then delivers the real DM automatically. People we already know follow you skip the tap entirely. Set `audience.tapToUnlock: true` instead to send that button DM to every commenter and deliver the real DM on the tap with no follow check.  Set `alsoMatchInDms: true` on a `comment` automation to also answer people who send a keyword as a direct message instead of commenting it. One automation then covers both doors, and each door is deduplicated separately (someone who already got the DM from their comment still gets it if they later DM the keyword). Requires at least one keyword.  Links in the DM's buttons can be click-tracked (`linkTracking`, on by default) and clickers optionally tagged (`clickTag`) for segmentation. Stats returned include delivered, read, and link clicks.  Personalisation: `{{first_name}}`, `{{name}}` and `{{username}}` in `dmMessage`, `commentReply`, their variations and button titles resolve from the commenter. `{{first_name}}` is the first word of the display name and `{{name}}` the display name; when the platform gives no display name both fall back to the platform username (unless it is all digits). `{{username}}` is the platform username. A value still unknown resolves to an empty string and the space before it is dropped.  Behaviour: `repeatPolicy` decides whether a person can get the DM again, `dedupeSameTextHours` stops two automations sending the same text to one person, `publicReplyPolicy` decides whether the public reply waits for the DM, and `actions` likes or hides the matched comment. 
 
 ### Examples
 

data/docs/CommentsApi.md

@@ -41,7 +41,7 @@ Zernio.configure do |config|
 end
 
 api_instance = Zernio::CommentsApi.new
-post_id = 'post_id_example' # String | Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID.
+post_id = 'post_id_example' # String | Zernio post ID or platform-specific post ID. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>); a bare number is read as an activity id (urn:li:activity:<n>).
 account_id = 'account_id_example' # String | 
 comment_id = 'comment_id_example' # String | For LinkedIn, accepts either the numeric comment ID or the composite comment URN returned by the comments listing (e.g. urn:li:comment:(threadUrn,id))
 
@@ -76,7 +76,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **post_id** | **String** | Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID. |  |
+| **post_id** | **String** | Zernio post ID or platform-specific post ID. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:&lt;id&gt; or urn:li:ugcPost:&lt;id&gt;); a bare number is read as an activity id (urn:li:activity:&lt;n&gt;). |  |
 | **account_id** | **String** |  |  |
 | **comment_id** | **String** | For LinkedIn, accepts either the numeric comment ID or the composite comment URN returned by the comments listing (e.g. urn:li:comment:(threadUrn,id)) |  |
 
@@ -187,7 +187,7 @@ Zernio.configure do |config|
 end
 
 api_instance = Zernio::CommentsApi.new
-post_id = 'post_id_example' # String | Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook, a comment ID is also accepted here and returns that comment's replies, kept for backwards compatibility; prefer the `commentId` query parameter, which also works on Instagram.
+post_id = 'post_id_example' # String | Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>). A bare number is read as an activity id (urn:li:activity:<n>, the number in a linkedin.com/feed/update URL); a share or ugcPost number passed bare returns an empty list. On Facebook, a comment ID is also accepted here and returns that comment's replies, kept for backwards compatibility; prefer the `commentId` query parameter, which also works on Instagram.
 account_id = 'account_id_example' # String | 
 opts = {
   subreddit: 'subreddit_example', # String | (Reddit only) Subreddit name
@@ -227,7 +227,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **post_id** | **String** | Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook, a comment ID is also accepted here and returns that comment&#39;s replies, kept for backwards compatibility; prefer the &#x60;commentId&#x60; query parameter, which also works on Instagram. |  |
+| **post_id** | **String** | Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:&lt;id&gt; or urn:li:ugcPost:&lt;id&gt;). A bare number is read as an activity id (urn:li:activity:&lt;n&gt;, the number in a linkedin.com/feed/update URL); a share or ugcPost number passed bare returns an empty list. On Facebook, a comment ID is also accepted here and returns that comment&#39;s replies, kept for backwards compatibility; prefer the &#x60;commentId&#x60; query parameter, which also works on Instagram. |  |
 | **account_id** | **String** |  |  |
 | **subreddit** | **String** | (Reddit only) Subreddit name | [optional] |
 | **limit** | **Integer** | Maximum number of comments to return | [optional][default to 25] |
@@ -645,7 +645,7 @@ Zernio.configure do |config|
 end
 
 api_instance = Zernio::CommentsApi.new
-post_id = 'post_id_example' # String | Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID.
+post_id = 'post_id_example' # String | Zernio post ID or platform-specific post ID. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>); a bare number is read as an activity id (urn:li:activity:<n>).
 reply_to_inbox_post_request = Zernio::ReplyToInboxPostRequest.new({account_id: 'account_id_example', message: 'message_example'}) # ReplyToInboxPostRequest | 
 opts = {
   idempotency_key: 'idempotency_key_example' # String | Optional client-generated unique key (e.g. a UUID) that makes retries safe. Same key + same body replays the original response; same key + different body → 422; key still processing → 409. A request cut off mid-handler (for example by a function timeout) can leave its key in progress, answering 409 until the key expires after 24 hours.
@@ -682,7 +682,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **post_id** | **String** | Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID. |  |
+| **post_id** | **String** | Zernio post ID or platform-specific post ID. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:&lt;id&gt; or urn:li:ugcPost:&lt;id&gt;); a bare number is read as an activity id (urn:li:activity:&lt;n&gt;). |  |
 | **reply_to_inbox_post_request** | [**ReplyToInboxPostRequest**](ReplyToInboxPostRequest.md) |  |  |
 | **idempotency_key** | **String** | Optional client-generated unique key (e.g. a UUID) that makes retries safe. Same key + same body replays the original response; same key + different body → 422; key still processing → 409. A request cut off mid-handler (for example by a function timeout) can leave its key in progress, answering 409 until the key expires after 24 hours. | [optional] |
 

data/docs/GetInboxPostComments200ResponseMeta.md

@@ -8,6 +8,7 @@
 | **post_id** | **String** |  | [optional] |
 | **account_id** | **String** |  | [optional] |
 | **subreddit** | **String** | (Reddit only) Subreddit name | [optional] |
+| **post_urn** | **String** | (LinkedIn only) The post URN that was queried, after a bare number is read as urn:li:activity:<n> | [optional] |
 | **last_updated** | **Time** |  | [optional] |
 | **ad_comments** | [**GetInboxPostComments200ResponseMetaAdComments**](GetInboxPostComments200ResponseMetaAdComments.md) |  | [optional] |
 
@@ -21,6 +22,7 @@ instance = Zernio::GetInboxPostComments200ResponseMeta.new(
   post_id: null,
   account_id: null,
   subreddit: null,
+  post_urn: null,
   last_updated: null,
   ad_comments: null
 )

data/docs/UpdatePostMetadataRequest.md

@@ -12,7 +12,7 @@
 | **tags** | **Array<String>** | Array of keyword tags (max 500 characters combined for YouTube) | [optional] |
 | **category_id** | **String** | YouTube video category ID | [optional] |
 | **privacy_status** | **String** | Video privacy setting | [optional] |
-| **thumbnail_url** | **String** | Public URL of a custom thumbnail image (JPEG, PNG, or GIF, max 50 MB, recommended 1280x720). Works on any video you own, including existing videos not published through Zernio. The channel must be verified (phone verification) to set custom thumbnails. If the thumbnail cannot be set (YouTube refuses it, for example a channel without the custom-thumbnail permission or a video not owned by the connected channel, or the image URL cannot be fetched or is not a supported format or size), the request answers 400 with the reason and no field is updated. A temporary YouTube or network failure answers 500 and can be retried. | [optional] |
+| **thumbnail_url** | **String** | Public URL of a custom thumbnail image (JPEG, PNG, or GIF, max 50 MB, recommended 1280x720). Works on any video you own, including existing videos not published through Zernio. The channel must be verified (phone verification) to set custom thumbnails. If the thumbnail cannot be set (YouTube refuses it, for example a channel without the custom-thumbnail permission or a video not owned by the connected channel, or the image URL cannot be fetched or is not a supported format or size), the request answers 400 with the reason and no field is updated. A YouTube thumbnail rate limit (uploadRateLimitExceeded) answers 429; retry later, not immediately, because retries keep the channel over its limit. Any other temporary YouTube or network failure answers 500 and can be retried. | [optional] |
 | **made_for_kids** | **Boolean** | COPPA compliance flag. Set true for child-directed content (restricts comments, notifications, ad targeting). | [optional] |
 | **contains_synthetic_media** | **Boolean** | AI-generated content disclosure. Set true if the video contains synthetic content that could be mistaken for real. YouTube may add a label. | [optional] |
 | **playlist_id** | **String** | YouTube playlist ID to add the video to (e.g. 'PLxxxxxxxxxxxxx'). Use GET /v1/accounts/{id}/youtube-playlists to list available playlists. Only playlists owned by the channel are supported. | [optional] |

data/lib/zernio-sdk/api/account_groups_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/account_settings_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/accounts_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/ad_accounts_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/ad_audiences_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/ad_campaigns_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/ad_creatives_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/ad_insights_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/ad_library_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/ad_targeting_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/analytics_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/api_keys_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/blogs_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/branded_calling_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/broadcasts_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/business_agent_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/calls_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/changelog_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/comment_automations_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0
@@ -20,7 +20,7 @@ module Zernio
       @api_client = api_client
     end
     # Create comment-to-DM automation
-    # Create a keyword-triggered automation. On Instagram and Facebook, when someone comments a matching keyword (or, with `trigger: story_reply`, replies to your Instagram story with one), they automatically receive a DM.  Platforms:   * `instagram`, `facebook`: the full DM automation (private reply, buttons,     product card, audience rules, follow gate) plus the optional public reply.   * `tiktok`, `threads`, `linkedin`, `youtube`: public reply only. These     platforms have no private reply to a comment, so the automation answers a     matching comment with `commentReply` and nothing else. `commentReply` is     required and the DM fields (`dmMessage`, `dmMessageVariations`, `buttons`,     `template`, `quickReplies`, `alsoMatchInDms`, `audience`, `followGate`,     `dmDelaySeconds`, `commentReplyDelaySeconds`) are rejected with a 400 naming the     field. TikTok comments arrive by webhook (TikTok business accounts only); the     others are read by the comment poll, so a reply follows the comment by up to the     poll interval (10 minutes on posts from the last 24 hours, longer on older posts).     `repeatPolicy` applies there too: with the default `once`, a person gets one public     reply per automation, and their later comments get none.   * X accounts are refused with a 400 (`platform_not_supported`): X comment polling is     off, so an X automation could never fire.  To continue into a specific workflow after the recipient taps a button, use `{\"type\":\"postback\",\"title\":\"Send it\",\"payload\":\"zernio:workflow:<workflowId>\"}`. The target must be active and belong to the same account and profile. This also works for product-card buttons. The tap starts that workflow directly, without matching its keyword or first-message condition. A tap on a workflow that is waiting on `wait_for_reply` in that conversation answers that wait and resumes the run. A tap on a different active workflow starts it and exits the other live runs. Stale or invalid targets still do nothing. The initial comment DM alone does not start the workflow: the recipient must tap.  Triggers (`trigger`):   * `comment` (default): fires on keyword comments on a post or reel.   * `story_reply`: fires when someone replies to your Instagram story with a keyword,     and answers them with a DM. Set `platformPostId` to a story media id to scope to     one story, or omit it to match replies to any story.   * `live_comment` (Instagram only): fires on keyword comments made during one of     your Instagram live broadcasts and answers them with a private reply. `comment`     automations never fire on live comments, and `live_comment` ones never fire on     post comments. Meta only accepts the private reply while the broadcast is live.   * `story_mention` (Instagram only): fires when someone mentions your account in     their story, and answers them with a DM. A mention carries no text and Meta does     not identify the story, so `keywords` must be empty and `platformPostId` omitted.  Comments on Instagram and Facebook arrive by webhook. Every 10 minutes Zernio also reads the latest comments and replies back (the bound post, or the 5 newest posts for an account-wide automation, up to 20 Graph reads per account per run; a post not fully read is picked up again on the next run) and runs any comment the webhook did not deliver, so a dropped webhook still fires. A comment is answered at most once whichever path sees it first.  Targeting (comment trigger):   * Per-post: set `platformPostId` to scope to one specific post (only one active     per-post automation is allowed per post).   * Account-wide (\"any post\"): omit `platformPostId` (and `postId`). The automation     evaluates every comment on every post on the account. You can stack unlimited     account-wide automations, each with its own keyword set, and they all run     independently. Per-post automations take priority on their post.  Audience (`audience`, Instagram only): restrict the automation to followers or non-followers, and/or to accounts above a follower count. Instagram only reveals the follow relationship for people who have messaged the account, so `audience.whenUnknown` decides what happens for everyone else - including `verify`, which sends a one-tap confirmation DM (`followGate`) and then delivers the real DM automatically. People we already know follow you skip the tap entirely. Set `audience.tapToUnlock: true` instead to send that button DM to every commenter and deliver the real DM on the tap with no follow check.  Set `alsoMatchInDms: true` on a `comment` automation to also answer people who send a keyword as a direct message instead of commenting it. One automation then covers both doors, and each door is deduplicated separately (someone who already got the DM from their comment still gets it if they later DM the keyword). Requires at least one keyword.  Links in the DM's buttons can be click-tracked (`linkTracking`, on by default) and clickers optionally tagged (`clickTag`) for segmentation. Stats returned include delivered, read, and link clicks.  Personalisation: `{{first_name}}`, `{{name}}` and `{{username}}` in `dmMessage`, `commentReply`, their variations and button titles resolve from the commenter (first word of the display name, the display name, the platform username). A value the platform does not give us resolves to an empty string.  Behaviour: `repeatPolicy` decides whether a person can get the DM again, `dedupeSameTextHours` stops two automations sending the same text to one person, `publicReplyPolicy` decides whether the public reply waits for the DM, and `actions` likes or hides the matched comment. 
+    # Create a keyword-triggered automation. On Instagram and Facebook, when someone comments a matching keyword (or, with `trigger: story_reply`, replies to your Instagram story with one), they automatically receive a DM.  Platforms:   * `instagram`, `facebook`: the full DM automation (private reply, buttons,     product card, audience rules, follow gate) plus the optional public reply.   * `tiktok`, `threads`, `linkedin`, `youtube`: public reply only. These     platforms have no private reply to a comment, so the automation answers a     matching comment with `commentReply` and nothing else. `commentReply` is     required and the DM fields (`dmMessage`, `dmMessageVariations`, `buttons`,     `template`, `quickReplies`, `alsoMatchInDms`, `audience`, `followGate`,     `dmDelaySeconds`, `commentReplyDelaySeconds`) are rejected with a 400 naming the     field. TikTok comments arrive by webhook (TikTok business accounts only); the     others are read by the comment poll, so a reply follows the comment by up to the     poll interval (10 minutes on posts from the last 24 hours, longer on older posts).     `repeatPolicy` applies there too: with the default `once`, a person gets one public     reply per automation, and their later comments get none.   * X accounts are refused with a 400 (`platform_not_supported`): X comment polling is     off, so an X automation could never fire.  To continue into a specific workflow after the recipient taps a button, use `{\"type\":\"postback\",\"title\":\"Send it\",\"payload\":\"zernio:workflow:<workflowId>\"}`. The target must be active and belong to the same account and profile. This also works for product-card buttons. The tap starts that workflow directly, without matching its keyword or first-message condition. A tap on a workflow that is waiting on `wait_for_reply` in that conversation answers that wait and resumes the run. A tap on a different active workflow starts it and exits the other live runs. Stale or invalid targets still do nothing. The initial comment DM alone does not start the workflow: the recipient must tap.  Triggers (`trigger`):   * `comment` (default): fires on keyword comments on a post or reel.   * `story_reply`: fires when someone replies to your Instagram story with a keyword,     and answers them with a DM. Set `platformPostId` to a story media id to scope to     one story, or omit it to match replies to any story.   * `live_comment` (Instagram only): fires on keyword comments made during one of     your Instagram live broadcasts and answers them with a private reply. `comment`     automations never fire on live comments, and `live_comment` ones never fire on     post comments. Meta only accepts the private reply while the broadcast is live.   * `story_mention` (Instagram only): fires when someone mentions your account in     their story, and answers them with a DM. A mention carries no text and Meta does     not identify the story, so `keywords` must be empty and `platformPostId` omitted.  Comments on Instagram and Facebook arrive by webhook. Every 10 minutes Zernio also reads the latest comments and replies back (the bound post, or the 5 newest posts for an account-wide automation, up to 20 Graph reads per account per run; a post not fully read is picked up again on the next run) and runs any comment the webhook did not deliver, so a dropped webhook still fires. A comment is answered at most once whichever path sees it first.  Targeting (comment trigger):   * Per-post: set `platformPostId` to scope to one specific post (only one active     per-post automation is allowed per post).   * Account-wide (\"any post\"): omit `platformPostId` (and `postId`). The automation     evaluates every comment on every post on the account. You can stack unlimited     account-wide automations, each with its own keyword set, and they all run     independently. Per-post automations take priority on their post.  Audience (`audience`, Instagram only): restrict the automation to followers or non-followers, and/or to accounts above a follower count. Instagram only reveals the follow relationship for people who have messaged the account, so `audience.whenUnknown` decides what happens for everyone else - including `verify`, which sends a one-tap confirmation DM (`followGate`) and then delivers the real DM automatically. People we already know follow you skip the tap entirely. Set `audience.tapToUnlock: true` instead to send that button DM to every commenter and deliver the real DM on the tap with no follow check.  Set `alsoMatchInDms: true` on a `comment` automation to also answer people who send a keyword as a direct message instead of commenting it. One automation then covers both doors, and each door is deduplicated separately (someone who already got the DM from their comment still gets it if they later DM the keyword). Requires at least one keyword.  Links in the DM's buttons can be click-tracked (`linkTracking`, on by default) and clickers optionally tagged (`clickTag`) for segmentation. Stats returned include delivered, read, and link clicks.  Personalisation: `{{first_name}}`, `{{name}}` and `{{username}}` in `dmMessage`, `commentReply`, their variations and button titles resolve from the commenter. `{{first_name}}` is the first word of the display name and `{{name}}` the display name; when the platform gives no display name both fall back to the platform username (unless it is all digits). `{{username}}` is the platform username. A value still unknown resolves to an empty string and the space before it is dropped.  Behaviour: `repeatPolicy` decides whether a person can get the DM again, `dedupeSameTextHours` stops two automations sending the same text to one person, `publicReplyPolicy` decides whether the public reply waits for the DM, and `actions` likes or hides the matched comment. 
     # @param create_comment_automation_request [CreateCommentAutomationRequest] 
     # @param [Hash] opts the optional parameters
     # @return [CreateCommentAutomation200Response]
@@ -30,7 +30,7 @@ module Zernio
     end
 
     # Create comment-to-DM automation
-    # Create a keyword-triggered automation. On Instagram and Facebook, when someone comments a matching keyword (or, with &#x60;trigger: story_reply&#x60;, replies to your Instagram story with one), they automatically receive a DM.  Platforms:   * &#x60;instagram&#x60;, &#x60;facebook&#x60;: the full DM automation (private reply, buttons,     product card, audience rules, follow gate) plus the optional public reply.   * &#x60;tiktok&#x60;, &#x60;threads&#x60;, &#x60;linkedin&#x60;, &#x60;youtube&#x60;: public reply only. These     platforms have no private reply to a comment, so the automation answers a     matching comment with &#x60;commentReply&#x60; and nothing else. &#x60;commentReply&#x60; is     required and the DM fields (&#x60;dmMessage&#x60;, &#x60;dmMessageVariations&#x60;, &#x60;buttons&#x60;,     &#x60;template&#x60;, &#x60;quickReplies&#x60;, &#x60;alsoMatchInDms&#x60;, &#x60;audience&#x60;, &#x60;followGate&#x60;,     &#x60;dmDelaySeconds&#x60;, &#x60;commentReplyDelaySeconds&#x60;) are rejected with a 400 naming the     field. TikTok comments arrive by webhook (TikTok business accounts only); the     others are read by the comment poll, so a reply follows the comment by up to the     poll interval (10 minutes on posts from the last 24 hours, longer on older posts).     &#x60;repeatPolicy&#x60; applies there too: with the default &#x60;once&#x60;, a person gets one public     reply per automation, and their later comments get none.   * X accounts are refused with a 400 (&#x60;platform_not_supported&#x60;): X comment polling is     off, so an X automation could never fire.  To continue into a specific workflow after the recipient taps a button, use &#x60;{\&quot;type\&quot;:\&quot;postback\&quot;,\&quot;title\&quot;:\&quot;Send it\&quot;,\&quot;payload\&quot;:\&quot;zernio:workflow:&lt;workflowId&gt;\&quot;}&#x60;. The target must be active and belong to the same account and profile. This also works for product-card buttons. The tap starts that workflow directly, without matching its keyword or first-message condition. A tap on a workflow that is waiting on &#x60;wait_for_reply&#x60; in that conversation answers that wait and resumes the run. A tap on a different active workflow starts it and exits the other live runs. Stale or invalid targets still do nothing. The initial comment DM alone does not start the workflow: the recipient must tap.  Triggers (&#x60;trigger&#x60;):   * &#x60;comment&#x60; (default): fires on keyword comments on a post or reel.   * &#x60;story_reply&#x60;: fires when someone replies to your Instagram story with a keyword,     and answers them with a DM. Set &#x60;platformPostId&#x60; to a story media id to scope to     one story, or omit it to match replies to any story.   * &#x60;live_comment&#x60; (Instagram only): fires on keyword comments made during one of     your Instagram live broadcasts and answers them with a private reply. &#x60;comment&#x60;     automations never fire on live comments, and &#x60;live_comment&#x60; ones never fire on     post comments. Meta only accepts the private reply while the broadcast is live.   * &#x60;story_mention&#x60; (Instagram only): fires when someone mentions your account in     their story, and answers them with a DM. A mention carries no text and Meta does     not identify the story, so &#x60;keywords&#x60; must be empty and &#x60;platformPostId&#x60; omitted.  Comments on Instagram and Facebook arrive by webhook. Every 10 minutes Zernio also reads the latest comments and replies back (the bound post, or the 5 newest posts for an account-wide automation, up to 20 Graph reads per account per run; a post not fully read is picked up again on the next run) and runs any comment the webhook did not deliver, so a dropped webhook still fires. A comment is answered at most once whichever path sees it first.  Targeting (comment trigger):   * Per-post: set &#x60;platformPostId&#x60; to scope to one specific post (only one active     per-post automation is allowed per post).   * Account-wide (\&quot;any post\&quot;): omit &#x60;platformPostId&#x60; (and &#x60;postId&#x60;). The automation     evaluates every comment on every post on the account. You can stack unlimited     account-wide automations, each with its own keyword set, and they all run     independently. Per-post automations take priority on their post.  Audience (&#x60;audience&#x60;, Instagram only): restrict the automation to followers or non-followers, and/or to accounts above a follower count. Instagram only reveals the follow relationship for people who have messaged the account, so &#x60;audience.whenUnknown&#x60; decides what happens for everyone else - including &#x60;verify&#x60;, which sends a one-tap confirmation DM (&#x60;followGate&#x60;) and then delivers the real DM automatically. People we already know follow you skip the tap entirely. Set &#x60;audience.tapToUnlock: true&#x60; instead to send that button DM to every commenter and deliver the real DM on the tap with no follow check.  Set &#x60;alsoMatchInDms: true&#x60; on a &#x60;comment&#x60; automation to also answer people who send a keyword as a direct message instead of commenting it. One automation then covers both doors, and each door is deduplicated separately (someone who already got the DM from their comment still gets it if they later DM the keyword). Requires at least one keyword.  Links in the DM&#39;s buttons can be click-tracked (&#x60;linkTracking&#x60;, on by default) and clickers optionally tagged (&#x60;clickTag&#x60;) for segmentation. Stats returned include delivered, read, and link clicks.  Personalisation: &#x60;{{first_name}}&#x60;, &#x60;{{name}}&#x60; and &#x60;{{username}}&#x60; in &#x60;dmMessage&#x60;, &#x60;commentReply&#x60;, their variations and button titles resolve from the commenter (first word of the display name, the display name, the platform username). A value the platform does not give us resolves to an empty string.  Behaviour: &#x60;repeatPolicy&#x60; decides whether a person can get the DM again, &#x60;dedupeSameTextHours&#x60; stops two automations sending the same text to one person, &#x60;publicReplyPolicy&#x60; decides whether the public reply waits for the DM, and &#x60;actions&#x60; likes or hides the matched comment. 
+    # Create a keyword-triggered automation. On Instagram and Facebook, when someone comments a matching keyword (or, with &#x60;trigger: story_reply&#x60;, replies to your Instagram story with one), they automatically receive a DM.  Platforms:   * &#x60;instagram&#x60;, &#x60;facebook&#x60;: the full DM automation (private reply, buttons,     product card, audience rules, follow gate) plus the optional public reply.   * &#x60;tiktok&#x60;, &#x60;threads&#x60;, &#x60;linkedin&#x60;, &#x60;youtube&#x60;: public reply only. These     platforms have no private reply to a comment, so the automation answers a     matching comment with &#x60;commentReply&#x60; and nothing else. &#x60;commentReply&#x60; is     required and the DM fields (&#x60;dmMessage&#x60;, &#x60;dmMessageVariations&#x60;, &#x60;buttons&#x60;,     &#x60;template&#x60;, &#x60;quickReplies&#x60;, &#x60;alsoMatchInDms&#x60;, &#x60;audience&#x60;, &#x60;followGate&#x60;,     &#x60;dmDelaySeconds&#x60;, &#x60;commentReplyDelaySeconds&#x60;) are rejected with a 400 naming the     field. TikTok comments arrive by webhook (TikTok business accounts only); the     others are read by the comment poll, so a reply follows the comment by up to the     poll interval (10 minutes on posts from the last 24 hours, longer on older posts).     &#x60;repeatPolicy&#x60; applies there too: with the default &#x60;once&#x60;, a person gets one public     reply per automation, and their later comments get none.   * X accounts are refused with a 400 (&#x60;platform_not_supported&#x60;): X comment polling is     off, so an X automation could never fire.  To continue into a specific workflow after the recipient taps a button, use &#x60;{\&quot;type\&quot;:\&quot;postback\&quot;,\&quot;title\&quot;:\&quot;Send it\&quot;,\&quot;payload\&quot;:\&quot;zernio:workflow:&lt;workflowId&gt;\&quot;}&#x60;. The target must be active and belong to the same account and profile. This also works for product-card buttons. The tap starts that workflow directly, without matching its keyword or first-message condition. A tap on a workflow that is waiting on &#x60;wait_for_reply&#x60; in that conversation answers that wait and resumes the run. A tap on a different active workflow starts it and exits the other live runs. Stale or invalid targets still do nothing. The initial comment DM alone does not start the workflow: the recipient must tap.  Triggers (&#x60;trigger&#x60;):   * &#x60;comment&#x60; (default): fires on keyword comments on a post or reel.   * &#x60;story_reply&#x60;: fires when someone replies to your Instagram story with a keyword,     and answers them with a DM. Set &#x60;platformPostId&#x60; to a story media id to scope to     one story, or omit it to match replies to any story.   * &#x60;live_comment&#x60; (Instagram only): fires on keyword comments made during one of     your Instagram live broadcasts and answers them with a private reply. &#x60;comment&#x60;     automations never fire on live comments, and &#x60;live_comment&#x60; ones never fire on     post comments. Meta only accepts the private reply while the broadcast is live.   * &#x60;story_mention&#x60; (Instagram only): fires when someone mentions your account in     their story, and answers them with a DM. A mention carries no text and Meta does     not identify the story, so &#x60;keywords&#x60; must be empty and &#x60;platformPostId&#x60; omitted.  Comments on Instagram and Facebook arrive by webhook. Every 10 minutes Zernio also reads the latest comments and replies back (the bound post, or the 5 newest posts for an account-wide automation, up to 20 Graph reads per account per run; a post not fully read is picked up again on the next run) and runs any comment the webhook did not deliver, so a dropped webhook still fires. A comment is answered at most once whichever path sees it first.  Targeting (comment trigger):   * Per-post: set &#x60;platformPostId&#x60; to scope to one specific post (only one active     per-post automation is allowed per post).   * Account-wide (\&quot;any post\&quot;): omit &#x60;platformPostId&#x60; (and &#x60;postId&#x60;). The automation     evaluates every comment on every post on the account. You can stack unlimited     account-wide automations, each with its own keyword set, and they all run     independently. Per-post automations take priority on their post.  Audience (&#x60;audience&#x60;, Instagram only): restrict the automation to followers or non-followers, and/or to accounts above a follower count. Instagram only reveals the follow relationship for people who have messaged the account, so &#x60;audience.whenUnknown&#x60; decides what happens for everyone else - including &#x60;verify&#x60;, which sends a one-tap confirmation DM (&#x60;followGate&#x60;) and then delivers the real DM automatically. People we already know follow you skip the tap entirely. Set &#x60;audience.tapToUnlock: true&#x60; instead to send that button DM to every commenter and deliver the real DM on the tap with no follow check.  Set &#x60;alsoMatchInDms: true&#x60; on a &#x60;comment&#x60; automation to also answer people who send a keyword as a direct message instead of commenting it. One automation then covers both doors, and each door is deduplicated separately (someone who already got the DM from their comment still gets it if they later DM the keyword). Requires at least one keyword.  Links in the DM&#39;s buttons can be click-tracked (&#x60;linkTracking&#x60;, on by default) and clickers optionally tagged (&#x60;clickTag&#x60;) for segmentation. Stats returned include delivered, read, and link clicks.  Personalisation: &#x60;{{first_name}}&#x60;, &#x60;{{name}}&#x60; and &#x60;{{username}}&#x60; in &#x60;dmMessage&#x60;, &#x60;commentReply&#x60;, their variations and button titles resolve from the commenter. &#x60;{{first_name}}&#x60; is the first word of the display name and &#x60;{{name}}&#x60; the display name; when the platform gives no display name both fall back to the platform username (unless it is all digits). &#x60;{{username}}&#x60; is the platform username. A value still unknown resolves to an empty string and the space before it is dropped.  Behaviour: &#x60;repeatPolicy&#x60; decides whether a person can get the DM again, &#x60;dedupeSameTextHours&#x60; stops two automations sending the same text to one person, &#x60;publicReplyPolicy&#x60; decides whether the public reply waits for the DM, and &#x60;actions&#x60; likes or hides the matched comment. 
     # @param create_comment_automation_request [CreateCommentAutomationRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(CreateCommentAutomation200Response, Integer, Hash)>] CreateCommentAutomation200Response data, response status code and response headers

data/lib/zernio-sdk/api/comments_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0
@@ -21,7 +21,7 @@ module Zernio
     end
     # Delete comment
     # Delete a comment on a post. Supported by Facebook, Instagram, Threads, LinkedIn, Reddit, Bluesky, X (Twitter), YouTube, and TikTok (accounts connected through the TikTok for Business app). Not supported on Google Business (reviews only). Requires accountId and commentId query parameters. 
-    # @param post_id [String] Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID.
+    # @param post_id [String] Zernio post ID or platform-specific post ID. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>); a bare number is read as an activity id (urn:li:activity:<n>).
     # @param account_id [String] 
     # @param comment_id [String] For LinkedIn, accepts either the numeric comment ID or the composite comment URN returned by the comments listing (e.g. urn:li:comment:(threadUrn,id))
     # @param [Hash] opts the optional parameters
@@ -33,7 +33,7 @@ module Zernio
 
     # Delete comment
     # Delete a comment on a post. Supported by Facebook, Instagram, Threads, LinkedIn, Reddit, Bluesky, X (Twitter), YouTube, and TikTok (accounts connected through the TikTok for Business app). Not supported on Google Business (reviews only). Requires accountId and commentId query parameters. 
-    # @param post_id [String] Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID.
+    # @param post_id [String] Zernio post ID or platform-specific post ID. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>); a bare number is read as an activity id (urn:li:activity:<n>).
     # @param account_id [String] 
     # @param comment_id [String] For LinkedIn, accepts either the numeric comment ID or the composite comment URN returned by the comments listing (e.g. urn:li:comment:(threadUrn,id))
     # @param [Hash] opts the optional parameters
@@ -178,7 +178,7 @@ module Zernio
 
     # Get post comments
     # Fetch comments for a specific post. Requires accountId query parameter.  Pass `commentId` (Facebook, Instagram, Reddit, TikTok) to fetch replies to a specific comment instead of the post's top-level comments. Facebook, Instagram and TikTok return the comment's replies, paged by `limit`/`cursor`; Reddit returns the focused comment thread instead. On Facebook and Instagram the requested comment itself comes back in the top-level `comment` field.  On Facebook, passing a COMMENT id as `postId` (instead of using `commentId`) is also supported for backwards compatibility and returns that comment's replies the same way. Prefer `commentId` for new integrations; it also works on Instagram, which rejects a comment id passed as `postId`. YouTube does not support either form, `postId` must be a video id.  Responses are cached for up to 10 minutes, so a page may lag new comments by that window. Do not poll this endpoint for real-time updates: subscribe to the `comment.received` webhook, which delivers new comments as they arrive. Your own writes (creating, replying to, or deleting a comment) refresh the cache immediately.  TikTok is served for accounts connected through the TikTok for Business app: `postId` is the TikTok video id, each top-level comment carries up to three inline replies, and `commentId` pages the full reply list of one comment. Developer-app TikTok accounts return 400 with code `PLATFORM_LIMITATION`.  On X (Twitter), when `postId` is itself a reply rather than the thread's root post, only replies to that specific post are returned, not the whole conversation thread.  Hidden comments: Facebook Pages and Instagram accounts connected through Instagram Login return them with `isHidden: true`. Instagram accounts connected through Facebook Login do not return them at all (Meta omits them, together with their replies), so a hidden comment and a deleted one look the same on this read. 
-    # @param post_id [String] Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook, a comment ID is also accepted here and returns that comment's replies, kept for backwards compatibility; prefer the `commentId` query parameter, which also works on Instagram.
+    # @param post_id [String] Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>). A bare number is read as an activity id (urn:li:activity:<n>, the number in a linkedin.com/feed/update URL); a share or ugcPost number passed bare returns an empty list. On Facebook, a comment ID is also accepted here and returns that comment's replies, kept for backwards compatibility; prefer the `commentId` query parameter, which also works on Instagram.
     # @param account_id [String] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :subreddit (Reddit only) Subreddit name
@@ -193,7 +193,7 @@ module Zernio
 
     # Get post comments
     # Fetch comments for a specific post. Requires accountId query parameter.  Pass `commentId` (Facebook, Instagram, Reddit, TikTok) to fetch replies to a specific comment instead of the post's top-level comments. Facebook, Instagram and TikTok return the comment's replies, paged by `limit`/`cursor`; Reddit returns the focused comment thread instead. On Facebook and Instagram the requested comment itself comes back in the top-level `comment` field.  On Facebook, passing a COMMENT id as `postId` (instead of using `commentId`) is also supported for backwards compatibility and returns that comment's replies the same way. Prefer `commentId` for new integrations; it also works on Instagram, which rejects a comment id passed as `postId`. YouTube does not support either form, `postId` must be a video id.  Responses are cached for up to 10 minutes, so a page may lag new comments by that window. Do not poll this endpoint for real-time updates: subscribe to the `comment.received` webhook, which delivers new comments as they arrive. Your own writes (creating, replying to, or deleting a comment) refresh the cache immediately.  TikTok is served for accounts connected through the TikTok for Business app: `postId` is the TikTok video id, each top-level comment carries up to three inline replies, and `commentId` pages the full reply list of one comment. Developer-app TikTok accounts return 400 with code `PLATFORM_LIMITATION`.  On X (Twitter), when `postId` is itself a reply rather than the thread's root post, only replies to that specific post are returned, not the whole conversation thread.  Hidden comments: Facebook Pages and Instagram accounts connected through Instagram Login return them with `isHidden: true`. Instagram accounts connected through Facebook Login do not return them at all (Meta omits them, together with their replies), so a hidden comment and a deleted one look the same on this read. 
-    # @param post_id [String] Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook, a comment ID is also accepted here and returns that comment's replies, kept for backwards compatibility; prefer the `commentId` query parameter, which also works on Instagram.
+    # @param post_id [String] Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>). A bare number is read as an activity id (urn:li:activity:<n>, the number in a linkedin.com/feed/update URL); a share or ugcPost number passed bare returns an empty list. On Facebook, a comment ID is also accepted here and returns that comment's replies, kept for backwards compatibility; prefer the `commentId` query parameter, which also works on Instagram.
     # @param account_id [String] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :subreddit (Reddit only) Subreddit name
@@ -690,7 +690,7 @@ module Zernio
 
     # Reply to comment
     # Post a reply to a post or specific comment. Requires accountId in request body.  **Idempotency:** send an `Idempotency-Key` header to make retries safe (e.g. after a client-side timeout where delivery is unknown): same key + same body replays the original response (with `Idempotent-Replayed: true`) instead of posting the comment a second time; same key + different body returns 422; a key still in flight returns 409. Keys are retained for 24 hours and are scoped to the credential and to this exact path, so reusing a key against a different postId returns 422 rather than replaying the other post's response.  Only successful (2xx) responses are stored for replay. If the request throws or returns a non-2xx status the key is released, so the header protects the \"request succeeded but the response was lost\" case. After an ambiguous failure (a 5xx or a network timeout) list the post's comments before retrying with the same key, and treat an empty result as inconclusive rather than as proof nothing was posted. 
-    # @param post_id [String] Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID.
+    # @param post_id [String] Zernio post ID or platform-specific post ID. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>); a bare number is read as an activity id (urn:li:activity:<n>).
     # @param reply_to_inbox_post_request [ReplyToInboxPostRequest] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key Optional client-generated unique key (e.g. a UUID) that makes retries safe. Same key + same body replays the original response; same key + different body → 422; key still processing → 409. A request cut off mid-handler (for example by a function timeout) can leave its key in progress, answering 409 until the key expires after 24 hours.
@@ -702,7 +702,7 @@ module Zernio
 
     # Reply to comment
     # Post a reply to a post or specific comment. Requires accountId in request body.  **Idempotency:** send an `Idempotency-Key` header to make retries safe (e.g. after a client-side timeout where delivery is unknown): same key + same body replays the original response (with `Idempotent-Replayed: true`) instead of posting the comment a second time; same key + different body returns 422; a key still in flight returns 409. Keys are retained for 24 hours and are scoped to the credential and to this exact path, so reusing a key against a different postId returns 422 rather than replaying the other post's response.  Only successful (2xx) responses are stored for replay. If the request throws or returns a non-2xx status the key is released, so the header protects the \"request succeeded but the response was lost\" case. After an ambiguous failure (a 5xx or a network timeout) list the post's comments before retrying with the same key, and treat an empty result as inconclusive rather than as proof nothing was posted. 
-    # @param post_id [String] Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID.
+    # @param post_id [String] Zernio post ID or platform-specific post ID. On LinkedIn, pass the post id exactly as the feed returns it (urn:li:share:<id> or urn:li:ugcPost:<id>); a bare number is read as an activity id (urn:li:activity:<n>).
     # @param reply_to_inbox_post_request [ReplyToInboxPostRequest] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key Optional client-generated unique key (e.g. a UUID) that makes retries safe. Same key + same body replays the original response; same key + different body → 422; key still processing → 409. A request cut off mid-handler (for example by a function timeout) can leave its key in progress, answering 409 until the key expires after 24 hours.

data/lib/zernio-sdk/api/commerce_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/connect_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/connected_apps_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/contacts_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/conversions_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/custom_fields_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0

data/lib/zernio-sdk/api/discord_api.rb

@@ -3,7 +3,7 @@
 
 #API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema).  Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id. 
 
-The version of the OpenAPI document: 1.285.1
+The version of the OpenAPI document: 1.286.2
 Contact: support@zernio.com
 Generated by: https://openapi-generator.tech
 Generator version: 7.19.0