late-sdk 0.0.695 → 0.0.697

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 333c877a4f531f235402f52f9e5b46407134e91e15ea59904eb00446704e8ffe
-  data.tar.gz: 2f91decb5e0e51b411126994a70545a6a445c645a44d61aa19ffaf4dcdfc3f90
+  metadata.gz: b9fb7862bf09ea4b3a1750659a8875dc2ae8baff5859afcff3a9a6dd3d0f65d3
+  data.tar.gz: d6c5bcd0de1ac34353c3d25e7e0f07ef956e782cdd4d378879ae1863e99725c2
 SHA512:
-  metadata.gz: a297b76f7e3eececf46d001f0659b9e3d09c854d78f10f3f8ab5fa8c37829ef78c4990b1581901ad54e3ced292772e3952ad6904017237f3064f582d6ea05797
-  data.tar.gz: 5adc7ecddaf704481e3be52353bd658b62168679b2c82043d186f2812b04a7ea072fa508dd6266b5c018d7662afb053887f92d2ed061c0b92fba75ad6c978c7f
+  metadata.gz: b2fdfcd4da7b34eb660a467910a951a119da56182efea8f8338d2504e30793ba810a4715045740b3d6f91c8ce69cd25da795307156f34af8ac0398b15c6c49f7
+  data.tar.gz: e9b01a21a98bc508fb69d093e13303094f0369c503bf3309ee8b7707fab98d9d40207029f15c9f8ea6122b57955dccfbcac3546f7489387cd492934815d8b349

data/docs/ConnectApi.md

@@ -713,7 +713,7 @@ end
 
 api_instance = Zernio::ConnectApi.new
 platform = 'facebook' # String | Social media platform to connect
