zernio-sdk 0.0.829 → 0.0.831

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e928adf661198cd11d538892669a1091a9a6446c4f9ec8dbf863ea38be997258
-  data.tar.gz: 6428f93dc05fa0caf91c561c9f3a19600421dd464d6dca11a3cedc1ba7c4d15b
+  metadata.gz: 1566f198f77264c080c32c6f6d2b8a147e61a1a4c280d2d1400104fbcb045cd2
+  data.tar.gz: 026223a99d111867cd93fd8c84b9b45b79ec602873531b862ead083eb22fea2c
 SHA512:
-  metadata.gz: b0ea149f56866e68e3a1dbd73ed9fe948b009662ad8a09ba209cf898a77e86b4d4595366516878fb1fc60574cc311e11796c2b5512540e4489b01964fd2dc6c7
-  data.tar.gz: a141593090f2ec584a2c2f139ef6cf803bfd81a5b55171d1c4667173f4f6d9d7d348b066b11c5413362541593f7aa52544d1bb547e95aff2449ce84fd4a2ca2c
+  metadata.gz: 0b0de919da3bd72263676fd2c05882cab0a967cc50c30779caed0fa9fc59481eb1ca9976e2512d414da966ea0479149b59f16083bdcfaf5ecafa39b61105dd01
+  data.tar.gz: 9b498c98ba0f0ed0afec793c1f36edf26f01e8eb0ddba7d988b2df312aa6d681ad34eace60254f3fddf0c9d6f8039b5c14b92af15f64a42ea7f4974ad6fa5f4b

data/docs/MessagesApi.md

@@ -329,7 +329,7 @@ Zernio.configure do |config|
 end
 
 api_instance = Zernio::MessagesApi.new
-conversation_id = 'conversation_id_example' # String | The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+conversation_id = 'conversation_id_example' # String | Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
 account_id = 'account_id_example' # String | The social account ID
 
 begin
@@ -363,7 +363,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **conversation_id** | **String** | The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID. |  |
+| **conversation_id** | **String** | Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed. |  |
 | **account_id** | **String** | The social account ID |  |
 
 ### Return type
@@ -400,7 +400,7 @@ Zernio.configure do |config|
 end
 
 api_instance = Zernio::MessagesApi.new
