zernio-sdk 0.0.539 → 0.0.541

data/docs/InboxApi.md

@@ -0,0 +1,79 @@
+# Zernio::InboxApi
+
+All URIs are relative to *https://zernio.com/api*
+
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**get_whats_app_media**](InboxApi.md#get_whats_app_media) | **GET** /v1/whatsapp/media/{mediaId} | Download WhatsApp media |
+
+
+## get_whats_app_media
+
+> File get_whats_app_media(media_id, account_id)
+
+Download WhatsApp media
+
+Streams the binary for a WhatsApp attachment. This is the endpoint the `url` on a WhatsApp `attachments[]` entry points at, in both the `message.received` webhook and the List messages response.  **This is an authenticated endpoint, not a public link.** Send `Authorization: Bearer <your API key>` exactly as you would for any other call. Passing the URL straight to a browser, an LLM vision API, or a no-code \"download file\" step without the header returns `401`. This is the most common integration mistake on this endpoint, and it differs from Instagram, Facebook and Telegram, whose `attachments[].url` is a direct CDN link that needs no header.  **Fetch on receipt, not lazily.** WhatsApp media lives in Meta's media store, not ours, and it is removed after a limited retention window (currently 7 days, and Meta has been dropping some inbound media sooner). Once Meta drops it the media is unrecoverable and this endpoint answers `400` permanently, so retrying will never succeed. Download and store the bytes when the webhook arrives. 
+
+### 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::InboxApi.new
+media_id = 'media_id_example' # String | The media id from `attachments[].payload.id`.
+account_id = 'account_id_example' # String | The WhatsApp account that received the media.
+
+begin
+  # Download WhatsApp media
+  result = api_instance.get_whats_app_media(media_id, account_id)
+  p result
+rescue Zernio::ApiError => e
+  puts "Error when calling InboxApi->get_whats_app_media: #{e}"
+end
+```
+
+#### Using the get_whats_app_media_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(File, Integer, Hash)> get_whats_app_media_with_http_info(media_id, account_id)
+
+```ruby
+begin
+  # Download WhatsApp media
+  data, status_code, headers = api_instance.get_whats_app_media_with_http_info(media_id, account_id)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => File
+rescue Zernio::ApiError => e
+  puts "Error when calling InboxApi->get_whats_app_media_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **media_id** | **String** | The media id from &#x60;attachments[].payload.id&#x60;. |  |
+| **account_id** | **String** | The WhatsApp account that received the media. |  |
+
+### Return type
+
+**File**
+
+### Authorization
+
+[bearerAuth](../README.md#bearerAuth)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/octet-stream, application/json
+

data/docs/InboxWebhookMessageAttachmentsInner.md

@@ -5,7 +5,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **type** | **String** | Attachment type (image, video, file, sticker, audio) |  |
-| **url** | **String** | Attachment URL (may expire for Meta platforms) |  |
+| **url** | **String** | Where to fetch the attachment. The contract depends on direction and platform: inbound WhatsApp media points at the authenticated `GET /v1/whatsapp/media/{mediaId}` and requires `Authorization: Bearer <your API key>`, while outgoing media carries the URL originally supplied and Instagram / Facebook / Telegram carry direct platform CDN links that need no authentication.  |  |
 | **payload** | **Object** | Additional attachment metadata | [optional] |
 
 ## Example

data/docs/SMSApi.md

@@ -5,17 +5,13 @@ All URIs are relative to *https://zernio.com/api*
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |
 | [**appeal_sms_registration**](SMSApi.md#appeal_sms_registration) | **POST** /v1/sms/registrations/{id}/appeal | Appeal a rejected campaign |
-| [**create_sms_sender_id**](SMSApi.md#create_sms_sender_id) | **POST** /v1/sms/sender-ids | Create an alphanumeric sender ID |
 | [**deactivate_sms_registration**](SMSApi.md#deactivate_sms_registration) | **DELETE** /v1/sms/registrations/{id} | Deactivate a brand/campaign registration |
-| [**delete_sms_sender_id**](SMSApi.md#delete_sms_sender_id) | **DELETE** /v1/sms/sender-ids/{id} | Delete an alphanumeric sender ID |
 | [**disable_sms_on_number**](SMSApi.md#disable_sms_on_number) | **DELETE** /v1/phone-numbers/{id}/sms | Disable SMS on a number |
 | [**enable_sms_on_number**](SMSApi.md#enable_sms_on_number) | **POST** /v1/phone-numbers/{id}/sms | Enable SMS on a number |
 | [**get_sms_registration**](SMSApi.md#get_sms_registration) | **GET** /v1/sms/registrations/{id} | Get a carrier registration |
 | [**list_sms_opt_outs**](SMSApi.md#list_sms_opt_outs) | **GET** /v1/sms/opt-outs | List SMS opt-outs |
 | [**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 |
-| [**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 |
 | [**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 |
@@ -97,75 +93,6 @@ end
 - **Accept**: application/json
 
 
-## create_sms_sender_id
-
-> <CreateSmsSenderId200Response> create_sms_sender_id(create_sms_sender_id_request)
-
-Create an alphanumeric sender ID
-
-Registers an alphanumeric sender ID (e.g. `ZERNIO`) — a branded `from` for one-way international SMS. No phone number purchase or carrier registration is needed; once created, pass it as `from` on `POST /v1/sms/messages`.  Constraints: 3-11 characters (letters, digits, spaces; at least one letter). Sends cannot reach the US, Canada, or Puerto Rico, are text-only, and recipients cannot reply. Sender IDs that impersonate well-known brands or institutions are rejected, and an ID already registered by another workspace returns 409 (active sender IDs are globally unique, first-come-first-served). Creating the same sender ID again is a no-op (re-activates it after a delete). 
-
-### 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
-create_sms_sender_id_request = Zernio::CreateSmsSenderIdRequest.new({sender_id: 'sender_id_example'}) # CreateSmsSenderIdRequest | 
-
-begin
-  # Create an alphanumeric sender ID
-  result = api_instance.create_sms_sender_id(create_sms_sender_id_request)
-  p result
-rescue Zernio::ApiError => e
-  puts "Error when calling SMSApi->create_sms_sender_id: #{e}"
-end
-```
-
-#### Using the create_sms_sender_id_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<CreateSmsSenderId200Response>, Integer, Hash)> create_sms_sender_id_with_http_info(create_sms_sender_id_request)
-
-```ruby
-begin
-  # Create an alphanumeric sender ID
-  data, status_code, headers = api_instance.create_sms_sender_id_with_http_info(create_sms_sender_id_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <CreateSmsSenderId200Response>
-rescue Zernio::ApiError => e
-  puts "Error when calling SMSApi->create_sms_sender_id_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **create_sms_sender_id_request** | [**CreateSmsSenderIdRequest**](CreateSmsSenderIdRequest.md) |  |  |
-
-### Return type
-
-[**CreateSmsSenderId200Response**](CreateSmsSenderId200Response.md)
-
-### Authorization
-
-[bearerAuth](../README.md#bearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: application/json
-
-
 ## deactivate_sms_registration
 
 > <DeactivateSmsRegistration200Response> deactivate_sms_registration(id)
@@ -235,75 +162,6 @@ end
 - **Accept**: application/json
 
 
-## delete_sms_sender_id
-
-> <DeleteSmsSenderId200Response> delete_sms_sender_id(id)
-
-Delete an alphanumeric sender ID
-
-Deactivates the sender ID so it can no longer send. Re-creating the same sender ID via `POST /v1/sms/sender-ids` re-activates it. 
-
-### 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 | Sender ID resource id.
-
-begin
-  # Delete an alphanumeric sender ID
-  result = api_instance.delete_sms_sender_id(id)
-  p result
-rescue Zernio::ApiError => e
-  puts "Error when calling SMSApi->delete_sms_sender_id: #{e}"
-end
-```
-
-#### Using the delete_sms_sender_id_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<DeleteSmsSenderId200Response>, Integer, Hash)> delete_sms_sender_id_with_http_info(id)
-
-```ruby
-begin
-  # Delete an alphanumeric sender ID
-  data, status_code, headers = api_instance.delete_sms_sender_id_with_http_info(id)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <DeleteSmsSenderId200Response>
-rescue Zernio::ApiError => e
-  puts "Error when calling SMSApi->delete_sms_sender_id_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **id** | **String** | Sender ID resource id. |  |
-
-### Return type
-
-[**DeleteSmsSenderId200Response**](DeleteSmsSenderId200Response.md)
-
-### Authorization
-
-[bearerAuth](../README.md#bearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: Not defined
-- **Accept**: application/json
-
-
 ## disable_sms_on_number
 
 > <DisableSmsOnNumber200Response> disable_sms_on_number(id)
@@ -653,70 +511,6 @@ end
 - **Accept**: application/json
 
 
-## list_sms_sender_ids
-
-> <ListSmsSenderIds200Response> list_sms_sender_ids
-
-List alphanumeric sender IDs
-
-### 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
-
-begin
-  # List alphanumeric sender IDs
-  result = api_instance.list_sms_sender_ids
-  p result
-rescue Zernio::ApiError => e
-  puts "Error when calling SMSApi->list_sms_sender_ids: #{e}"
-end
-```
-
-#### Using the list_sms_sender_ids_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<ListSmsSenderIds200Response>, Integer, Hash)> list_sms_sender_ids_with_http_info
-
-```ruby
-begin
-  # List alphanumeric sender IDs
-  data, status_code, headers = api_instance.list_sms_sender_ids_with_http_info
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <ListSmsSenderIds200Response>
-rescue Zernio::ApiError => e
-  puts "Error when calling SMSApi->list_sms_sender_ids_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-This endpoint does not need any parameter.
-
-### Return type
-
-[**ListSmsSenderIds200Response**](ListSmsSenderIds200Response.md)
-
-### Authorization
-
-[bearerAuth](../README.md#bearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: Not defined
-- **Accept**: application/json
-
-
 ## lookup_sms_number
 
 > <LookupSmsNumber200Response> lookup_sms_number(number)
@@ -786,75 +580,6 @@ end
 - **Accept**: application/json
 
 
-## request_sms_sender_id_limit_increase
-
-> <RequestSmsSenderIdLimitIncrease200Response> request_sms_sender_id_limit_increase(request_sms_sender_id_limit_increase_request)
-
-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. 
-
-### 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
-request_sms_sender_id_limit_increase_request = Zernio::RequestSmsSenderIdLimitIncreaseRequest.new({requested_cap: 37, reason: 'reason_example'}) # RequestSmsSenderIdLimitIncreaseRequest | 
-
-begin
-  # Request a higher sender ID daily limit
-  result = api_instance.request_sms_sender_id_limit_increase(request_sms_sender_id_limit_increase_request)
-  p result
-rescue Zernio::ApiError => e
-  puts "Error when calling SMSApi->request_sms_sender_id_limit_increase: #{e}"
-end
-```
-
-#### Using the request_sms_sender_id_limit_increase_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<RequestSmsSenderIdLimitIncrease200Response>, Integer, Hash)> request_sms_sender_id_limit_increase_with_http_info(request_sms_sender_id_limit_increase_request)
-
-```ruby
-begin
-  # Request a higher sender ID daily limit
-  data, status_code, headers = api_instance.request_sms_sender_id_limit_increase_with_http_info(request_sms_sender_id_limit_increase_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <RequestSmsSenderIdLimitIncrease200Response>
-rescue Zernio::ApiError => e
-  puts "Error when calling SMSApi->request_sms_sender_id_limit_increase_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **request_sms_sender_id_limit_increase_request** | [**RequestSmsSenderIdLimitIncreaseRequest**](RequestSmsSenderIdLimitIncreaseRequest.md) |  |  |
-
-### Return type
-
-[**RequestSmsSenderIdLimitIncrease200Response**](RequestSmsSenderIdLimitIncrease200Response.md)
-
-### Authorization
-
-[bearerAuth](../README.md#bearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: application/json
-
-
 ## resend_sms_registration_otp
 
 > <ResendSmsRegistrationOtp200Response> resend_sms_registration_otp(id)
@@ -999,7 +724,7 @@ end
 
 Send an SMS/MMS
 
-Sends an SMS (or MMS when `mediaUrls` is set) from one of your SMS-enabled numbers, or from an approved alphanumeric sender ID (`/v1/sms/sender-ids`). At least one of `text` / `mediaUrls` is required. Numbers are normalized to E.164, so `from` matches regardless of formatting and replies thread into the same inbox conversation.  US numbers must have an approved carrier registration (`/v1/sms/registrations`) before messages deliver.  **Alphanumeric sender IDs** are one-way and international only: they cannot reach the US, Canada, or Puerto Rico (403), are text-only (no MMS), and recipients cannot reply. Some destination countries substitute a numeric sender to ensure delivery.  **Idempotency:** send an `Idempotency-Key` header to make retries safe: same key + same body replays the original response instead of sending a second message; same key + different body returns 422; a key still in flight returns 409. 
+Sends an SMS (or MMS when `mediaUrls` is set) from one of your SMS-enabled numbers. At least one of `text` / `mediaUrls` is required. Both numbers are normalized to E.164, so `from` matches regardless of formatting and replies thread into the same inbox conversation.  US numbers must have an approved carrier registration (`/v1/sms/registrations`) before messages deliver.  **Idempotency:** send an `Idempotency-Key` header to make retries safe: same key + same body replays the original response instead of sending a second message; same key + different body returns 422; a key still in flight returns 409. 
 
 ### Examples
 

data/docs/SendSmsRequest.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **from** | **String** | One of your SMS-enabled numbers (E.164; formatting is normalized), or an approved alphanumeric sender ID (3-11 letters/digits/spaces, created via `/v1/sms/sender-ids`). |  |
+| **from** | **String** | One of your SMS-enabled numbers (E.164; formatting is normalized). |  |
 | **to** | **String** | Recipient number (E.164). |  |
 | **text** | **String** | Message body. Required unless `mediaUrls` is set. Max 10 SMS segments (1530 GSM-7 or 670 unicode characters). | [optional] |
 | **media_urls** | **Array<String>** | Public media URLs to attach (sends as MMS). Max 10. | [optional] |

data/docs/WebhookPayloadMessageMessage.md

@@ -10,7 +10,7 @@
 | **platform_message_id** | **String** | Platform's message ID |  |
 | **direction** | **String** |  |  |
 | **text** | **String** | Message text content |  |
-| **attachments** | [**Array<InboxWebhookMessageAttachmentsInner>**](InboxWebhookMessageAttachmentsInner.md) |  |  |
+| **attachments** | [**Array<WebhookPayloadMessageMessageAttachmentsInner>**](WebhookPayloadMessageMessageAttachmentsInner.md) |  |  |
 | **sender** | [**WebhookPayloadMessageMessageSender**](WebhookPayloadMessageMessageSender.md) |  |  |
 | **sent_at** | **Time** |  |  |
 | **is_read** | **Boolean** |  |  |

data/docs/WebhookPayloadMessageMessageAttachmentsInner.md

@@ -0,0 +1,22 @@
+# Zernio::WebhookPayloadMessageMessageAttachmentsInner
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **type** | **String** | Attachment type (image, video, file, sticker, audio) |  |
+| **url** | **String** | Where to fetch the attachment. **The contract differs by platform.**  - **WhatsApp**: points at `GET /v1/whatsapp/media/{mediaId}`, an   authenticated Zernio endpoint. You MUST send   `Authorization: Bearer <your API key>`; fetching it without that   header returns `401`. Download and store the bytes when this   webhook arrives: Meta drops inbound media after a limited   retention window, after which the endpoint answers `400`   permanently and the media is unrecoverable. - **Instagram / Facebook / Telegram**: a direct platform CDN link   that needs no authentication and expires on the platform's own   schedule.  |  |
+| **payload** | **Object** | Additional attachment metadata | [optional] |
+
+## Example
+
+```ruby
+require 'zernio-sdk'
+
+instance = Zernio::WebhookPayloadMessageMessageAttachmentsInner.new(
+  type: null,
+  url: null,
+  payload: null
+)
+```
+

data/docs/WebhookPayloadMessageSentMessage.md

@@ -10,7 +10,7 @@
 | **platform_message_id** | **String** | Platform's message ID |  |
 | **direction** | **String** |  |  |
 | **text** | **String** | Message text content |  |
-| **attachments** | [**Array<InboxWebhookMessageAttachmentsInner>**](InboxWebhookMessageAttachmentsInner.md) |  |  |
+| **attachments** | [**Array<WebhookPayloadMessageSentMessageAttachmentsInner>**](WebhookPayloadMessageSentMessageAttachmentsInner.md) |  |  |
 | **sender** | [**WebhookPayloadMessageSentMessageSender**](WebhookPayloadMessageSentMessageSender.md) |  |  |
 | **sent_at** | **Time** |  |  |
 | **is_read** | **Boolean** |  |  |

data/docs/WebhookPayloadMessageSentMessageAttachmentsInner.md

@@ -0,0 +1,22 @@
+# Zernio::WebhookPayloadMessageSentMessageAttachmentsInner
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **type** | **String** | Attachment type (image, video, file, sticker, audio) |  |
+| **url** | **String** | Where to fetch the attachment. For outgoing messages this is the media URL as sent, so for WhatsApp it is the URL you supplied when publishing (WhatsApp sends media by link), not a Zernio endpoint, and it needs no Zernio credentials. Contrast the inbound direction: `message.received` attachment URLs on WhatsApp point at the authenticated `GET /v1/whatsapp/media/{mediaId}`.  |  |
+| **payload** | **Object** | Additional attachment metadata | [optional] |
+
+## Example
+
+```ruby
+require 'zernio-sdk'
+
+instance = Zernio::WebhookPayloadMessageSentMessageAttachmentsInner.new(
+  type: null,
+  url: null,
+  payload: null
+)
+```
+

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

@@ -372,8 +372,8 @@ module Zernio
       return data, status_code, headers
     end
 
-    # Update an audience
-    # Update an audience. `saved_targeting` audiences accept `name`, `description`, and `spec` (full replacement, no merge, Zernio-only, no platform call). Platform audiences (uploaded/website/lookalike) accept `name` and `description` only, updated on the platform first and then mirrored locally; their rules are immutable, so `spec` returns 400 for them. Platform audience updates are Meta-only for now (other platforms return 501). Ads already created from a saved_targeting audience are unaffected, they snapshot the targeting at creation. 
+    # Update saved targeting audience
+    # Update a `saved_targeting` audience's name, description, or spec. Only `saved_targeting` audiences are updatable (they exist only on Zernio); uploaded/derived audiences return 422, delete and recreate those instead. `spec` replaces the stored spec wholesale (no merge). Ads already created from this audience are unaffected, they snapshot the targeting at creation. 
     # @param audience_id [String] 
     # @param update_ad_audience_request [UpdateAdAudienceRequest] 
     # @param [Hash] opts the optional parameters
@@ -383,8 +383,8 @@ module Zernio
       data
     end
 
-    # Update an audience
-    # Update an audience. `saved_targeting` audiences accept `name`, `description`, and `spec` (full replacement, no merge, Zernio-only, no platform call). Platform audiences (uploaded/website/lookalike) accept `name` and `description` only, updated on the platform first and then mirrored locally; their rules are immutable, so `spec` returns 400 for them. Platform audience updates are Meta-only for now (other platforms return 501). Ads already created from a saved_targeting audience are unaffected, they snapshot the targeting at creation. 
+    # Update saved targeting audience
+    # Update a `saved_targeting` audience's name, description, or spec. Only `saved_targeting` audiences are updatable (they exist only on Zernio); uploaded/derived audiences return 422, delete and recreate those instead. `spec` replaces the stored spec wholesale (no merge). Ads already created from this audience are unaffected, they snapshot the targeting at creation. 
     # @param audience_id [String] 
     # @param update_ad_audience_request [UpdateAdAudienceRequest] 
     # @param [Hash] opts the optional parameters