zernio-sdk 0.0.784 → 0.0.786

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4470ecb712494d1056ef762bcf0a85305c48e1928372196591115eac3d02cd67
-  data.tar.gz: ba8ea05c5a462624a1f286c6cbff5c34d1a9537c48c00017be06d6a02ef05f00
+  metadata.gz: e70db227d77b0022f2479e97c89b45ae0fafd9de3a671089251aa2aea36db7db
+  data.tar.gz: c07a16a15d790252b2cffdffcc4e97ff13ad5ee2753cbb72d6323fbb46b498ca
 SHA512:
-  metadata.gz: aa3229a577409d0ac61c2a204dac8bc7bf75a2267a8ccd70cbda1d87180de3a0328364a65e5cab8f8152e7b85df2fe58efcd00aba440b0dff17da0bcd1bb2066
-  data.tar.gz: ab3be7790e719007d42e18a7bbb09ecdeb1a0522559880a3d22202ac640ef0030196d5caee86536226d522ed056d4111a74e9bf8643a62a1d8177bd2a8d61766
+  metadata.gz: 8d341798bd632d644c9dcd9ddb3b990af1c26ac3025ed16a8727e0a1e9d03e8d31dd39eaad6ae0ad8beafdd10cc07873d3f3dc9634a27fb27cf8369d98c6ba36
+  data.tar.gz: 1d5dd020710394301785a45933b011304dd615e43cb736404e2f071f491e046c994330fa9161bc96ff8399c53df16ee8c1e4e64b0fbfafaacc34395e929ca2c2

data/docs/CommentsApi.md

@@ -552,11 +552,11 @@ end
 
 ## reply_to_inbox_post
 
-> <ReplyToInboxPost200Response> reply_to_inbox_post(post_id, reply_to_inbox_post_request)
+> <ReplyToInboxPost200Response> reply_to_inbox_post(post_id, reply_to_inbox_post_request, opts)
 
 Reply to comment
 
-Post a reply to a post or specific comment. Requires accountId in request body.
+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. 
 
 ### Examples
 
@@ -572,10 +572,13 @@ 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.
 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.
+}
 
 begin
   # Reply to comment
-  result = api_instance.reply_to_inbox_post(post_id, reply_to_inbox_post_request)
+  result = api_instance.reply_to_inbox_post(post_id, reply_to_inbox_post_request, opts)
   p result
 rescue Zernio::ApiError => e
   puts "Error when calling CommentsApi->reply_to_inbox_post: #{e}"
@@ -586,12 +589,12 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<ReplyToInboxPost200Response>, Integer, Hash)> reply_to_inbox_post_with_http_info(post_id, reply_to_inbox_post_request)
+> <Array(<ReplyToInboxPost200Response>, Integer, Hash)> reply_to_inbox_post_with_http_info(post_id, reply_to_inbox_post_request, opts)
 
 ```ruby
 begin
   # Reply to comment
-  data, status_code, headers = api_instance.reply_to_inbox_post_with_http_info(post_id, reply_to_inbox_post_request)
+  data, status_code, headers = api_instance.reply_to_inbox_post_with_http_info(post_id, reply_to_inbox_post_request, opts)
   p status_code # => 2xx
   p headers # => { ... }
   p data # => <ReplyToInboxPost200Response>
@@ -606,6 +609,7 @@ end
 | ---- | ---- | ----------- | ----- |
 | **post_id** | **String** | Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID. |  |
 | **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. | [optional] |
 
 ### Return type
 

data/docs/ReviewsApi.md

@@ -171,11 +171,11 @@ end
 
 ## reply_to_inbox_review
 
-> <ReplyToInboxReview200Response> reply_to_inbox_review(review_id, reply_to_inbox_review_request)
+> <ReplyToInboxReview200Response> reply_to_inbox_review(review_id, reply_to_inbox_review_request, opts)
 
 Reply to review
 
-Post a reply to a review. Requires accountId in request body.
+Post a reply to a review. 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 sending the reply to the platform again; 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 reviewId returns 422 rather than replaying the other review'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) fetch the review before retrying with the same key, and treat a missing reply as inconclusive rather than as proof nothing was sent. 
 
 ### Examples
 
@@ -191,10 +191,13 @@ end
 api_instance = Zernio::ReviewsApi.new
 review_id = 'review_id_example' # String | Review ID (URL-encoded for Google Business)
 reply_to_inbox_review_request = Zernio::ReplyToInboxReviewRequest.new({account_id: 'account_id_example', message: 'message_example'}) # ReplyToInboxReviewRequest | 
+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.
+}
 
 begin
   # Reply to review
-  result = api_instance.reply_to_inbox_review(review_id, reply_to_inbox_review_request)
+  result = api_instance.reply_to_inbox_review(review_id, reply_to_inbox_review_request, opts)
   p result
 rescue Zernio::ApiError => e
   puts "Error when calling ReviewsApi->reply_to_inbox_review: #{e}"
@@ -205,12 +208,12 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<ReplyToInboxReview200Response>, Integer, Hash)> reply_to_inbox_review_with_http_info(review_id, reply_to_inbox_review_request)
+> <Array(<ReplyToInboxReview200Response>, Integer, Hash)> reply_to_inbox_review_with_http_info(review_id, reply_to_inbox_review_request, opts)
 
 ```ruby
 begin
   # Reply to review