-profile_id = 'profile_id_example' # String | Your Zernio profile ID (get from /v1/profiles)
+profile_id = 'profile_id_example' # String | Your Zernio profile ID (get from /v1/profiles). For WhatsApp, a Zernio-provisioned number can only be connected on the profile it was provisioned to; connecting from any other profile is rejected with a 409.
 opts = {
   redirect_url: 'redirect_url_example', # String | Your custom redirect URL after connection completes. Accepts an http(s) URL, a custom app scheme for mobile deeplinks (e.g. myapp://callback), or a relative path. Result params are appended with the URL API, so an existing query string is preserved. Standard mode appends connected={platform}&profileId=X&accountId=Y&username=Z. Headless mode appends OAuth data params for platforms requiring selection (e.g. LinkedIn orgs, Facebook pages). If no selection is needed, the account is created directly and the redirect includes accountId.
   headless: true # Boolean | When true, the user is redirected to your redirect_url with raw OAuth data (code, state) instead of Zernio's default account selection UI. Use this to build a custom connect experience.
@@ -751,7 +751,7 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **platform** | **String** | Social media platform to connect |  |
-| **profile_id** | **String** | Your Zernio profile ID (get from /v1/profiles) |  |
+| **profile_id** | **String** | Your Zernio profile ID (get from /v1/profiles). For WhatsApp, a Zernio-provisioned number can only be connected on the profile it was provisioned to; connecting from any other profile is rejected with a 409. |  |
 | **redirect_url** | **String** | Your custom redirect URL after connection completes. Accepts an http(s) URL, a custom app scheme for mobile deeplinks (e.g. myapp://callback), or a relative path. Result params are appended with the URL API, so an existing query string is preserved. Standard mode appends connected={platform}&profileId=X&accountId=Y&username=Z. Headless mode appends OAuth data params for platforms requiring selection (e.g. LinkedIn orgs, Facebook pages). If no selection is needed, the account is created directly and the redirect includes accountId. | [optional] |
 | **headless** | **Boolean** | When true, the user is redirected to your redirect_url with raw OAuth data (code, state) instead of Zernio's default account selection UI. Use this to build a custom connect experience. | [optional][default to false] |
 

data/docs/WhatsAppPhoneNumbersApi.md

@@ -589,7 +589,7 @@ This endpoint does not need any parameter.
 
 Move a number to another profile
 
-Move a provisioned number to a different profile.  A number is not a single record. Alongside the number itself there are hidden telephony owner accounts (platform `phone`, plus `sms` when SMS is enabled) and, once WhatsApp is connected, the `whatsapp` account. They all carry a profileId and this endpoint moves them together.  Use this instead of `PATCH /v1/accounts/{accountId}`: that one moves the social account only and leaves the number itself pinned to its original profile, which splits the number across two profiles. Connecting a provisioned number always places it on the profile the NUMBER is on, so a `profileId` passed to `GET /v1/connect/whatsapp` cannot re-home it and a later reconnect pulls the account back. This endpoint is how you re-home it.  `id` is the number record id from `GET /v1/phone-numbers`, not an account id.  A profile holds at most one account per platform, so the destination must be free of every platform this number occupies. 
+Move a provisioned number to a different profile.  A number is not a single record. Alongside the number itself there are hidden telephony owner accounts (platform `phone`, plus `sms` when SMS is enabled) and, once WhatsApp is connected, the `whatsapp` account. They all carry a profileId and this endpoint moves them together.  Use this instead of `PATCH /v1/accounts/{accountId}`: that one moves the social account only and leaves the number itself pinned to its original profile, which splits the number across two profiles. Connecting a Zernio-provisioned number from any profile but its own is rejected with a `409` (`WHATSAPP_NUMBER_PINNED_TO_PROFILE`). This endpoint is how you re-home the number first, so it can then be connected from the new profile.  `id` is the number record id from `GET /v1/phone-numbers`, not an account id.  A profile holds at most one account per platform, so the destination must be free of every platform this number occupies. 
 
 ### Examples
 

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

@@ -670,7 +670,7 @@ module Zernio
     # Get OAuth connect URL
     # Initiate an OAuth connection flow. Returns an authUrl to redirect the user to. Standard flow: Zernio hosts the selection UI, then redirects to your redirect_url. Headless mode (headless=true): user is redirected to your redirect_url with OAuth data for custom UI. Use the platform-specific selection endpoints to complete. 
     # @param platform [String] Social media platform to connect
-    # @param profile_id [String] Your Zernio profile ID (get from /v1/profiles)
+    # @param profile_id [String] Your Zernio profile ID (get from /v1/profiles). For WhatsApp, a Zernio-provisioned number can only be connected on the profile it was provisioned to; connecting from any other profile is rejected with a 409.
     # @param [Hash] opts the optional parameters
     # @option opts [String] :redirect_url Your custom redirect URL after connection completes. Accepts an http(s) URL, a custom app scheme for mobile deeplinks (e.g. myapp://callback), or a relative path. Result params are appended with the URL API, so an existing query string is preserved. Standard mode appends connected={platform}&profileId=X&accountId=Y&username=Z. Headless mode appends OAuth data params for platforms requiring selection (e.g. LinkedIn orgs, Facebook pages). If no selection is needed, the account is created directly and the redirect includes accountId.
     # @option opts [Boolean] :headless When true, the user is redirected to your redirect_url with raw OAuth data (code, state) instead of Zernio's default account selection UI. Use this to build a custom connect experience. (default to false)
@@ -683,7 +683,7 @@ module Zernio
     # Get OAuth connect URL
     # Initiate an OAuth connection flow. Returns an authUrl to redirect the user to. Standard flow: Zernio hosts the selection UI, then redirects to your redirect_url. Headless mode (headless=true): user is redirected to your redirect_url with OAuth data for custom UI. Use the platform-specific selection endpoints to complete. 
     # @param platform [String] Social media platform to connect
-    # @param profile_id [String] Your Zernio profile ID (get from /v1/profiles)
+    # @param profile_id [String] Your Zernio profile ID (get from /v1/profiles). For WhatsApp, a Zernio-provisioned number can only be connected on the profile it was provisioned to; connecting from any other profile is rejected with a 409.
     # @param [Hash] opts the optional parameters
     # @option opts [String] :redirect_url Your custom redirect URL after connection completes. Accepts an http(s) URL, a custom app scheme for mobile deeplinks (e.g. myapp://callback), or a relative path. Result params are appended with the URL API, so an existing query string is preserved. Standard mode appends connected={platform}&profileId=X&accountId=Y&username=Z. Headless mode appends OAuth data params for platforms requiring selection (e.g. LinkedIn orgs, Facebook pages). If no selection is needed, the account is created directly and the redirect includes accountId.
     # @option opts [Boolean] :headless When true, the user is redirected to your redirect_url with raw OAuth data (code, state) instead of Zernio's default account selection UI. Use this to build a custom connect experience. (default to false)

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

@@ -547,7 +547,7 @@ module Zernio
     end
 
     # Move a number to another profile
-    # Move a provisioned number to a different profile.  A number is not a single record. Alongside the number itself there are hidden telephony owner accounts (platform `phone`, plus `sms` when SMS is enabled) and, once WhatsApp is connected, the `whatsapp` account. They all carry a profileId and this endpoint moves them together.  Use this instead of `PATCH /v1/accounts/{accountId}`: that one moves the social account only and leaves the number itself pinned to its original profile, which splits the number across two profiles. Connecting a provisioned number always places it on the profile the NUMBER is on, so a `profileId` passed to `GET /v1/connect/whatsapp` cannot re-home it and a later reconnect pulls the account back. This endpoint is how you re-home it.  `id` is the number record id from `GET /v1/phone-numbers`, not an account id.  A profile holds at most one account per platform, so the destination must be free of every platform this number occupies. 
+    # Move a provisioned number to a different profile.  A number is not a single record. Alongside the number itself there are hidden telephony owner accounts (platform `phone`, plus `sms` when SMS is enabled) and, once WhatsApp is connected, the `whatsapp` account. They all carry a profileId and this endpoint moves them together.  Use this instead of `PATCH /v1/accounts/{accountId}`: that one moves the social account only and leaves the number itself pinned to its original profile, which splits the number across two profiles. Connecting a Zernio-provisioned number from any profile but its own is rejected with a `409` (`WHATSAPP_NUMBER_PINNED_TO_PROFILE`). This endpoint is how you re-home the number first, so it can then be connected from the new profile.  `id` is the number record id from `GET /v1/phone-numbers`, not an account id.  A profile holds at most one account per platform, so the destination must be free of every platform this number occupies. 
     # @param id [String] WhatsAppPhoneNumber id.
     # @param move_whats_app_number_to_profile_request [MoveWhatsAppNumberToProfileRequest] 
     # @param [Hash] opts the optional parameters
@@ -558,7 +558,7 @@ module Zernio
     end
 
     # Move a number to another profile
-    # Move a provisioned number to a different profile.  A number is not a single record. Alongside the number itself there are hidden telephony owner accounts (platform `phone`, plus `sms` when SMS is enabled) and, once WhatsApp is connected, the `whatsapp` account. They all carry a profileId and this endpoint moves them together.  Use this instead of `PATCH /v1/accounts/{accountId}`: that one moves the social account only and leaves the number itself pinned to its original profile, which splits the number across two profiles. Connecting a provisioned number always places it on the profile the NUMBER is on, so a `profileId` passed to `GET /v1/connect/whatsapp` cannot re-home it and a later reconnect pulls the account back. This endpoint is how you re-home it.  `id` is the number record id from `GET /v1/phone-numbers`, not an account id.  A profile holds at most one account per platform, so the destination must be free of every platform this number occupies. 
+    # Move a provisioned number to a different profile.  A number is not a single record. Alongside the number itself there are hidden telephony owner accounts (platform `phone`, plus `sms` when SMS is enabled) and, once WhatsApp is connected, the `whatsapp` account. They all carry a profileId and this endpoint moves them together.  Use this instead of `PATCH /v1/accounts/{accountId}`: that one moves the social account only and leaves the number itself pinned to its original profile, which splits the number across two profiles. Connecting a Zernio-provisioned number from any profile but its own is rejected with a `409` (`WHATSAPP_NUMBER_PINNED_TO_PROFILE`). This endpoint is how you re-home the number first, so it can then be connected from the new profile.  `id` is the number record id from `GET /v1/phone-numbers`, not an account id.  A profile holds at most one account per platform, so the destination must be free of every platform this number occupies. 
     # @param id [String] WhatsAppPhoneNumber id.
     # @param move_whats_app_number_to_profile_request [MoveWhatsAppNumberToProfileRequest] 
     # @param [Hash] opts the optional parameters

data/lib/zernio-sdk/version.rb

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

data/openapi.yaml

@@ -15696,7 +15696,7 @@ paths:
           in: query
           required: true
           schema: { type: string }
-          description: Your Zernio profile ID (get from /v1/profiles)
+          description: 'Your Zernio profile ID (get from /v1/profiles). For WhatsApp, a Zernio-provisioned number can only be connected on the profile it was provisioned to; connecting from any other profile is rejected with a 409.'
         - name: redirect_url
           in: query
           schema: { type: string, format: uri }
@@ -16315,7 +16315,7 @@ paths:
                   selectedLocationName: "My Coffee Shop"
                   selectedLocationId: "9281089117903930794"
         '400':
-          description: "Missing required fields (profileId, locationId, or tempToken)"
+          description: 'Missing required fields (profileId, locationId, or tempToken), or the provided accountId is not one of the accounts this connection manages'
         '401': { $ref: '#/components/responses/Unauthorized' }
         '403':
           description: User does not have access to the specified profile
@@ -19190,6 +19190,8 @@ paths:
           description: Invalid or expired access token
         '403':
           description: Profile limit exceeded for this plan
+        '409':
+          description: 'The phone number is a Zernio-provisioned number pinned to a different profile. Connect it from that profile, or move it first with PATCH /v1/whatsapp/phone-numbers/{id}/profile.'
 
   /v1/connect/whatsapp/select-phone-number:
     get:
@@ -19345,6 +19347,8 @@ paths:
           content:
             application/json:
               schema: { $ref: '#/components/schemas/ErrorResponse' }
+        '409':
+          description: 'The phone number is a Zernio-provisioned number pinned to a different profile. Connect it from that profile, or move it first with PATCH /v1/whatsapp/phone-numbers/{id}/profile.'
         '500':
           description: Failed to bind phone number
           content:
@@ -20840,7 +20844,7 @@ paths:
                 selectedLocation:
                   id: "12345678901234567890"
                   name: "My Business Location"
-        '400': { description: Location not in available locations }
+        '400': { description: 'Location not in available locations, or the provided googleAccountId is not one of the accounts this connection manages' }
         '401': { $ref: '#/components/responses/Unauthorized' }
         '404': { description: Account not found }
 
@@ -20920,7 +20924,7 @@ paths:
                   isActive: true
                   selectedLocationName: "Snap Fitness Dianella"
                   selectedLocationId: "12345678901234567890"
-        '400': { description: 'Invalid body, or selected location not found under the Google account' }
+        '400': { description: 'Invalid body, selected location not found under the Google account, or the provided googleAccountId is not one of the accounts this connection manages' }
         '401': { $ref: '#/components/responses/Unauthorized' }
         '403': { description: 'Payment required, or target profile exceeds plan limit' }
         '404': { description: Source Google Business account not found }
@@ -32289,9 +32293,9 @@ paths:
         Use this instead of `PATCH /v1/accounts/{accountId}`: that one moves the
         social account only and leaves the number itself pinned to its original
         profile, which splits the number across two profiles. Connecting a
-        provisioned number always places it on the profile the NUMBER is on, so a
-        `profileId` passed to `GET /v1/connect/whatsapp` cannot re-home it and a
-        later reconnect pulls the account back. This endpoint is how you re-home it.
+        Zernio-provisioned number from any profile but its own is rejected with a
+        `409` (`WHATSAPP_NUMBER_PINNED_TO_PROFILE`). This endpoint is how you
+        re-home the number first, so it can then be connected from the new profile.
 
         `id` is the number record id from `GET /v1/phone-numbers`, not an account id.
 

data/spec/api/connect_api_spec.rb

@@ -154,7 +154,7 @@ describe 'ConnectApi' do
   # Get OAuth connect URL
   # Initiate an OAuth connection flow. Returns an authUrl to redirect the user to. Standard flow: Zernio hosts the selection UI, then redirects to your redirect_url. Headless mode (headless=true): user is redirected to your redirect_url with OAuth data for custom UI. Use the platform-specific selection endpoints to complete. 
   # @param platform Social media platform to connect
-  # @param profile_id Your Zernio profile ID (get from /v1/profiles)
+  # @param profile_id Your Zernio profile ID (get from /v1/profiles). For WhatsApp, a Zernio-provisioned number can only be connected on the profile it was provisioned to; connecting from any other profile is rejected with a 409.
   # @param [Hash] opts the optional parameters
   # @option opts [String] :redirect_url Your custom redirect URL after connection completes. Accepts an http(s) URL, a custom app scheme for mobile deeplinks (e.g. myapp://callback), or a relative path. Result params are appended with the URL API, so an existing query string is preserved. Standard mode appends connected={platform}&profileId=X&accountId=Y&username=Z. Headless mode appends OAuth data params for platforms requiring selection (e.g. LinkedIn orgs, Facebook pages). If no selection is needed, the account is created directly and the redirect includes accountId.
   # @option opts [Boolean] :headless When true, the user is redirected to your redirect_url with raw OAuth data (code, state) instead of Zernio's default account selection UI. Use this to build a custom connect experience.

data/spec/api/whats_app_phone_numbers_api_spec.rb

@@ -133,7 +133,7 @@ describe 'WhatsAppPhoneNumbersApi' do
 
   # unit tests for move_whats_app_number_to_profile
   # Move a number to another profile
-  # Move a provisioned number to a different profile.  A number is not a single record. Alongside the number itself there are hidden telephony owner accounts (platform `phone`, plus `sms` when SMS is enabled) and, once WhatsApp is connected, the `whatsapp` account. They all carry a profileId and this endpoint moves them together.  Use this instead of `PATCH /v1/accounts/{accountId}`: that one moves the social account only and leaves the number itself pinned to its original profile, which splits the number across two profiles. Connecting a provisioned number always places it on the profile the NUMBER is on, so a `profileId` passed to `GET /v1/connect/whatsapp` cannot re-home it and a later reconnect pulls the account back. This endpoint is how you re-home it.  `id` is the number record id from `GET /v1/phone-numbers`, not an account id.  A profile holds at most one account per platform, so the destination must be free of every platform this number occupies. 
+  # Move a provisioned number to a different profile.  A number is not a single record. Alongside the number itself there are hidden telephony owner accounts (platform `phone`, plus `sms` when SMS is enabled) and, once WhatsApp is connected, the `whatsapp` account. They all carry a profileId and this endpoint moves them together.  Use this instead of `PATCH /v1/accounts/{accountId}`: that one moves the social account only and leaves the number itself pinned to its original profile, which splits the number across two profiles. Connecting a Zernio-provisioned number from any profile but its own is rejected with a `409` (`WHATSAPP_NUMBER_PINNED_TO_PROFILE`). This endpoint is how you re-home the number first, so it can then be connected from the new profile.  `id` is the number record id from `GET /v1/phone-numbers`, not an account id.  A profile holds at most one account per platform, so the destination must be free of every platform this number occupies. 
   # @param id WhatsAppPhoneNumber id.
   # @param move_whats_app_number_to_profile_request 
   # @param [Hash] opts the optional parameters

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: late-sdk
 version: !ruby/object:Gem::Version
-  version: 0.0.695
+  version: 0.0.697
 platform: ruby
 authors:
 - OpenAPI-Generator
@@ -5024,7 +5024,7 @@ files:
 - spec/models/you_tube_video_retention_response_retention_curve_inner_spec.rb
 - spec/models/you_tube_video_retention_response_spec.rb
 - spec/spec_helper.rb
-- zernio-sdk-0.0.695.gem
+- zernio-sdk-0.0.697.gem
 - zernio-sdk.gemspec
 homepage: https://openapi-generator.tech
 licenses: