late-sdk 0.0.588 → 0.0.590

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2e1980bae6a327e7d16f99258611067edd539e6c88a4b12c6991fe6eb6cd3320
-  data.tar.gz: d1aa23a6d257cb2efa1721c306ad70a7c08bc6c4d9de2278e7b40ef68c861bfc
+  metadata.gz: b815c925c44c9ff3251021fac31a4fb5b410ff7a611bea807430a28451225e12
+  data.tar.gz: 679bfd340c10f0207e1cc58b0efbbe087e49626343d90d0a28ab41d4070da63f
 SHA512:
-  metadata.gz: d8f79a5751e9fdd1a147eb6b5754fde83bf318eb3c08c724affcfe6b811d1cb1c90849b98a34f56a03167b2bad201819f16860bae7d0f9aa122b400d4dedf843
-  data.tar.gz: 933f6933a2c7efa3a39ff2208c35869db160b51d41b405824976fcf7d097616677874390e8b2d4122600fd36c9bce12e1be97fcd1397f1cc11444b5143af0d39
+  metadata.gz: 97c134c3e3f6df17aa1a4132eb63f6752785f058f0b3296eadf999fbceac8138df1dcca81884673ee244f50186139fa451171763c59b82caba6e7ce4069fad76
+  data.tar.gz: 82b05c40bc1af0dbeb43244b5a21117f0e6e92dfa71542788eb2ca16a75951e990fa6c9f2949212ecdd97b4f4cd427ecc9fb35bbca17e571e4df11572c1db3bf

data/README.md

@@ -425,8 +425,10 @@ Class | Method | HTTP request | Description
 *Zernio::SMSApi* | [**list_sms_registrations**](docs/SMSApi.md#list_sms_registrations) | **GET** /v1/sms/registrations | List carrier registrations
 *Zernio::SMSApi* | [**list_sms_sender_ids**](docs/SMSApi.md#list_sms_sender_ids) | **GET** /v1/sms/sender-ids | List alphanumeric sender IDs
 *Zernio::SMSApi* | [**lookup_sms_number**](docs/SMSApi.md#lookup_sms_number) | **GET** /v1/sms/lookup | Look up carrier + line type
+*Zernio::SMSApi* | [**preflight_sms_registration**](docs/SMSApi.md#preflight_sms_registration) | **POST** /v1/sms/registrations/preflight | Pre-check a carrier registration
 *Zernio::SMSApi* | [**request_sms_sender_id_limit_increase**](docs/SMSApi.md#request_sms_sender_id_limit_increase) | **POST** /v1/sms/sender-ids/limit-request | Request a higher sender ID daily limit
 *Zernio::SMSApi* | [**resend_sms_registration_otp**](docs/SMSApi.md#resend_sms_registration_otp) | **POST** /v1/sms/registrations/{id}/resend-otp | Re-send the sole-prop OTP
+*Zernio::SMSApi* | [**respond_to_sms_registration_review**](docs/SMSApi.md#respond_to_sms_registration_review) | **POST** /v1/sms/registrations/{id}/respond | Reply to a change request
 *Zernio::SMSApi* | [**reuse_sms_registration_for_number**](docs/SMSApi.md#reuse_sms_registration_for_number) | **POST** /v1/phone-numbers/{id}/sms/reuse-registration | Add number to SMS registration
 *Zernio::SMSApi* | [**send_sms**](docs/SMSApi.md#send_sms) | **POST** /v1/sms/messages | Send an SMS/MMS
 *Zernio::SMSApi* | [**share_sms_registration**](docs/SMSApi.md#share_sms_registration) | **POST** /v1/sms/registrations/share | Create a registration share link
@@ -1561,6 +1563,10 @@ Class | Method | HTTP request | Description
  - [Zernio::PostUpdateResponse](docs/PostUpdateResponse.md)
  - [Zernio::PostUserId](docs/PostUserId.md)
  - [Zernio::PostsListResponse](docs/PostsListResponse.md)
+ - [Zernio::PreflightSmsRegistration200Response](docs/PreflightSmsRegistration200Response.md)
+ - [Zernio::PreflightSmsRegistration200ResponseAdvisoriesInner](docs/PreflightSmsRegistration200ResponseAdvisoriesInner.md)
+ - [Zernio::PreflightSmsRegistration200ResponseComposed](docs/PreflightSmsRegistration200ResponseComposed.md)
+ - [Zernio::PreflightSmsRegistrationRequest](docs/PreflightSmsRegistrationRequest.md)
  - [Zernio::Profile](docs/Profile.md)
  - [Zernio::ProfileCreateResponse](docs/ProfileCreateResponse.md)
  - [Zernio::ProfileDeleteResponse](docs/ProfileDeleteResponse.md)
@@ -1621,6 +1627,8 @@ Class | Method | HTTP request | Description
  - [Zernio::RespondToPhoneNumberReviewer200Response](docs/RespondToPhoneNumberReviewer200Response.md)
  - [Zernio::RespondToPhoneNumberReviewerRequest](docs/RespondToPhoneNumberReviewerRequest.md)
  - [Zernio::RespondToPhoneNumberReviewerRequestDocumentsInner](docs/RespondToPhoneNumberReviewerRequestDocumentsInner.md)
+ - [Zernio::RespondToSmsRegistrationReview200Response](docs/RespondToSmsRegistrationReview200Response.md)
+ - [Zernio::RespondToSmsRegistrationReviewRequest](docs/RespondToSmsRegistrationReviewRequest.md)
  - [Zernio::RestoreWorkflowVersion200Response](docs/RestoreWorkflowVersion200Response.md)
  - [Zernio::RestoreWorkflowVersion200ResponseWorkflow](docs/RestoreWorkflowVersion200ResponseWorkflow.md)
  - [Zernio::RetweetPost200Response](docs/RetweetPost200Response.md)

data/docs/CreateStandaloneAdRequest.md

@@ -11,7 +11,7 @@
 | **ad_set_name** | **String** | Meta only. Exact ad set name. Overrides the default `<name> - Ad Set`. (For per-ad names on the multi-creative shape, set `name` on each `creatives[]` entry.) | [optional] |
 | **ad_name** | **String** | Meta only. Exact ad name (the single-creative ad object's name). Overrides the default, which is `name`. (For per-ad names on the multi-creative shape, set `name` on each `creatives[]` entry instead.) | [optional] |
 | **tracking** | [**CreateStandaloneAdRequestTracking**](CreateStandaloneAdRequestTracking.md) |  | [optional] |
-| **goal** | **String** | Required on legacy and multi-creative shapes; the attach shape inherits it from the ad set. Available goals vary by platform.  **Meta** - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL. - `lead_conversion`: OUTCOME_LEADS optimizing website pixel leads. Same pixel and event fields, but with a leads-class event such as LEAD, SUBMIT_APPLICATION, SCHEDULE or CONTACT. Meta gates conversion events by objective, so leads-class events are rejected under `conversions`. - `lead_generation`: OUTCOME_LEADS with instant forms. Requires `leadGenFormId`. `promotedObject.pageId` is optional and auto-filled from the connected Page. - `app_promotion`: requires `promotedObject.applicationId` and `promotedObject.objectStoreUrl`. - `catalog_sales`: Advantage+ catalog ads, for example vehicle inventory. Requires `promotedObject.productSetId`, `promotedObject.pixelId` and `promotedObject.customEventType`. Builds a catalog TEMPLATE creative from the copy fields, which may carry template tags like {{product.name}} or {{vehicle.make}}. No imageUrl or video is sent; Meta renders the visuals per catalog item. Discover catalogs via GET /v1/ads/catalogs and product sets via GET /v1/ads/catalogs/{catalogId}/product-sets. Single shape only, no creatives[], adSetId, dynamicCreative or placementAssets.  **TikTok** - `conversions`: website-conversion ad group. Requires `promotedObject.pixelId`, your TikTok Pixel ID. Accepts an optional `promotedObject.customEventType` with a TikTok optimization_event code your pixel tracks (newer pixels use e.g. SHOPPING for purchase events; legacy pixels use ON_WEB_ORDER, INITIATE_ORDER, ON_WEB_REGISTER or FORM). To inherit pixel and event from an existing ad group, pass `adSetId` instead.  **LinkedIn** - `engagement`, `traffic`, `awareness` and `video_views` create standalone Direct Sponsored Content ads. `traffic` requires `linkUrl`; `video_views` requires `video`. - `job_applicants` requires a `platformSpecificData.jobs` creative. - For `lead_generation` or `conversions` on LinkedIn, or to promote an existing post, use POST /v1/ads/boost.  **OpenAI Ads** - Only `traffic`, `awareness`, and `conversions` are supported (other goals return 400). Maps to OpenAI's `bidding_type` (clicks, impressions, conversions respectively). `conversions` requires an active conversion event setting on the account; create a tracking tag with `defaultEventType` via the tracking-tags API (`POST /v1/accounts/{accountId}/tracking-tags`), or configure a conversion event in OpenAI Ads Manager, or the request returns 422.  | [optional] |
+| **goal** | **String** | Required on legacy and multi-creative shapes; the attach shape inherits it from the ad set. Available goals vary by platform.  **Meta** - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL, or `promotedObject.customConversionId` to optimise against a Custom Conversion instead. - `lead_conversion`: OUTCOME_LEADS optimizing website pixel leads. Same pixel and event fields, but with a leads-class event such as LEAD, SUBMIT_APPLICATION, SCHEDULE or CONTACT (or `promotedObject.customConversionId` to optimise against a Custom Conversion instead). Meta gates conversion events by objective, so leads-class events are rejected under `conversions`. - `lead_generation`: OUTCOME_LEADS with instant forms. Requires `leadGenFormId`. `promotedObject.pageId` is optional and auto-filled from the connected Page. - `app_promotion`: requires `promotedObject.applicationId` and `promotedObject.objectStoreUrl`. - `catalog_sales`: Advantage+ catalog ads, for example vehicle inventory. Requires `promotedObject.productSetId`, `promotedObject.pixelId` and `promotedObject.customEventType`. Builds a catalog TEMPLATE creative from the copy fields, which may carry template tags like {{product.name}} or {{vehicle.make}}. No imageUrl or video is sent; Meta renders the visuals per catalog item. Discover catalogs via GET /v1/ads/catalogs and product sets via GET /v1/ads/catalogs/{catalogId}/product-sets. Single shape only, no creatives[], adSetId, dynamicCreative or placementAssets.  **TikTok** - `conversions`: website-conversion ad group. Requires `promotedObject.pixelId`, your TikTok Pixel ID. Accepts an optional `promotedObject.customEventType` with a TikTok optimization_event code your pixel tracks (newer pixels use e.g. SHOPPING for purchase events; legacy pixels use ON_WEB_ORDER, INITIATE_ORDER, ON_WEB_REGISTER or FORM). To inherit pixel and event from an existing ad group, pass `adSetId` instead.  **LinkedIn** - `engagement`, `traffic`, `awareness` and `video_views` create standalone Direct Sponsored Content ads. `traffic` requires `linkUrl`; `video_views` requires `video`. - `job_applicants` requires a `platformSpecificData.jobs` creative. - For `lead_generation` or `conversions` on LinkedIn, or to promote an existing post, use POST /v1/ads/boost.  **OpenAI Ads** - Only `traffic`, `awareness`, and `conversions` are supported (other goals return 400). Maps to OpenAI's `bidding_type` (clicks, impressions, conversions respectively). `conversions` requires an active conversion event setting on the account; create a tracking tag with `defaultEventType` via the tracking-tags API (`POST /v1/accounts/{accountId}/tracking-tags`), or configure a conversion event in OpenAI Ads Manager, or the request returns 422.  | [optional] |
 | **optimization_goal** | **String** | Meta only. Explicit ad-set `optimization_goal` (e.g. `LANDING_PAGE_VIEWS`, `LINK_CLICKS`, `REACH`, `IMPRESSIONS`, `OFFSITE_CONVERSIONS`, `THRUPLAY`, `LEAD_GENERATION`). Overrides the default derived from `goal` (e.g. `traffic` defaults to `LINK_CLICKS`). Forwarded verbatim to Meta, which validates compatibility with the campaign objective and rejects incompatible combinations. | [optional] |
 | **billing_event** | **String** | Meta only. Explicit ad-set `billing_event`. Defaults to `IMPRESSIONS`. Forwarded verbatim to Meta, which validates compatibility with the optimization goal. | [optional] |
 | **buying_type** | **String** | Meta only. RESERVED = Reach & Frequency: requires `rfPredictionId` (a RESERVED prediction from /v1/ads/rf-predictions + /reserve). Budget, schedule and pricing come from the reservation, so budgetAmount/budgetType are not required and bid fields are ignored. Only the plain single-ad shape (no creatives[], adSetId, existingCampaignId or dynamicCreative). | [optional] |

data/docs/PreflightSmsRegistration200Response.md

@@ -0,0 +1,24 @@
+# Zernio::PreflightSmsRegistration200Response
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **composed** | [**PreflightSmsRegistration200ResponseComposed**](PreflightSmsRegistration200ResponseComposed.md) |  | [optional] |
+| **advisories** | [**Array<PreflightSmsRegistration200ResponseAdvisoriesInner>**](PreflightSmsRegistration200ResponseAdvisoriesInner.md) |  | [optional] |
+| **verdict** | **String** |  | [optional] |
+| **ai_unavailable** | **Boolean** | True when the AI portion of the check could not run; advisories then contain only deterministic findings. | [optional] |
+
+## Example
+
+```ruby
+require 'zernio-sdk'
+
+instance = Zernio::PreflightSmsRegistration200Response.new(
+  composed: null,
+  advisories: null,
+  verdict: null,
+  ai_unavailable: null
+)
+```
+

data/docs/PreflightSmsRegistration200ResponseAdvisoriesInner.md

@@ -0,0 +1,24 @@
+# Zernio::PreflightSmsRegistration200ResponseAdvisoriesInner
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **field** | **String** | The payload field the finding is about, when attributable. | [optional] |
+| **code** | **String** | Stable rule id for deterministic findings; absent on AI findings. | [optional] |
+| **concern** | **String** |  | [optional] |
+| **severity** | **String** |  | [optional] |
+
+## Example
+
+```ruby
+require 'zernio-sdk'
+
+instance = Zernio::PreflightSmsRegistration200ResponseAdvisoriesInner.new(
+  field: null,
+  code: null,
+  concern: null,
+  severity: null
+)
+```
+

data/docs/PreflightSmsRegistration200ResponseComposed.md

@@ -0,0 +1,20 @@
+# Zernio::PreflightSmsRegistration200ResponseComposed
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **brand** | **Object** |  | [optional] |
+| **campaign** | **Object** |  | [optional] |
+
+## Example
+
+```ruby
+require 'zernio-sdk'
+
+instance = Zernio::PreflightSmsRegistration200ResponseComposed.new(
+  brand: null,
+  campaign: null
+)
+```
+

data/docs/PreflightSmsRegistrationRequest.md

@@ -0,0 +1,26 @@
+# Zernio::PreflightSmsRegistrationRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **registration_type** | **String** |  |  |
+| **phone_numbers** | **Array<String>** |  | [optional] |
+| **brand** | **Object** | Same shape as the registration `brand`. |  |
+| **campaign** | **Object** | Same shape as the registration `campaign`. |  |
+| **messaging_brand_name** | **String** |  | [optional] |
+
+## Example
+
+```ruby
+require 'zernio-sdk'
+
+instance = Zernio::PreflightSmsRegistrationRequest.new(
+  registration_type: null,
+  phone_numbers: null,
+  brand: null,
+  campaign: null,
+  messaging_brand_name: null
+)
+```
+

data/docs/RespondToSmsRegistrationReview200Response.md

@@ -0,0 +1,18 @@
+# Zernio::RespondToSmsRegistrationReview200Response
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **status** | **String** |  | [optional] |
+
+## Example
+
+```ruby
+require 'zernio-sdk'
+
+instance = Zernio::RespondToSmsRegistrationReview200Response.new(
+  status: null
+)
+```
+

data/docs/RespondToSmsRegistrationReviewRequest.md

@@ -0,0 +1,20 @@
+# Zernio::RespondToSmsRegistrationReviewRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **note** | **String** | Answer for the reviewer. Required when no files are sent. | [optional] |
+| **files** | **Array<String>** | Hosted document URLs returned by POST /v1/sms/opt-in-proof. | [optional] |
+
+## Example
+
+```ruby
+require 'zernio-sdk'
+
+instance = Zernio::RespondToSmsRegistrationReviewRequest.new(
+  note: null,
+  files: null
+)
+```
+

data/docs/SMSApi.md

@@ -15,8 +15,10 @@ All URIs are relative to *https://zernio.com/api*
 | [**list_sms_registrations**](SMSApi.md#list_sms_registrations) | **GET** /v1/sms/registrations | List carrier registrations |
 | [**list_sms_sender_ids**](SMSApi.md#list_sms_sender_ids) | **GET** /v1/sms/sender-ids | List alphanumeric sender IDs |
 | [**lookup_sms_number**](SMSApi.md#lookup_sms_number) | **GET** /v1/sms/lookup | Look up carrier + line type |
+| [**preflight_sms_registration**](SMSApi.md#preflight_sms_registration) | **POST** /v1/sms/registrations/preflight | Pre-check a carrier registration |
 | [**request_sms_sender_id_limit_increase**](SMSApi.md#request_sms_sender_id_limit_increase) | **POST** /v1/sms/sender-ids/limit-request | Request a higher sender ID daily limit |
 | [**resend_sms_registration_otp**](SMSApi.md#resend_sms_registration_otp) | **POST** /v1/sms/registrations/{id}/resend-otp | Re-send the sole-prop OTP |
+| [**respond_to_sms_registration_review**](SMSApi.md#respond_to_sms_registration_review) | **POST** /v1/sms/registrations/{id}/respond | Reply to a change request |
 | [**reuse_sms_registration_for_number**](SMSApi.md#reuse_sms_registration_for_number) | **POST** /v1/phone-numbers/{id}/sms/reuse-registration | Add number to SMS registration |
 | [**send_sms**](SMSApi.md#send_sms) | **POST** /v1/sms/messages | Send an SMS/MMS |
 | [**share_sms_registration**](SMSApi.md#share_sms_registration) | **POST** /v1/sms/registrations/share | Create a registration share link |
@@ -786,6 +788,75 @@ end
 - **Accept**: application/json
 
 
+## preflight_sms_registration
+
+> <PreflightSmsRegistration200Response> preflight_sms_registration(preflight_sms_registration_request)
+
+Pre-check a carrier registration
+
+Dry-run of `POST /v1/sms/registrations` for 10DLC: validates and composes the exact brand/campaign payloads a submission would store (branding, disclosures, auto-replies), runs deterministic compliance lints plus an AI reviewer over them, and returns the findings WITHOUT creating anything. Use it to fix issues before submitting; `block` severity findings indicate a near-certain carrier rejection. 
+
+### Examples
+
+```ruby
+require 'time'
+require 'zernio-sdk'
+# setup authorization
+Zernio.configure do |config|
+  # Configure Bearer authorization (JWT): bearerAuth
+  config.access_token = 'YOUR_BEARER_TOKEN'
+end
+
+api_instance = Zernio::SMSApi.new
+preflight_sms_registration_request = Zernio::PreflightSmsRegistrationRequest.new({registration_type: 'standard_10dlc', brand: 3.56, campaign: 3.56}) # PreflightSmsRegistrationRequest | 
+
+begin
+  # Pre-check a carrier registration
+  result = api_instance.preflight_sms_registration(preflight_sms_registration_request)
+  p result
+rescue Zernio::ApiError => e
+  puts "Error when calling SMSApi->preflight_sms_registration: #{e}"
+end
+```
+
+#### Using the preflight_sms_registration_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<PreflightSmsRegistration200Response>, Integer, Hash)> preflight_sms_registration_with_http_info(preflight_sms_registration_request)
+
+```ruby
+begin
+  # Pre-check a carrier registration
+  data, status_code, headers = api_instance.preflight_sms_registration_with_http_info(preflight_sms_registration_request)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <PreflightSmsRegistration200Response>
+rescue Zernio::ApiError => e
+  puts "Error when calling SMSApi->preflight_sms_registration_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **preflight_sms_registration_request** | [**PreflightSmsRegistrationRequest**](PreflightSmsRegistrationRequest.md) |  |  |
+
+### Return type
+
+[**PreflightSmsRegistration200Response**](PreflightSmsRegistration200Response.md)
+
+### Authorization
+
+[bearerAuth](../README.md#bearerAuth)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
 ## request_sms_sender_id_limit_increase
 
 > <RequestSmsSenderIdLimitIncrease200Response> request_sms_sender_id_limit_increase(request_sms_sender_id_limit_increase_request)
@@ -924,6 +995,77 @@ end
 - **Accept**: application/json
 
 
+## respond_to_sms_registration_review
+
+> <RespondToSmsRegistrationReview200Response> respond_to_sms_registration_review(id, respond_to_sms_registration_review_request)
+
+Reply to a change request
+
+Replies to a reviewer change request on a registration in `changes_requested` state: a note, hosted document URLs (from `POST /v1/sms/opt-in-proof`), or both, sent together. The registration returns to `requested` (back in review) — no need to resubmit the whole registration. To change the submitted brand/campaign fields themselves, resubmit via `POST /v1/sms/registrations` with `resubmitRequestId` instead. 
+
+### Examples
+
+```ruby
+require 'time'
+require 'zernio-sdk'
+# setup authorization
+Zernio.configure do |config|
+  # Configure Bearer authorization (JWT): bearerAuth
+  config.access_token = 'YOUR_BEARER_TOKEN'
+end
+
+api_instance = Zernio::SMSApi.new
+id = 'id_example' # String | 
+respond_to_sms_registration_review_request = Zernio::RespondToSmsRegistrationReviewRequest.new # RespondToSmsRegistrationReviewRequest | 
+
+begin
+  # Reply to a change request
+  result = api_instance.respond_to_sms_registration_review(id, respond_to_sms_registration_review_request)
+  p result
+rescue Zernio::ApiError => e
+  puts "Error when calling SMSApi->respond_to_sms_registration_review: #{e}"
+end
+```
+
+#### Using the respond_to_sms_registration_review_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<RespondToSmsRegistrationReview200Response>, Integer, Hash)> respond_to_sms_registration_review_with_http_info(id, respond_to_sms_registration_review_request)
+
+```ruby
+begin
+  # Reply to a change request
+  data, status_code, headers = api_instance.respond_to_sms_registration_review_with_http_info(id, respond_to_sms_registration_review_request)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <RespondToSmsRegistrationReview200Response>
+rescue Zernio::ApiError => e
+  puts "Error when calling SMSApi->respond_to_sms_registration_review_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **String** |  |  |
+| **respond_to_sms_registration_review_request** | [**RespondToSmsRegistrationReviewRequest**](RespondToSmsRegistrationReviewRequest.md) |  |  |
+
+### Return type
+
+[**RespondToSmsRegistrationReview200Response**](RespondToSmsRegistrationReview200Response.md)
+
+### Authorization
+
+[bearerAuth](../README.md#bearerAuth)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
 ## reuse_sms_registration_for_number
 
 > <ReuseSmsRegistrationForNumber200Response> reuse_sms_registration_for_number(id)

data/docs/StartSmsRegistrationRequest.md

@@ -8,6 +8,7 @@
 | **phone_numbers** | **Array<String>** | Your numbers this registration covers. |  |
 | **brand** | [**StartSmsRegistrationRequestBrand**](StartSmsRegistrationRequestBrand.md) |  | [optional] |
 | **campaign** | [**StartSmsRegistrationRequestCampaign**](StartSmsRegistrationRequestCampaign.md) |  | [optional] |
+| **messaging_brand_name** | **String** | DBA / trade name used to brand message content (samples and auto-replies) when it differs from the legal name, e.g. a sole proprietor texting under a business name. The legal `brand.displayName` is still what the carrier vets. | [optional] |
 | **wizard_values** | **Hash<String, String>** | Raw dashboard-wizard answers, stored only to prefill edit-and-resubmit. API integrators can omit. | [optional] |
 | **resubmit_request_id** | **String** | Resubmit a registration that was returned for changes — updates it in place instead of creating a new one. | [optional] |
 | **toll_free** | [**StartSmsRegistrationRequestTollFree**](StartSmsRegistrationRequestTollFree.md) |  | [optional] |
@@ -22,6 +23,7 @@ instance = Zernio::StartSmsRegistrationRequest.new(
   phone_numbers: null,
   brand: null,
   campaign: null,
+  messaging_brand_name: null,
   wizard_values: null,
   resubmit_request_id: null,
   toll_free: null

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

@@ -732,6 +732,74 @@ module Zernio
       return data, status_code, headers
     end
 
+    # Pre-check a carrier registration
+    # Dry-run of `POST /v1/sms/registrations` for 10DLC: validates and composes the exact brand/campaign payloads a submission would store (branding, disclosures, auto-replies), runs deterministic compliance lints plus an AI reviewer over them, and returns the findings WITHOUT creating anything. Use it to fix issues before submitting; `block` severity findings indicate a near-certain carrier rejection. 
+    # @param preflight_sms_registration_request [PreflightSmsRegistrationRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [PreflightSmsRegistration200Response]
+    def preflight_sms_registration(preflight_sms_registration_request, opts = {})
+      data, _status_code, _headers = preflight_sms_registration_with_http_info(preflight_sms_registration_request, opts)
+      data
+    end
+
+    # Pre-check a carrier registration
+    # Dry-run of `POST /v1/sms/registrations` for 10DLC: validates and composes the exact brand/campaign payloads a submission would store (branding, disclosures, auto-replies), runs deterministic compliance lints plus an AI reviewer over them, and returns the findings WITHOUT creating anything. Use it to fix issues before submitting; `block` severity findings indicate a near-certain carrier rejection. 
+    # @param preflight_sms_registration_request [PreflightSmsRegistrationRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(PreflightSmsRegistration200Response, Integer, Hash)>] PreflightSmsRegistration200Response data, response status code and response headers
+    def preflight_sms_registration_with_http_info(preflight_sms_registration_request, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: SMSApi.preflight_sms_registration ...'
+      end
+      # verify the required parameter 'preflight_sms_registration_request' is set
+      if @api_client.config.client_side_validation && preflight_sms_registration_request.nil?
+        fail ArgumentError, "Missing the required parameter 'preflight_sms_registration_request' when calling SMSApi.preflight_sms_registration"
+      end
+      # resource path
+      local_var_path = '/v1/sms/registrations/preflight'
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
+      # HTTP header 'Content-Type'
+      content_type = @api_client.select_header_content_type(['application/json'])
+      if !content_type.nil?
+          header_params['Content-Type'] = content_type
+      end
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body] || @api_client.object_to_http_body(preflight_sms_registration_request)
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'PreflightSmsRegistration200Response'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['bearerAuth']
+
+      new_options = opts.merge(
+        :operation => :"SMSApi.preflight_sms_registration",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: SMSApi#preflight_sms_registration\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # Request a higher sender ID daily limit
     # Asks support to raise the workspace's daily sender-ID message cap. There is no self-serve raise: the request (desired cap + use case) is reviewed manually, usually within a business day. 
     # @param request_sms_sender_id_limit_increase_request [RequestSmsSenderIdLimitIncreaseRequest] 
@@ -863,6 +931,80 @@ module Zernio
       return data, status_code, headers
     end
 
+    # Reply to a change request
+    # Replies to a reviewer change request on a registration in `changes_requested` state: a note, hosted document URLs (from `POST /v1/sms/opt-in-proof`), or both, sent together. The registration returns to `requested` (back in review) — no need to resubmit the whole registration. To change the submitted brand/campaign fields themselves, resubmit via `POST /v1/sms/registrations` with `resubmitRequestId` instead. 
+    # @param id [String] 
+    # @param respond_to_sms_registration_review_request [RespondToSmsRegistrationReviewRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [RespondToSmsRegistrationReview200Response]
+    def respond_to_sms_registration_review(id, respond_to_sms_registration_review_request, opts = {})
+      data, _status_code, _headers = respond_to_sms_registration_review_with_http_info(id, respond_to_sms_registration_review_request, opts)
+      data
+    end
+
+    # Reply to a change request
+    # Replies to a reviewer change request on a registration in &#x60;changes_requested&#x60; state: a note, hosted document URLs (from &#x60;POST /v1/sms/opt-in-proof&#x60;), or both, sent together. The registration returns to &#x60;requested&#x60; (back in review) — no need to resubmit the whole registration. To change the submitted brand/campaign fields themselves, resubmit via &#x60;POST /v1/sms/registrations&#x60; with &#x60;resubmitRequestId&#x60; instead. 
+    # @param id [String] 
+    # @param respond_to_sms_registration_review_request [RespondToSmsRegistrationReviewRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(RespondToSmsRegistrationReview200Response, Integer, Hash)>] RespondToSmsRegistrationReview200Response data, response status code and response headers
+    def respond_to_sms_registration_review_with_http_info(id, respond_to_sms_registration_review_request, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: SMSApi.respond_to_sms_registration_review ...'
+      end
+      # verify the required parameter 'id' is set
+      if @api_client.config.client_side_validation && id.nil?
+        fail ArgumentError, "Missing the required parameter 'id' when calling SMSApi.respond_to_sms_registration_review"
+      end
+      # verify the required parameter 'respond_to_sms_registration_review_request' is set
+      if @api_client.config.client_side_validation && respond_to_sms_registration_review_request.nil?
+        fail ArgumentError, "Missing the required parameter 'respond_to_sms_registration_review_request' when calling SMSApi.respond_to_sms_registration_review"
+      end
+      # resource path
+      local_var_path = '/v1/sms/registrations/{id}/respond'.sub('{' + 'id' + '}', CGI.escape(id.to_s))
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
+      # HTTP header 'Content-Type'
+      content_type = @api_client.select_header_content_type(['application/json'])
+      if !content_type.nil?
+          header_params['Content-Type'] = content_type
+      end
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:debug_body] || @api_client.object_to_http_body(respond_to_sms_registration_review_request)
+
+      # return_type
+      return_type = opts[:debug_return_type] || 'RespondToSmsRegistrationReview200Response'
+
+      # auth_names
+      auth_names = opts[:debug_auth_names] || ['bearerAuth']
+
+      new_options = opts.merge(
+        :operation => :"SMSApi.respond_to_sms_registration_review",
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: SMSApi#respond_to_sms_registration_review\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # Add number to SMS registration
     # Attaches this number to your existing approved 10DLC campaign instead of running a fresh registration: the number inherits the campaign's approval (no new brand or campaign, no extra carrier fee). Enable SMS on the number first (`POST /v1/phone-numbers/{id}/sms`; its response tells you whether a reusable registration exists). 
     # @param id [String] 

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

@@ -32,7 +32,7 @@ module Zernio
 
     attr_accessor :tracking
 
-    # Required on legacy and multi-creative shapes; the attach shape inherits it from the ad set. Available goals vary by platform.  **Meta** - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL. - `lead_conversion`: OUTCOME_LEADS optimizing website pixel leads. Same pixel and event fields, but with a leads-class event such as LEAD, SUBMIT_APPLICATION, SCHEDULE or CONTACT. Meta gates conversion events by objective, so leads-class events are rejected under `conversions`. - `lead_generation`: OUTCOME_LEADS with instant forms. Requires `leadGenFormId`. `promotedObject.pageId` is optional and auto-filled from the connected Page. - `app_promotion`: requires `promotedObject.applicationId` and `promotedObject.objectStoreUrl`. - `catalog_sales`: Advantage+ catalog ads, for example vehicle inventory. Requires `promotedObject.productSetId`, `promotedObject.pixelId` and `promotedObject.customEventType`. Builds a catalog TEMPLATE creative from the copy fields, which may carry template tags like {{product.name}} or {{vehicle.make}}. No imageUrl or video is sent; Meta renders the visuals per catalog item. Discover catalogs via GET /v1/ads/catalogs and product sets via GET /v1/ads/catalogs/{catalogId}/product-sets. Single shape only, no creatives[], adSetId, dynamicCreative or placementAssets.  **TikTok** - `conversions`: website-conversion ad group. Requires `promotedObject.pixelId`, your TikTok Pixel ID. Accepts an optional `promotedObject.customEventType` with a TikTok optimization_event code your pixel tracks (newer pixels use e.g. SHOPPING for purchase events; legacy pixels use ON_WEB_ORDER, INITIATE_ORDER, ON_WEB_REGISTER or FORM). To inherit pixel and event from an existing ad group, pass `adSetId` instead.  **LinkedIn** - `engagement`, `traffic`, `awareness` and `video_views` create standalone Direct Sponsored Content ads. `traffic` requires `linkUrl`; `video_views` requires `video`. - `job_applicants` requires a `platformSpecificData.jobs` creative. - For `lead_generation` or `conversions` on LinkedIn, or to promote an existing post, use POST /v1/ads/boost.  **OpenAI Ads** - Only `traffic`, `awareness`, and `conversions` are supported (other goals return 400). Maps to OpenAI's `bidding_type` (clicks, impressions, conversions respectively). `conversions` requires an active conversion event setting on the account; create a tracking tag with `defaultEventType` via the tracking-tags API (`POST /v1/accounts/{accountId}/tracking-tags`), or configure a conversion event in OpenAI Ads Manager, or the request returns 422. 
+    # Required on legacy and multi-creative shapes; the attach shape inherits it from the ad set. Available goals vary by platform.  **Meta** - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL, or `promotedObject.customConversionId` to optimise against a Custom Conversion instead. - `lead_conversion`: OUTCOME_LEADS optimizing website pixel leads. Same pixel and event fields, but with a leads-class event such as LEAD, SUBMIT_APPLICATION, SCHEDULE or CONTACT (or `promotedObject.customConversionId` to optimise against a Custom Conversion instead). Meta gates conversion events by objective, so leads-class events are rejected under `conversions`. - `lead_generation`: OUTCOME_LEADS with instant forms. Requires `leadGenFormId`. `promotedObject.pageId` is optional and auto-filled from the connected Page. - `app_promotion`: requires `promotedObject.applicationId` and `promotedObject.objectStoreUrl`. - `catalog_sales`: Advantage+ catalog ads, for example vehicle inventory. Requires `promotedObject.productSetId`, `promotedObject.pixelId` and `promotedObject.customEventType`. Builds a catalog TEMPLATE creative from the copy fields, which may carry template tags like {{product.name}} or {{vehicle.make}}. No imageUrl or video is sent; Meta renders the visuals per catalog item. Discover catalogs via GET /v1/ads/catalogs and product sets via GET /v1/ads/catalogs/{catalogId}/product-sets. Single shape only, no creatives[], adSetId, dynamicCreative or placementAssets.  **TikTok** - `conversions`: website-conversion ad group. Requires `promotedObject.pixelId`, your TikTok Pixel ID. Accepts an optional `promotedObject.customEventType` with a TikTok optimization_event code your pixel tracks (newer pixels use e.g. SHOPPING for purchase events; legacy pixels use ON_WEB_ORDER, INITIATE_ORDER, ON_WEB_REGISTER or FORM). To inherit pixel and event from an existing ad group, pass `adSetId` instead.  **LinkedIn** - `engagement`, `traffic`, `awareness` and `video_views` create standalone Direct Sponsored Content ads. `traffic` requires `linkUrl`; `video_views` requires `video`. - `job_applicants` requires a `platformSpecificData.jobs` creative. - For `lead_generation` or `conversions` on LinkedIn, or to promote an existing post, use POST /v1/ads/boost.  **OpenAI Ads** - Only `traffic`, `awareness`, and `conversions` are supported (other goals return 400). Maps to OpenAI's `bidding_type` (clicks, impressions, conversions respectively). `conversions` requires an active conversion event setting on the account; create a tracking tag with `defaultEventType` via the tracking-tags API (`POST /v1/accounts/{accountId}/tracking-tags`), or configure a conversion event in OpenAI Ads Manager, or the request returns 422. 
     attr_accessor :goal
 
     # Meta only. Explicit ad-set `optimization_goal` (e.g. `LANDING_PAGE_VIEWS`, `LINK_CLICKS`, `REACH`, `IMPRESSIONS`, `OFFSITE_CONVERSIONS`, `THRUPLAY`, `LEAD_GENERATION`). Overrides the default derived from `goal` (e.g. `traffic` defaults to `LINK_CLICKS`). Forwarded verbatim to Meta, which validates compatibility with the campaign objective and rejects incompatible combinations.

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

@@ -14,7 +14,7 @@ require 'date'
 require 'time'
 
 module Zernio
-  # What the ad optimises against. Behaviour depends on the platform.  **Meta**: forwarded to the ad set's `promoted_object` (snake-cased). Required for goals whose ad-set optimization_goal points at a specific event/page/app (without it Meta rejects the ad-set create with `error_subcode: 1815430` \"Please select a promoted object for your ad set\"):   - `goal: conversions` (OFFSITE_CONVERSIONS): requires `pixelId` + `customEventType`   - `goal: app_promotion` (APP_INSTALLS): requires `applicationId` + `objectStoreUrl`   - `goal: lead_generation` (LEAD_GENERATION): `pageId` is auto-filled from the connected Page when omitted  Other Meta goals (engagement, traffic, awareness, video_views) ignore this field.  **TikTok**: only `goal: conversions` uses it.   - `pixelId` maps to the ad group's `pixel_id`. Required: a TikTok website-conversion     ad group without a pixel is rejected with `40002: Please select a pixel`.   - `customEventType` maps to the ad group's `optimization_event` (the pixel event to     optimise for). Optional: TikTok accepts a pixel-only auto-bid conversion ad group.     See the `customEventType` field below for the valid TikTok codes.  The remaining `promotedObject.*` fields are Meta-only. Platforms other than Meta and TikTok ignore `promotedObject` entirely. 
+  # What the ad optimises against. Behaviour depends on the platform.  **Meta**: forwarded to the ad set's `promoted_object` (snake-cased). Required for goals whose ad-set optimization_goal points at a specific event/page/app (without it Meta rejects the ad-set create with `error_subcode: 1815430` \"Please select a promoted object for your ad set\"):   - `goal: conversions` / `lead_conversion` (OFFSITE_CONVERSIONS): requires `pixelId` + `customEventType`, or `customConversionId` when optimising against a Custom Conversion (the conversion carries its own event definition)   - `goal: app_promotion` (APP_INSTALLS): requires `applicationId` + `objectStoreUrl`   - `goal: lead_generation` (LEAD_GENERATION): `pageId` is auto-filled from the connected Page when omitted  Other Meta goals (engagement, traffic, awareness, video_views) ignore this field.  **TikTok**: only `goal: conversions` uses it.   - `pixelId` maps to the ad group's `pixel_id`. Required: a TikTok website-conversion     ad group without a pixel is rejected with `40002: Please select a pixel`.   - `customEventType` maps to the ad group's `optimization_event` (the pixel event to     optimise for). Optional: TikTok accepts a pixel-only auto-bid conversion ad group.     See the `customEventType` field below for the valid TikTok codes.  The remaining `promotedObject.*` fields are Meta-only. Platforms other than Meta and TikTok ignore `promotedObject` entirely. 
   class CreateStandaloneAdRequestPromotedObject < ApiModelBase
     # Pixel ID. **Meta:** Facebook Pixel ID, required for `goal: conversions`. **TikTok:** TikTok Pixel ID, required for `goal: conversions`. 
     attr_accessor :pixel_id