-  data, status_code, headers = api_instance.reply_to_inbox_review_with_http_info(review_id, reply_to_inbox_review_request)
+  data, status_code, headers = api_instance.reply_to_inbox_review_with_http_info(review_id, reply_to_inbox_review_request, opts)
   p status_code # => 2xx
   p headers # => { ... }
   p data # => <ReplyToInboxReview200Response>
@@ -225,6 +228,7 @@ end
 | ---- | ---- | ----------- | ----- |
 | **review_id** | **String** | Review ID (URL-encoded for Google Business) |  |
 | **reply_to_inbox_review_request** | [**ReplyToInboxReviewRequest**](ReplyToInboxReviewRequest.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. | [optional] |
 
 ### Return type
 

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

@@ -609,10 +609,11 @@ module Zernio
     end
 
     # Reply to comment
-    # Post a reply to a post or specific comment. Requires accountId in request body.
+    # 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 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.
     # @return [ReplyToInboxPost200Response]
     def reply_to_inbox_post(post_id, reply_to_inbox_post_request, opts = {})
       data, _status_code, _headers = reply_to_inbox_post_with_http_info(post_id, reply_to_inbox_post_request, opts)
@@ -620,10 +621,11 @@ module Zernio
     end
 
     # Reply to comment
-    # Post a reply to a post or specific comment. Requires accountId in request body.
+    # 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 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.
     # @return [Array<(ReplyToInboxPost200Response, Integer, Hash)>] ReplyToInboxPost200Response data, response status code and response headers
     def reply_to_inbox_post_with_http_info(post_id, reply_to_inbox_post_request, opts = {})
       if @api_client.config.debugging
@@ -637,6 +639,10 @@ module Zernio
       if @api_client.config.client_side_validation && reply_to_inbox_post_request.nil?
         fail ArgumentError, "Missing the required parameter 'reply_to_inbox_post_request' when calling CommentsApi.reply_to_inbox_post"
       end
+      if @api_client.config.client_side_validation && !opts[:'idempotency_key'].nil? && opts[:'idempotency_key'].to_s.length > 255
+        fail ArgumentError, 'invalid value for "opts[:"idempotency_key"]" when calling CommentsApi.reply_to_inbox_post, the character length must be smaller than or equal to 255.'
+      end
+
       # resource path
       local_var_path = '/v1/inbox/comments/{postId}'.sub('{' + 'postId' + '}', CGI.escape(post_id.to_s))
 
@@ -652,6 +658,7 @@ module Zernio
       if !content_type.nil?
           header_params['Content-Type'] = content_type
       end
+      header_params[:'Idempotency-Key'] = opts[:'idempotency_key'] if !opts[:'idempotency_key'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}

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

@@ -217,10 +217,11 @@ module Zernio
     end
 
     # Reply to review
-    # Post a reply to a review. Requires accountId in request body.
+    # Post a reply to a review. 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 sending the reply to the platform again; 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 reviewId returns 422 rather than replaying the other review'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) fetch the review before retrying with the same key, and treat a missing reply as inconclusive rather than as proof nothing was sent. 
     # @param review_id [String] Review ID (URL-encoded for Google Business)
     # @param reply_to_inbox_review_request [ReplyToInboxReviewRequest] 
     # @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.
     # @return [ReplyToInboxReview200Response]
     def reply_to_inbox_review(review_id, reply_to_inbox_review_request, opts = {})
       data, _status_code, _headers = reply_to_inbox_review_with_http_info(review_id, reply_to_inbox_review_request, opts)
@@ -228,10 +229,11 @@ module Zernio
     end
 
     # Reply to review
-    # Post a reply to a review. Requires accountId in request body.
+    # Post a reply to a review. 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 sending the reply to the platform again; 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 reviewId returns 422 rather than replaying the other review'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) fetch the review before retrying with the same key, and treat a missing reply as inconclusive rather than as proof nothing was sent. 
     # @param review_id [String] Review ID (URL-encoded for Google Business)
     # @param reply_to_inbox_review_request [ReplyToInboxReviewRequest] 
     # @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.
     # @return [Array<(ReplyToInboxReview200Response, Integer, Hash)>] ReplyToInboxReview200Response data, response status code and response headers
     def reply_to_inbox_review_with_http_info(review_id, reply_to_inbox_review_request, opts = {})
       if @api_client.config.debugging
@@ -245,6 +247,10 @@ module Zernio
       if @api_client.config.client_side_validation && reply_to_inbox_review_request.nil?
         fail ArgumentError, "Missing the required parameter 'reply_to_inbox_review_request' when calling ReviewsApi.reply_to_inbox_review"
       end
+      if @api_client.config.client_side_validation && !opts[:'idempotency_key'].nil? && opts[:'idempotency_key'].to_s.length > 255
+        fail ArgumentError, 'invalid value for "opts[:"idempotency_key"]" when calling ReviewsApi.reply_to_inbox_review, the character length must be smaller than or equal to 255.'
+      end
+
       # resource path
       local_var_path = '/v1/inbox/reviews/{reviewId}/reply'.sub('{' + 'reviewId' + '}', CGI.escape(review_id.to_s))
 
@@ -260,6 +266,7 @@ module Zernio
       if !content_type.nil?
           header_params['Content-Type'] = content_type
       end
+      header_params[:'Idempotency-Key'] = opts[:'idempotency_key'] if !opts[:'idempotency_key'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}

data/lib/zernio-sdk/version.rb

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

data/openapi.yaml

@@ -546,7 +546,7 @@ components:
     IdempotencyKeyInFlight:
       description: Same Idempotency-Key still processing; retry after a short backoff
     IdempotencyKeyReused:
-      description: Idempotency-Key reused with a different body
+      description: Idempotency-Key reused with a different request
     BadRequest:
       description: Invalid request
       content:
@@ -28262,7 +28262,24 @@ paths:
       x-resource-group: "engagement"
       operationId: replyToInboxPost
       summary: Reply to comment
-      description: Post a reply to a post or specific comment. Requires accountId in request body.
+      description: |
+        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.
       tags: [Comments]
       security: [{ bearerAuth: [] }]
       parameters:
@@ -28271,6 +28288,7 @@ paths:
           required: true
           description: Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID.
           schema: { type: string }
+        - $ref: '#/components/parameters/IdempotencyKeyHeader'
       requestBody:
         required: true
         content:
@@ -28309,6 +28327,8 @@ paths:
         '401': { $ref: '#/components/responses/Unauthorized' }
         '403':
           description: 'Inbox addon required, or the connected account is not permitted to comment on this post on the platform (code platform_api_error, type platform_error)'
+        '409': { $ref: '#/components/responses/IdempotencyKeyInFlight' }
+        '422': { $ref: '#/components/responses/IdempotencyKeyReused' }
         '429': { $ref: '#/components/responses/RateLimited' }
         '502':
           description: 'Upstream platform error (code platform_api_error, type platform_error)'
@@ -29684,7 +29704,24 @@ paths:
       x-resource-group: "engagement"
       operationId: replyToInboxReview
       summary: Reply to review
-      description: Post a reply to a review. Requires accountId in request body.
+      description: |
+        Post a reply to a review. 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 sending the reply to the platform again; 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 reviewId returns 422 rather than
+        replaying the other review'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) fetch the review before
+        retrying with the same key, and treat a missing reply as inconclusive
+        rather than as proof nothing was sent.
       tags: [Reviews]
       security: [{ bearerAuth: [] }]
       parameters:
@@ -29693,6 +29730,7 @@ paths:
           required: true
           schema: { type: string }
           description: Review ID (URL-encoded for Google Business)
+        - $ref: '#/components/parameters/IdempotencyKeyHeader'
       requestBody:
         required: true
         content:
@@ -29722,6 +29760,8 @@ paths:
         '401': { $ref: '#/components/responses/Unauthorized' }
         '403':
           description: Inbox addon required
+        '409': { $ref: '#/components/responses/IdempotencyKeyInFlight' }
+        '422': { $ref: '#/components/responses/IdempotencyKeyReused' }
     delete:
       x-resource-group: "engagement"
       operationId: deleteInboxReviewReply

data/spec/api/comments_api_spec.rb

@@ -140,10 +140,11 @@ describe 'CommentsApi' do
 
   # unit tests for reply_to_inbox_post
   # Reply to comment
-  # Post a reply to a post or specific comment. Requires accountId in request body.
+  # 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 Zernio post ID or platform-specific post ID. LinkedIn third-party posts accept full activity URN or numeric ID.
   # @param reply_to_inbox_post_request 
   # @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.
   # @return [ReplyToInboxPost200Response]
   describe 'reply_to_inbox_post test' do
     it 'should work' do

data/spec/api/reviews_api_spec.rb

@@ -68,10 +68,11 @@ describe 'ReviewsApi' do
 
   # unit tests for reply_to_inbox_review
   # Reply to review
-  # Post a reply to a review. Requires accountId in request body.
+  # Post a reply to a review. 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 sending the reply to the platform again; 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 reviewId returns 422 rather than replaying the other review'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) fetch the review before retrying with the same key, and treat a missing reply as inconclusive rather than as proof nothing was sent. 
   # @param review_id Review ID (URL-encoded for Google Business)
   # @param reply_to_inbox_review_request 
   # @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.
   # @return [ReplyToInboxReview200Response]
   describe 'reply_to_inbox_review test' do
     it 'should work' do

metadata

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