-conversation_id = 'conversation_id_example' # String | The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+conversation_id = 'conversation_id_example' # String | Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
 account_id = 'account_id_example' # String | Social account ID
 opts = {
   limit: 56, # Integer | Number of messages to return per page. Default 100, max 100.
@@ -439,7 +439,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **conversation_id** | **String** | The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID. |  |
+| **conversation_id** | **String** | Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed. |  |
 | **account_id** | **String** | Social account ID |  |
 | **limit** | **Integer** | Number of messages to return per page. Default 100, max 100. | [optional][default to 100] |
 | **cursor** | **String** | Opaque pagination cursor. Pass `pagination.nextCursor` from a prior response verbatim: a cursor we cannot parse returns 400 rather than silently restarting from the first page. | [optional] |
@@ -1014,7 +1014,7 @@ Zernio.configure do |config|
 end
 
 api_instance = Zernio::MessagesApi.new
-conversation_id = 'conversation_id_example' # String | The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+conversation_id = 'conversation_id_example' # String | Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
 update_inbox_conversation_request = Zernio::UpdateInboxConversationRequest.new({account_id: 'account_id_example', status: 'active'}) # UpdateInboxConversationRequest | 
 
 begin
@@ -1048,7 +1048,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **conversation_id** | **String** | The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID. |  |
+| **conversation_id** | **String** | Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed. |  |
 | **update_inbox_conversation_request** | [**UpdateInboxConversationRequest**](UpdateInboxConversationRequest.md) |  |  |
 
 ### Return type

data/docs/TwitterPlatformData.md

@@ -10,7 +10,7 @@
 | **reply_settings** | **String** | Controls who can reply to the tweet. \"following\" allows only people you follow, \"mentionedUsers\" allows only mentioned users, \"subscribers\" allows only subscribers, \"verified\" allows only verified users. Omit for default (everyone can reply). For threads, applies to the first tweet only. Cannot be combined with replyToTweetId. | [optional] |
 | **thread_items** | [**Array<TwitterPlatformDataThreadItemsInner>**](TwitterPlatformDataThreadItemsInner.md) | Complete sequence of tweets in a thread. The first item becomes the root tweet, subsequent items are chained as replies. When threadItems is provided, the top-level content field is used only for display and search purposes, it is NOT published. You must include your first tweet as threadItems[0].  | [optional] |
 | **poll** | [**TwitterPlatformDataPoll**](TwitterPlatformDataPoll.md) |  | [optional] |
-| **long_video** | **Boolean** | Enable long video uploads (over 140 seconds) using amplify_video media category. Requires the connected X account to have an active X Premium subscription. When true, videos are uploaded with the amplify_video category which supports longer durations (up to 10 minutes via API). When false or omitted, the standard tweet_video category is used (140 second limit). Note that not all Premium accounts have API long-video access, as X may require separate allowlisting. | [optional][default to false] |
+| **long_video** | **Boolean** | Uploads the video with X's amplify_video media category instead of the standard tweet_video. Applied only when the connected X account has a paid X subscription; on other accounts the flag is accepted and ignored. It is not required to post long videos. The standard tweet_video path already publishes videos well past 140 seconds on free accounts, and maximum duration is set by X per account, not by Zernio. Zernio enforces only the 512 MB file-size limit. Some accounts additionally require X's long-video API allowlisting, without which X rejects an amplify_video upload. | [optional][default to false] |
 | **geo_restriction** | [**GeoRestriction**](GeoRestriction.md) |  | [optional] |
 | **paid_partnership** | **Boolean** | When true, the post is labeled by X as a paid partnership / paid promotion. For threads, applies to the root tweet only. Field availability may depend on your X API access tier. | [optional][default to false] |
 | **made_with_ai** | **Boolean** | When true, the post is labeled by X as containing AI-generated media. Per X, this label is for AI-generated media, not AI-written text. For threads, applies to the root tweet only. | [optional][default to false] |

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

@@ -325,7 +325,7 @@ module Zernio
 
     # Get conversation
     # Retrieve details and metadata for a specific conversation. Requires accountId query parameter.
-    # @param conversation_id [String] The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+    # @param conversation_id [String] Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
     # @param account_id [String] The social account ID
     # @param [Hash] opts the optional parameters
     # @return [GetInboxConversation200Response]
@@ -336,7 +336,7 @@ module Zernio
 
     # Get conversation
     # Retrieve details and metadata for a specific conversation. Requires accountId query parameter.
-    # @param conversation_id [String] The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+    # @param conversation_id [String] Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
     # @param account_id [String] The social account ID
     # @param [Hash] opts the optional parameters
     # @return [Array<(GetInboxConversation200Response, Integer, Hash)>] GetInboxConversation200Response data, response status code and response headers
@@ -395,7 +395,7 @@ module Zernio
 
     # List messages
     # Fetch messages for a specific conversation, with cursor-based pagination and ordering control.  Pagination: pass `pagination.nextCursor` from a prior response back as the `cursor` query param to fetch the next page. The cursor is opaque; do not parse or construct it client-side.  Sort order: defaults to `asc` (oldest first, chat style). For the \"show me the latest messages\" pattern, pass `?sortOrder=desc&limit=N`. Twitter, Instagram, Telegram, WhatsApp and Reddit honor the requested order from the local message store. For Facebook and Bluesky, the upstream APIs only return newest-first and have no order parameter — sort order is best-effort and only reverses items within a single page (pages still walk newest→oldest). The response field `sortOrderApplied` tells you what was actually applied.  Reddit threads are paginated client-side because Reddit's API has no per-thread cursor. Very long threads may be upstream-truncated by Reddit's inbox/sent windows (~100 most-recent items each); this is a Reddit platform limitation.  Instagram and Facebook conversations include history from before the account was connected, replayed from Meta. That replay covers the 500 most recent messages per conversation: a longer thread keeps its newest 500 and older messages are not retrievable. Messages that arrived after the account was connected are unaffected. Replayed messages are stored as already read and emit no webhooks.  Twitter/X limitation: X's encrypted \"X Chat\" messages are not accessible via the API. Conversations where the other participant uses encrypted X Chat may only show your outgoing messages. See the list conversations endpoint for more details.  This endpoint is read-only and does NOT mark messages as read or send read receipts. To mark a conversation read (and send WhatsApp blue ticks on eligible accounts), call `POST /v1/inbox/conversations/{conversationId}/read`. 
-    # @param conversation_id [String] The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+    # @param conversation_id [String] Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
     # @param account_id [String] Social account ID
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :limit Number of messages to return per page. Default 100, max 100. (default to 100)
@@ -409,7 +409,7 @@ module Zernio
 
     # List messages
     # Fetch messages for a specific conversation, with cursor-based pagination and ordering control.  Pagination: pass &#x60;pagination.nextCursor&#x60; from a prior response back as the &#x60;cursor&#x60; query param to fetch the next page. The cursor is opaque; do not parse or construct it client-side.  Sort order: defaults to &#x60;asc&#x60; (oldest first, chat style). For the \&quot;show me the latest messages\&quot; pattern, pass &#x60;?sortOrder&#x3D;desc&amp;limit&#x3D;N&#x60;. Twitter, Instagram, Telegram, WhatsApp and Reddit honor the requested order from the local message store. For Facebook and Bluesky, the upstream APIs only return newest-first and have no order parameter — sort order is best-effort and only reverses items within a single page (pages still walk newest→oldest). The response field &#x60;sortOrderApplied&#x60; tells you what was actually applied.  Reddit threads are paginated client-side because Reddit&#39;s API has no per-thread cursor. Very long threads may be upstream-truncated by Reddit&#39;s inbox/sent windows (~100 most-recent items each); this is a Reddit platform limitation.  Instagram and Facebook conversations include history from before the account was connected, replayed from Meta. That replay covers the 500 most recent messages per conversation: a longer thread keeps its newest 500 and older messages are not retrievable. Messages that arrived after the account was connected are unaffected. Replayed messages are stored as already read and emit no webhooks.  Twitter/X limitation: X&#39;s encrypted \&quot;X Chat\&quot; messages are not accessible via the API. Conversations where the other participant uses encrypted X Chat may only show your outgoing messages. See the list conversations endpoint for more details.  This endpoint is read-only and does NOT mark messages as read or send read receipts. To mark a conversation read (and send WhatsApp blue ticks on eligible accounts), call &#x60;POST /v1/inbox/conversations/{conversationId}/read&#x60;. 
-    # @param conversation_id [String] The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+    # @param conversation_id [String] Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
     # @param account_id [String] Social account ID
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :limit Number of messages to return per page. Default 100, max 100. (default to 100)
@@ -1088,7 +1088,7 @@ module Zernio
 
     # Update conversation status
     # Archive or activate a conversation. Requires accountId in request body.
-    # @param conversation_id [String] The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+    # @param conversation_id [String] Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
     # @param update_inbox_conversation_request [UpdateInboxConversationRequest] 
     # @param [Hash] opts the optional parameters
     # @return [UpdateInboxConversation200Response]
@@ -1099,7 +1099,7 @@ module Zernio
 
     # Update conversation status
     # Archive or activate a conversation. Requires accountId in request body.
-    # @param conversation_id [String] The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+    # @param conversation_id [String] Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
     # @param update_inbox_conversation_request [UpdateInboxConversationRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(UpdateInboxConversation200Response, Integer, Hash)>] UpdateInboxConversation200Response data, response status code and response headers

data/lib/zernio-sdk/models/twitter_platform_data.rb

@@ -32,7 +32,7 @@ module Zernio
 
     attr_accessor :poll
 
-    # Enable long video uploads (over 140 seconds) using amplify_video media category. Requires the connected X account to have an active X Premium subscription. When true, videos are uploaded with the amplify_video category which supports longer durations (up to 10 minutes via API). When false or omitted, the standard tweet_video category is used (140 second limit). Note that not all Premium accounts have API long-video access, as X may require separate allowlisting.
+    # Uploads the video with X's amplify_video media category instead of the standard tweet_video. Applied only when the connected X account has a paid X subscription; on other accounts the flag is accepted and ignored. It is not required to post long videos. The standard tweet_video path already publishes videos well past 140 seconds on free accounts, and maximum duration is set by X per account, not by Zernio. Zernio enforces only the 512 MB file-size limit. Some accounts additionally require X's long-video API allowlisting, without which X rejects an amplify_video upload.
     attr_accessor :long_video
 
     attr_accessor :geo_restriction

data/lib/zernio-sdk/version.rb

@@ -11,5 +11,5 @@ Generator version: 7.19.0
 =end
 
 module Zernio
-  VERSION = '0.0.829'
+  VERSION = '0.0.831'
 end

data/openapi.yaml

@@ -5611,7 +5611,7 @@ components:
         longVideo:
           type: boolean
           default: false
-          description: Enable long video uploads (over 140 seconds) using amplify_video media category. Requires the connected X account to have an active X Premium subscription. When true, videos are uploaded with the amplify_video category which supports longer durations (up to 10 minutes via API). When false or omitted, the standard tweet_video category is used (140 second limit). Note that not all Premium accounts have API long-video access, as X may require separate allowlisting.
+          description: Uploads the video with X's amplify_video media category instead of the standard tweet_video. Applied only when the connected X account has a paid X subscription; on other accounts the flag is accepted and ignored. It is not required to post long videos. The standard tweet_video path already publishes videos well past 140 seconds on free accounts, and maximum duration is set by X per account, not by Zernio. Zernio enforces only the 512 MB file-size limit. Some accounts additionally require X's long-video API allowlisting, without which X rejects an amplify_video upload.
         geoRestriction:
           $ref: '#/components/schemas/GeoRestriction'
         paidPartnership:
@@ -27032,7 +27032,7 @@ paths:
           in: path
           required: true
           schema: { type: string }
-          description: The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+          description: 'Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.'
         - name: accountId
           in: query
           required: true
@@ -27169,7 +27169,7 @@ paths:
           in: path
           required: true
           schema: { type: string }
-          description: The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+          description: 'Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.'
       requestBody:
         required: true
         content:
@@ -27249,7 +27249,7 @@ paths:
           in: path
           required: true
           schema: { type: string }
-          description: The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+          description: 'Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.'
         - name: accountId
           in: query
           required: true

data/spec/api/messages_api_spec.rb

@@ -89,7 +89,7 @@ describe 'MessagesApi' do
   # unit tests for get_inbox_conversation
   # Get conversation
   # Retrieve details and metadata for a specific conversation. Requires accountId query parameter.
-  # @param conversation_id The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+  # @param conversation_id Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
   # @param account_id The social account ID
   # @param [Hash] opts the optional parameters
   # @return [GetInboxConversation200Response]
@@ -102,7 +102,7 @@ describe 'MessagesApi' do
   # unit tests for get_inbox_conversation_messages
   # List messages
   # Fetch messages for a specific conversation, with cursor-based pagination and ordering control.  Pagination: pass `pagination.nextCursor` from a prior response back as the `cursor` query param to fetch the next page. The cursor is opaque; do not parse or construct it client-side.  Sort order: defaults to `asc` (oldest first, chat style). For the \"show me the latest messages\" pattern, pass `?sortOrder=desc&limit=N`. Twitter, Instagram, Telegram, WhatsApp and Reddit honor the requested order from the local message store. For Facebook and Bluesky, the upstream APIs only return newest-first and have no order parameter — sort order is best-effort and only reverses items within a single page (pages still walk newest→oldest). The response field `sortOrderApplied` tells you what was actually applied.  Reddit threads are paginated client-side because Reddit's API has no per-thread cursor. Very long threads may be upstream-truncated by Reddit's inbox/sent windows (~100 most-recent items each); this is a Reddit platform limitation.  Instagram and Facebook conversations include history from before the account was connected, replayed from Meta. That replay covers the 500 most recent messages per conversation: a longer thread keeps its newest 500 and older messages are not retrievable. Messages that arrived after the account was connected are unaffected. Replayed messages are stored as already read and emit no webhooks.  Twitter/X limitation: X's encrypted \"X Chat\" messages are not accessible via the API. Conversations where the other participant uses encrypted X Chat may only show your outgoing messages. See the list conversations endpoint for more details.  This endpoint is read-only and does NOT mark messages as read or send read receipts. To mark a conversation read (and send WhatsApp blue ticks on eligible accounts), call `POST /v1/inbox/conversations/{conversationId}/read`. 
-  # @param conversation_id The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+  # @param conversation_id Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
   # @param account_id Social account ID
   # @param [Hash] opts the optional parameters
   # @option opts [Integer] :limit Number of messages to return per page. Default 100, max 100.
@@ -224,7 +224,7 @@ describe 'MessagesApi' do
   # unit tests for update_inbox_conversation
   # Update conversation status
   # Archive or activate a conversation. Requires accountId in request body.
-  # @param conversation_id The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
+  # @param conversation_id Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.
   # @param update_inbox_conversation_request 
   # @param [Hash] opts the optional parameters
   # @return [UpdateInboxConversation200Response]

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: zernio-sdk
 version: !ruby/object:Gem::Version
-  version: 0.0.829
+  version: 0.0.831
 platform: ruby
 authors:
 - OpenAPI-Generator