late-sdk 0.0.855 → 0.0.857

data/openapi.yaml

@@ -31,7 +31,7 @@ info:
 
     Key features: Unified posting to 16 platforms, ads management on 7 ad networks (via /v1/ads), aggregated analytics, unified inbox (DMs, comments, reviews), webhooks, OAuth connect, queue scheduling, and white-label support for agencies managing unlimited accounts.
 
-    Supported posting platforms: Twitter/X, Instagram, WhatsApp, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Reddit, Bluesky, Threads, Google Business, Telegram, Snapchat, Discord, Slack. Supported ad platforms: Meta Ads, Google Ads, TikTok Ads, LinkedIn Ads, Pinterest Ads, X Ads, OpenAI Ads.
+    Supported posting platforms: Twitter/X, Instagram, WhatsApp, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Reddit, Bluesky, Threads, Google Business, Telegram, Snapchat, Discord, Slack. Supported ad platforms: Meta Ads, Google Ads, TikTok Ads, LinkedIn Ads, Pinterest Ads, X Ads, OpenAI Ads. Snapchat is a closed beta with no public release date: connections are gated behind approval and return 403 `PLATFORM_BETA_RESTRICTED` until then.
   x-category: Social
   x-website: https://zernio.com
   x-thumbnail: https://rapidapi-prod-apis.s3.amazonaws.com/b24d3df5-563c-4a50-9e1e-1ad3eb1fce69.png
@@ -121,6 +121,8 @@ x-documentation:
     | Telegram | Yes | - | - | - |
     | Snapchat | Yes | - | - | - |
 
+    > **Snapchat Note:** Snapchat is a closed beta with no public release date. Connecting a Snapchat account is gated behind approval and returns 403 `PLATFORM_BETA_RESTRICTED` until then.
+
     > **LinkedIn Analytics Note:** For personal LinkedIn accounts, analytics are only available for posts published through Zernio. This is a LinkedIn API limitation: the `memberCreatorPostAnalytics` endpoint only returns metrics for posts authored by the authenticated user. Company/organization page analytics are not affected and work for all posts.
 
     > **Google Business Analytics Note:** Per-post analytics for Google Business Profile are deprecated by Google with no replacement, so Google Business posts always report `syncStatus: "unavailable"` with an explanatory `errorMessage`. Location-level metrics (impressions, clicks, calls, directions, bookings) are available via the dedicated `/v1/analytics/googlebusiness/performance` endpoint.
@@ -9180,6 +9182,49 @@ components:
             page_id: { type: string }
         earliestAd: { type: string, format: date-time }
         latestAd: { type: string, format: date-time }
+    AdKeyword:
+      type: object
+      properties:
+        id: { type: string }
+        accountId: { type: string, description: Social account ID owning the sync }
+        profileId: { type: string }
+        platform: { type: string, enum: [google] }
+        adAccountId: { type: string, description: Google customer ID }
+        campaignId: { type: string }
+        campaignName: { type: [string, "null"] }
+        campaignStatus: { type: [string, "null"] }
+        adSetId: { type: string, description: Google ad group ID }
+        adSetName: { type: [string, "null"] }
+        adSetStatus: { type: [string, "null"] }
+        keyword: { type: string }
+        matchType: { type: string, enum: [exact, phrase, broad, unknown] }
+        status: { type: string, enum: [active, paused] }
+        negative: { type: boolean }
+        qualityScore: { type: [integer, "null"], description: 'Google Quality Score, 1-10. Null when unrated.' }
+        syncedAt: { type: [string, "null"], format: date-time }
+        metrics:
+          type: [object, "null"]
+          description: 'Trailing 30-day window. Null on rows synced before the metrics columns existed (re-synced on the keyword''s next weekly sweep).'
+          properties:
+            windowDays: { type: integer }
+            clicks: { type: integer }
+            impressions: { type: integer }
+            cost: { type: number, description: 'Account currency, not USD-normalized' }
+            conversions: { type: number }
+            firstPageCpc: { type: [number, "null"], description: Account currency }
+            firstPositionCpc: { type: [number, "null"], description: Account currency }
+    KeywordEntry:
+      description: 'A Google Search keyword: a bare string (BROAD match), or an object naming the match type.'
+      oneOf:
+        - type: string
+          minLength: 1
+          maxLength: 80
+          description: 'Keyword text; defaults to BROAD match'
+        - type: object
+          required: [text]
+          properties:
+            text: { type: string, minLength: 1, maxLength: 80 }
+            matchType: { type: string, enum: [exact, phrase, broad] }
     ConversionEvent:
       type: object
       description: |
@@ -15018,6 +15063,10 @@ paths:
         Create and optionally publish a post. Immediate posts (`publishNow: true`) include `platformPostUrl` in the response.
         Content is optional when media is attached, all platforms have `customContent`, every platform entry is an X Article (`platformSpecificData.article`), or every platform entry is a LinkedIn text-free reshare (`platformSpecificData.reshareUrl` with no text). See each platform's schema for media constraints.
 
+        ## Scheduling
+
+        Pick one of `scheduledFor` (schedule), `publishNow: true` (publish synchronously) or `queuedFromProfile` (next queue slot). With none of them and `isDraft` unset, the post is saved as a draft. `platforms` is required unless the post is a draft. `isDraft: true` wins over `publishNow` and `scheduledFor` (the post is saved, never published); `publishNow: true` wins over `scheduledFor`. A `scheduledFor` already in the past is not rejected: the post is published synchronously in the same request, exactly like `publishNow`.
+
         ## Idempotency
 
         Two layers of duplicate-protection apply, so safe-to-retry callers (network blips, n8n / Zapier retries, etc.) don't accidentally double-post.
@@ -15055,6 +15104,7 @@ paths:
                   description: 'Post caption/text. Optional when media is attached, all platforms have customContent, every platform entry is an X Article (platformSpecificData.article), or every platform entry is a LinkedIn text-free reshare (platformSpecificData.reshareUrl with no text). Required for other text-only posts.'
                 mediaItems:
                   type: array
+                  description: 'Media attached to every platform in the request (a platform entry can override it with `customMedia`). Each entry needs a publicly reachable HTTPS `url`; `type` (image, video, gif, document) is inferred from the URL extension when omitted and a `type` that contradicts the extension is rejected with 400. Upload files with `POST /v1/media/presign` first; per-platform size, duration and format limits are listed on each platform schema.'
                   items: { $ref: '#/components/schemas/MediaItem' }
                 platforms:
                   type: array
@@ -15092,13 +15142,22 @@ paths:
                           - $ref: '#/components/schemas/BlueskyPlatformData'
                           - $ref: '#/components/schemas/DiscordPlatformData'
                           - $ref: '#/components/schemas/SlackPlatformData'
-                scheduledFor: { type: string, format: date-time }
-                publishNow: { type: boolean, default: false }
+                scheduledFor:
+                  type: string
+                  format: date-time
+                  description: 'When to publish. Required unless `publishNow` is true, `queuedFromProfile` is set, or the post is a draft. An ISO 8601 value with a `Z` or offset (`2026-01-15T10:00:00Z`, `2026-01-15T11:00:00+01:00`) is taken as-is; a value without one (`2026-01-15T10:00:00` or `2026-01-15 10:00`) is read as local time in `timezone`. A value already in the past is published synchronously in the same request. Ignored when `publishNow` is true.'
+                publishNow:
+                  type: boolean
+                  default: false
+                  description: 'Publish to every platform synchronously in this request instead of scheduling; the response then carries each platform result and `platformPostUrl`, with HTTP 207 when some platforms failed. Takes precedence over `scheduledFor`; ignored when `isDraft` is true.'
                 isDraft:
                   type: boolean
                   default: false
                   description: When true, saves the post as a draft. When none of scheduledFor, publishNow, or queuedFromProfile are provided, the post defaults to draft automatically.
-                timezone: { type: string, default: UTC }
+                timezone:
+                  type: string
+                  default: UTC
+                  description: 'IANA timezone (`Europe/Madrid`, `America/New_York`) used to interpret a `scheduledFor` (root or per-platform) that carries no `Z` or offset. Has no effect on values that already carry one. An unknown name returns 400 when `scheduledFor` is set.'
                 tags:
                   type: array
                   description: "Tags/keywords. YouTube constraints: each tag max 100 chars, combined max 500 chars, duplicates auto-removed."
@@ -15111,8 +15170,14 @@ paths:
                   type: array
                   description: "Stored for reference only. This field does NOT automatically create @mentions when publishing. For LinkedIn @mentions, use the /v1/accounts/{accountId}/linkedin-mentions endpoint to resolve profile URLs to URNs, then embed the returned mentionFormat directly in the post content field."
                   items: { type: string }
-                crosspostingEnabled: { type: boolean, default: true }
-                metadata: { type: object, additionalProperties: true }
+                crosspostingEnabled:
+                  type: boolean
+                  default: true
+                  description: 'Stored on the post and echoed back on reads. Publishing does not branch on it: every entry in `platforms` is published regardless, so treat it as a label for your own tooling.'
+                metadata:
+                  type: object
+                  additionalProperties: true
+                  description: 'Free-form key/value pairs of your own, stored on the post and returned on reads and in webhook payloads. Zernio also writes the bookkeeping keys `usageCounted`, `usageRefunded` and `hidden` into this object; do not set them, and they are stripped from webhook payloads.'
                 tiktokSettings:
                   $ref: '#/components/schemas/TikTokPlatformData'
                   description: 'Root-level TikTok settings applied to the TikTok platforms sent in the same request. Merged into each platform''s platformSpecificData, with platform-specific settings taking precedence.'
@@ -18011,7 +18076,7 @@ paths:
           schema:
             type: string
             enum: [facebook, instagram, linkedin, twitter, tiktok, youtube, threads, reddit, pinterest, bluesky, googlebusiness, telegram, snapchat, discord, slack, whatsapp]
-          description: Social media platform to connect
+          description: 'Social media platform to connect. `snapchat` is a closed beta with no public release date: it returns 403 `PLATFORM_BETA_RESTRICTED` until the account is approved.'
         - name: profileId
           in: query
           required: true
@@ -18126,7 +18191,7 @@ paths:
         '401': { $ref: '#/components/responses/Unauthorized' }
         '402': { $ref: '#/components/responses/PaymentRequired' }
         '403':
-          description: "No access to profile, or BYOK required for AppSumo Twitter"
+          description: "No access to profile, BYOK required for AppSumo Twitter, or Snapchat closed beta (code PLATFORM_BETA_RESTRICTED)"
         '404':
           description: Profile not found
     post:
@@ -21734,6 +21799,10 @@ paths:
                   value:
                     error: "Cannot connect to this profile. It exceeds your Pro plan limit of 5 profiles."
                     code: "PROFILE_LIMIT_EXCEEDED"
+                betaRestricted:
+                  value:
+                    error: "Snapchat integration is currently in beta. Please wait until it is publicly released."
+                    code: "PLATFORM_BETA_RESTRICTED"
         '500':
           description: Failed to connect Snapchat account
 
@@ -25959,7 +26028,7 @@ paths:
 
         `name`, `url` and `events` are required. `url` must be a valid URL and `events` must contain at least one event. Whitespace is trimmed from `url` before validation.
 
-        Webhooks are automatically disabled after 10 consecutive delivery failures.
+        Webhooks are auto-disabled only once the endpoint has had no successful delivery for 3 days AND has either reached 20 consecutive terminal failures (each one an event that exhausted the full retry ladder) or been failing continuously for 3 days. The owner is emailed; re-enable it with `isActive: true`.
 
         A restricted (zrk_) API key can only subscribe to events whose resource group
         the key holds; an event outside the key's groups is rejected with 403, so a
@@ -26071,7 +26140,7 @@ paths:
 
         When provided, `name` must be 1-50 characters, `url` must be a valid URL, and `events` must contain at least one event. Whitespace is trimmed from `url` before validation.
 
-        Webhooks are automatically disabled after 10 consecutive delivery failures.
+        Webhooks are auto-disabled only once the endpoint has had no successful delivery for 3 days AND has either reached 20 consecutive terminal failures (each one an event that exhausted the full retry ladder) or been failing continuously for 3 days. The owner is emailed; re-enable it with `isActive: true`.
 
         A restricted (zrk_) API key can only set `events` to events whose resource
         group the key holds; an event outside the key's groups is rejected with 403.
@@ -41282,30 +41351,126 @@ paths:
                 properties:
                   keywords:
                     type: array
-                    items:
-                      type: object
-                      properties:
-                        id: { type: string }
-                        accountId: { type: string, description: Social account ID owning the sync }
-                        profileId: { type: string }
-                        platform: { type: string, enum: [google] }
-                        adAccountId: { type: string, description: Google customer ID }
-                        campaignId: { type: string }
-                        campaignName: { type: [string, "null"] }
-                        campaignStatus: { type: [string, "null"] }
-                        adSetId: { type: string, description: Google ad group ID }
-                        adSetName: { type: [string, "null"] }
-                        adSetStatus: { type: [string, "null"] }
-                        keyword: { type: string }
-                        matchType: { type: string, enum: [exact, phrase, broad, unknown] }
-                        status: { type: string, enum: [active, paused] }
-                        negative: { type: boolean }
-                        syncedAt: { type: [string, "null"], format: date-time }
+                    items: { $ref: '#/components/schemas/AdKeyword' }
                   pagination: { $ref: '#/components/schemas/Pagination' }
         '400': { $ref: '#/components/responses/BadRequest' }
         '401': { $ref: '#/components/responses/Unauthorized' }
         '403':
           description: Ads access required. Legacy plans need the Ads add-on; included by default on usage-based plans.
+    post:
+      x-resource-group: "ads"
+      operationId: addAdKeywords
+      tags: ["Ad Campaigns"]
+      x-platforms: ["google"]
+      summary: Add Search keywords to an ad group
+      description: |
+        Adds one or more keyword criteria to an existing Google Search ad group,
+        without touching the keywords already there (unlike the whole-set diff on
+        `PUT /v1/ads/{adId}`, `keywords`/`negativeKeywords` in `platformSpecificData`,
+        which replaces the set). Set `negative: true` to add ad-group-level negatives
+        instead of positive keywords.
+      security:
+        - bearerAuth: []
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              type: object
+              required: [accountId, adSetId, keywords]
+              properties:
+                accountId: { type: string, description: Social account ID (Google Ads) }
+                adSetId: { type: string, description: Google ad group ID to add the keywords to }
+                keywords:
+                  type: array
+                  minItems: 1
+                  maxItems: 1000
+                  items:
+                    anyOf:
+                      - type: string
+                        description: 'Keyword text; defaults to BROAD match'
+                      - type: object
+                        required: [text]
+                        properties:
+                          text: { type: string, minLength: 1, maxLength: 80 }
+                          matchType: { type: string, enum: [exact, phrase, broad] }
+                negative: { type: boolean, default: false, description: 'Add as ad-group-level negatives instead of positive keywords' }
+      responses:
+        '201':
+          description: Keywords added
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  keywords:
+                    type: array
+                    items: { $ref: '#/components/schemas/AdKeyword' }
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '404': { description: 'The ad group ("adSetId") was not found for this account.' }
+        '501': { description: Only available on Google Ads accounts }
+
+  /v1/ads/keywords/{keywordId}:
+    patch:
+      x-resource-group: "ads"
+      operationId: updateAdKeyword
+      tags: ["Ad Campaigns"]
+      x-platforms: ["google"]
+      summary: Pause or enable a Search keyword
+      description: |
+        Changes `ad_group_criterion.status` for one keyword criterion (M.140).
+        Negative keywords have no status on Google and cannot be paused or enabled.
+      security:
+        - bearerAuth: []
+      parameters:
+        - { name: keywordId, in: path, required: true, schema: { type: string }, description: Zernio keyword ID (not the Google criterion ID) }
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              type: object
+              required: [status]
+              properties:
+                status: { type: string, enum: [active, paused] }
+      responses:
+        '200':
+          description: Keyword updated
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  keyword: { $ref: '#/components/schemas/AdKeyword' }
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '404': { description: Keyword not found }
+        '422': { description: 'Negative keywords have no status on Google; they cannot be paused or enabled.' }
+    delete:
+      x-resource-group: "ads"
+      operationId: removeAdKeyword
+      tags: ["Ad Campaigns"]
+      x-platforms: ["google"]
+      summary: Remove a Search keyword
+      description: Removes one keyword criterion (positive or negative) from its ad group (M.140).
+      security:
+        - bearerAuth: []
+      parameters:
+        - { name: keywordId, in: path, required: true, schema: { type: string }, description: Zernio keyword ID (not the Google criterion ID) }
+      responses:
+        '200':
+          description: Keyword removed
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  removed: { type: boolean, description: Always true on success }
+                  keywordId: { type: string }
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '404': { description: Keyword not found }
 
   /v1/ads/campaigns:
     get:
@@ -41627,6 +41792,102 @@ paths:
         '404': { description: Campaign not found }
         '501': { description: Operation not supported on this platform }
 
+  /v1/ads/campaigns/{campaignId}/negative-keywords:
+    get:
+      x-resource-group: "ads"
+      operationId: listCampaignNegativeKeywords
+      tags: ["Ad Campaigns"]
+      x-platforms: ["google"]
+      summary: List campaign-level negative keywords
+      description: |
+        Returns the campaign-level negative keywords (`campaign_criterion.negative`),
+        distinct from the ad-group-level negatives under `GET /v1/ads/keywords`. Read
+        live from Google on every call (not synced to Postgres), and gated by the
+        shared Google Ads operations budget like every other on-demand Google surface.
+
+        The platform is always discovered from the campaign itself; a non-Google
+        campaign returns 501 rather than 404, whether or not `platform` was passed.
+      security:
+        - bearerAuth: []
+      parameters:
+        - { name: campaignId, in: path, required: true, schema: { type: string }, description: Platform campaign ID }
+        - { name: platform, in: query, schema: { type: string, enum: [facebook, instagram, tiktok, linkedin, pinterest, google, twitter, openai] }, description: 'Optional and NOT authoritative: the resolved campaign''s own platform decides 200 vs 501, never this hint.' }
+      responses:
+        '200':
+          description: Campaign-level negative keywords
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  keywords:
+                    type: array
+                    items:
+                      type: object
+                      properties:
+                        criterionId: { type: string }
+                        text: { type: string }
+                        matchType: { type: string, enum: [exact, phrase, broad] }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '404': { description: Campaign not found }
+        '429': { description: Google Ads operations budget exhausted; retry later }
+        '501': { description: Only available on Google Ads campaigns }
+    put:
+      x-resource-group: "ads"
+      operationId: replaceCampaignNegativeKeywords
+      tags: ["Ad Campaigns"]
+      x-platforms: ["google"]
+      summary: Replace campaign-level negative keywords
+      description: |
+        Replaces the FULL set of campaign-level negative keywords (C.270): the desired
+        list is diffed against what Google already has, and the difference is applied
+        as one `create`/`remove` mutate. Send an empty array to clear every campaign
+        negative.
+
+        The platform is always discovered from the campaign itself; a non-Google
+        campaign returns 501 rather than 404, whether or not `platform` was sent.
+      security:
+        - bearerAuth: []
+      parameters:
+        - { name: campaignId, in: path, required: true, schema: { type: string }, description: Platform campaign ID }
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              type: object
+              required: [keywords]
+              properties:
+                platform: { type: string, enum: [facebook, instagram, tiktok, linkedin, pinterest, google, twitter, openai], description: 'Optional and NOT authoritative: the resolved campaign''s own platform decides 200 vs 501, never this hint.' }
+                keywords:
+                  type: array
+                  maxItems: 1000
+                  items: { $ref: '#/components/schemas/KeywordEntry' }
+      responses:
+        '200':
+          description: Campaign-level negative keywords replaced
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  created: { type: integer, description: Negative criteria newly created on Google }
+                  removed: { type: integer, description: Negative criteria removed from Google }
+                  keywords:
+                    type: array
+                    description: The full negative-keyword set after the replace
+                    items:
+                      type: object
+                      properties:
+                        criterionId: { type: string }
+                        text: { type: string }
+                        matchType: { type: string, enum: [exact, phrase, broad] }
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '404': { description: Campaign not found }
+        '429': { description: Google Ads operations budget exhausted; retry later }
+        '501': { description: Only available on Google Ads campaigns }
+
   /v1/ads/campaigns/bulk-status:
     post:
       x-resource-group: "ads"
@@ -45560,8 +45821,9 @@ paths:
                                 items: { type: string, enum: [mobile, desktop] }
                 audienceId: { type: string, description: Custom audience ID for targeting }
                 campaignType: { type: string, enum: [display, search], default: display, description: Google only }
-                keywords: { type: array, maxItems: 1000, items: { type: string, maxLength: 80 }, description: "Google Search only. BROAD-match keywords on the new ad group. Editable later via PUT /v1/ads/{adId} targeting.keywords, which also sets match types." }
-                negativeKeywords: { type: array, items: { type: string, maxLength: 80 }, description: "Google Search only; other platforms return 400. BROAD-match negative keywords on the new ad group. Editable later via PUT /v1/ads/{adId} targeting.negativeKeywords." }
+                keywords: { type: array, maxItems: 1000, items: { $ref: '#/components/schemas/KeywordEntry' }, description: "Google Search only. Keywords on the new ad group; entries are strings (BROAD) or { text, matchType }. Editable later via PUT /v1/ads/{adId} targeting.keywords." }
+                negativeKeywords: { type: array, maxItems: 1000, items: { $ref: '#/components/schemas/KeywordEntry' }, description: "Google Search only; other platforms return 400. Ad-group-level negative keywords on the new ad group. Editable later via PUT /v1/ads/{adId} targeting.negativeKeywords." }
+                campaignNegativeKeywords: { type: array, maxItems: 1000, items: { $ref: '#/components/schemas/KeywordEntry' }, description: "Google Search only; other platforms return 400. Campaign-level negative keywords (campaign_criterion.negative), created alongside the ad group. Editable later via PUT /v1/ads/campaigns/{campaignId}/negative-keywords." }
                 additionalHeadlines: { type: array, items: { type: string }, description: "Google Search RSA only. Extra headlines." }
                 additionalDescriptions: { type: array, items: { type: string }, description: "Google Search RSA only. Extra descriptions." }
                 sitelinks:
@@ -49010,7 +49272,8 @@ paths:
         pixel.
 
         NOT idempotent on either platform: each call creates a new pixel (and,
-        for OpenAI, a new Conversions API key). Do not retry blindly on
+        for OpenAI, a new Conversions API key plus, with `defaultEventType`, a
+        new conversion event setting). Do not retry blindly on
         timeout. Meta (platform `metaads`) and OpenAI Ads (platform
         `openaiads`); other platforms return 405.
       security:
@@ -49027,6 +49290,10 @@ paths:
               properties:
                 adAccountId: { type: string, description: 'Meta ad account id, e.g. `act_123456789`. Required by this endpoint but ignored for OpenAI Ads.' }
                 name: { type: string, minLength: 1, maxLength: 200 }
+                defaultEventType:
+                  type: string
+                  enum: [order_created, lead_created, items_added, contents_viewed, checkout_started, registration_completed, subscription_created, trial_started, appointment_scheduled, page_viewed, app_installed, app_opened]
+                  description: 'OpenAI Ads only (ignored by Meta). When set, also provisions a standard conversion event setting wired to the new pixel, so `goal: conversions` ad creates on `POST /v1/ads/create` have an event to reference immediately.'
       responses:
         '201':
           description: Tracking tag created

data/spec/api/ad_campaigns_api_spec.rb

@@ -32,6 +32,18 @@ describe 'AdCampaignsApi' do
     end
   end
 
+  # unit tests for add_ad_keywords
+  # Add Search keywords to an ad group
+  # Adds one or more keyword criteria to an existing Google Search ad group, without touching the keywords already there (unlike the whole-set diff on `PUT /v1/ads/{adId}`, `keywords`/`negativeKeywords` in `platformSpecificData`, which replaces the set). Set `negative: true` to add ad-group-level negatives instead of positive keywords. 
+  # @param add_ad_keywords_request 
+  # @param [Hash] opts the optional parameters
+  # @return [AddAdKeywords201Response]
+  describe 'add_ad_keywords test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for attach_campaign_assets
   # Attach extension assets to a Google Search campaign
   # Attach sitelinks, callouts and/or structured snippets to an already-existing Google Search campaign — the same builders POST /v1/ads/create uses, but without rebuilding the hierarchy. At least one of sitelinks, callouts or structuredSnippets is required.  Google-only. Other platforms have no equivalent extension surface and return 501.  Approval status is Google-async; poll `asset.policy_summary` after review. Assets stay in the account library even if the campaign is later deleted.
@@ -319,6 +331,44 @@ describe 'AdCampaignsApi' do
     end
   end
 
+  # unit tests for list_campaign_negative_keywords
+  # List campaign-level negative keywords
+  # Returns the campaign-level negative keywords (`campaign_criterion.negative`), distinct from the ad-group-level negatives under `GET /v1/ads/keywords`. Read live from Google on every call (not synced to Postgres), and gated by the shared Google Ads operations budget like every other on-demand Google surface.  The platform is always discovered from the campaign itself; a non-Google campaign returns 501 rather than 404, whether or not `platform` was passed. 
+  # @param campaign_id Platform campaign ID
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :platform Optional and NOT authoritative: the resolved campaign's own platform decides 200 vs 501, never this hint.
+  # @return [ListCampaignNegativeKeywords200Response]
+  describe 'list_campaign_negative_keywords test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for remove_ad_keyword
+  # Remove a Search keyword
+  # Removes one keyword criterion (positive or negative) from its ad group (M.140).
+  # @param keyword_id Zernio keyword ID (not the Google criterion ID)
+  # @param [Hash] opts the optional parameters
+  # @return [RemoveAdKeyword200Response]
+  describe 'remove_ad_keyword test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for replace_campaign_negative_keywords
+  # Replace campaign-level negative keywords
+  # Replaces the FULL set of campaign-level negative keywords (C.270): the desired list is diffed against what Google already has, and the difference is applied as one `create`/`remove` mutate. Send an empty array to clear every campaign negative.  The platform is always discovered from the campaign itself; a non-Google campaign returns 501 rather than 404, whether or not `platform` was sent. 
+  # @param campaign_id Platform campaign ID
+  # @param replace_campaign_negative_keywords_request 
+  # @param [Hash] opts the optional parameters
+  # @return [ReplaceCampaignNegativeKeywords200Response]
+  describe 'replace_campaign_negative_keywords test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for update_ad
   # Update ad
   # Patch one or more fields on an ad. Status, budget, targeting, and creative changes are propagated to the platform.  Per-platform support: - **Meta** (Facebook + Instagram): all fields supported. - **TikTok**: status, budget, targeting (via `/v2/adgroup/update/`), and creative   (via `/v2/ad/update/` patch-style — `headline` is ignored, `body` becomes `ad_text`). - **Google**: status, budget, and KEYWORD edits via `targeting.keywords` /   `targeting.negativeKeywords` — each list you send becomes the FULL new set of its   kind on the ad group (criteria not in the list are removed); a kind left out is   untouched. Any other `targeting` field returns 400: Google cannot mutate broad   targeting post-create without recreating the campaign. `creative` returns 501. - **LinkedIn**: status, budget, targeting (geo countries only, applied to the   LinkedIn Campaign via PARTIAL_UPDATE), and creative (uploads new media, creates a   replacement inline creative on the same campaign, pauses the old one). - **Pinterest / X / OpenAI Ads**: status + budget only. Sending   `targeting` or `creative` returns 501 with code `unsupported_platform_operation`.   OpenAI Ads budget is lifetime-only (see `budget.type` below). 
@@ -358,6 +408,19 @@ describe 'AdCampaignsApi' do
     end
   end
 
+  # unit tests for update_ad_keyword
+  # Pause or enable a Search keyword
+  # Changes `ad_group_criterion.status` for one keyword criterion (M.140). Negative keywords have no status on Google and cannot be paused or enabled. 
+  # @param keyword_id Zernio keyword ID (not the Google criterion ID)
+  # @param update_ad_keyword_request 
+  # @param [Hash] opts the optional parameters
+  # @return [UpdateAdKeyword200Response]
+  describe 'update_ad_keyword test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for update_ad_set
   # Update an ad set
   # Ad-set-level writes. Use this for ABO budget updates, ad-set-scoped pause/resume, bid-strategy edits, Meta value-rule-set attach/detach, and Meta-only post-launch delivery settings via `platformSpecificData`. At least one updatable field is required.  Value rule sets (Meta only, see `/v1/ads/value-rule-sets`): - ATTACH or REPLACE: send `valueRuleSetId`. Attachment is driven by the id's   presence, so `valueRulesApplied: true` is optional. Sending a different id   replaces the previous association; there is no separate replace call. - DETACH: send `valueRulesApplied: false` and OMIT `valueRuleSetId`. - Sending `valueRulesApplied: false` TOGETHER with `valueRuleSetId` returns 400   `mutually_exclusive_fields`. This is deliberate: Meta attaches the rule set   whenever `value_rule_set_id` is present, even with `value_rules_applied` false,   so echoing stored state while asking to detach would silently keep the bid   adjustments live. - Eligibility: only ad sets on `LOWEST_COST_WITHOUT_CAP` or `COST_CAP`. Meta   rejects the rest server-side. - Read back with `GET /v1/ads/ad-sets/{adSetId}?fields=value_rule_set_id`. Meta   does not document `value_rules_applied` as a readable ad-set field, so the   boolean cannot be read back.  Bid strategy compatibility (per Meta's spec): - `LOWEST_COST_WITHOUT_CAP`: no `bidAmount`, no `roasAverageFloor`. - `LOWEST_COST_WITH_BID_CAP` / `COST_CAP`: `bidAmount` REQUIRED (whole currency units). - `LOWEST_COST_WITH_MIN_ROAS`: `roasAverageFloor` REQUIRED (decimal multiplier, e.g. 2.0 = 2.0x ROAS). - Meta only: send `bidAmount` WITHOUT `bidStrategy` to change the cap amount on an ad set   under a COST_CAP / LOWEST_COST_WITH_BID_CAP parent campaign, leaving the strategy itself   (inherited from the campaign) untouched. `roasAverageFloor` without `bidStrategy` is   rejected (it has no meaning outside LOWEST_COST_WITH_MIN_ROAS).  Delivery settings are validated by Meta against the campaign objective; incompatible combinations (e.g. a billingEvent the optimization goal doesn't allow) surface as 400s from Meta.  When updating `budget` on an ABO campaign: if the parent campaign is CBO, the response is 409 with code BUDGET_LEVEL_MISMATCH — route to PUT /v1/ads/campaigns/{campaignId} instead. 
@@ -388,7 +451,7 @@ describe 'AdCampaignsApi' do
   # Pause or resume a single ad
   # Ad-scoped pause/resume — touches ONLY this ad, never its parent ad set or campaign (so sibling ads keep running). Thin wrapper over the `status` field of PUT /v1/ads/{adId}, for callers that want a URL symmetric to /v1/ads/campaigns/{campaignId}/status and /v1/ads/ad-sets/{adSetId}/status.  `{adId}` accepts the same identifier dialects as GET/PUT /v1/ads/{adId} (Zernio hex `_id`, Meta numeric `platformAdId`, or the creative's effective story/media IDs). `platform` is inferred from the ad, so it's not required in the body. Ads in terminal statuses (rejected, completed, cancelled) and no-op flips (already in the target state) are skipped. 
   # @param ad_id Zernio `_id` (hex), Meta `platformAdId` (numeric), or one of the creative's effective story/media IDs.
-  # @param update_ad_status_request 
+  # @param update_ad_keyword_request 
   # @param [Hash] opts the optional parameters
   # @return [UpdateAdStatus200Response]
   describe 'update_ad_status test' do

data/spec/api/connect_api_spec.rb

@@ -201,7 +201,7 @@ describe 'ConnectApi' do
   # unit tests for get_connect_url
   # 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 platform Social media platform to connect. `snapchat` is a closed beta with no public release date: it returns 403 `PLATFORM_BETA_RESTRICTED` until the account is approved.
   # @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. MUST be an absolute http(s) URL or a custom app scheme for mobile deeplinks (e.g. myapp://callback); a relative path is rejected with 400 INVALID_REDIRECT_URL. 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.  On failure, the browser is sent to the same redirect_url with `error` and `platform` appended. `error` and `platform` are always present. `error_message`, `is_user_fixable`, `reason` and `dashboard_url` are conditional and must be treated as optional.  This list is NOT exhaustive and new values may be added at any time. Treat an unrecognized value as a generic failure rather than matching it exhaustively. Existing values are not renamed or removed without notice.  OAuth and callback:   oauth_denied, invalid_callback, invalid_state, unsupported_platform, connection_failed,   internal_error, token_exchange_failed, byok_config_error, personal_account_not_supported,   missing_google_permissions, platform_requires_destination, reconnect_account_mismatch,   invalid_request  Access and limits:   profile_not_found, invalid_profile_id, access_denied, account_limit_exceeded,   profile_limit_exceeded, payment_required  Destination selection:   no_facebook_pages, facebook_pages_error, no_google_locations, google_locations_error,   google_permission_denied, no_snapchat_public_profiles, snapchat_profiles_error,   discord_no_guild, slack_no_team  WhatsApp:   whatsapp_error, one_whatsapp_per_profile, whatsapp_number_already_connected,   whatsapp_number_pinned_to_profile, connection_cancelled  Google Ads (platform=googleads):   google_ads_auth_failed, google_ads_invalid_state, google_ads_config_error,   google_ads_token_failed, google_ads_quota_exhausted, google_ads_callback_error  TikTok Ads (platform=tiktokads):   tiktok_ads_auth_failed, tiktok_ads_invalid_state, tiktok_ads_access_denied,   tiktok_ads_config_error, tiktok_ads_token_failed, tiktok_ads_account_not_found,   tiktok_ads_callback_error  X Ads (platform=xads):   x_ads_denied, x_ads_auth_failed, x_ads_config_error, x_ads_account_not_found,   x_ads_state_error, x_ads_token_failed, x_ads_token_missing, x_ads_callback_error  Shopify (platform=shopify):   shopify_auth_failed, shopify_config_error, shopify_invalid_state, shopify_invalid_hmac,   shopify_invalid_shop, shopify_missing_scopes, shopify_callback_error  1. On this endpoint every upstream OAuth error is collapsed into `oauth_denied`. The provider's own value (for example Meta's `access_denied`) is not forwarded. The dedicated ads flows below are different: they use their own denial slugs and `google_ads_auth_failed` and `tiktok_ads_auth_failed` may carry the provider's raw error string in `error_message`.  2. On the tiktok and twitter ads flows `platform` carries the ads platform id (`tiktokads`, `xads`), not the value used in the request path. The googleads and shopify flows report `googleads` and `shopify`. 

data/spec/api/posts_api_spec.rb

@@ -47,7 +47,7 @@ describe 'PostsApi' do
 
   # unit tests for create_post
   # Create post
-  # Create and optionally publish a post. Immediate posts (`publishNow: true`) include `platformPostUrl` in the response. Content is optional when media is attached, all platforms have `customContent`, every platform entry is an X Article (`platformSpecificData.article`), or every platform entry is a LinkedIn text-free reshare (`platformSpecificData.reshareUrl` with no text). See each platform's schema for media constraints.  ## Idempotency  Two layers of duplicate-protection apply, so safe-to-retry callers (network blips, n8n / Zapier retries, etc.) don't accidentally double-post.  **1. Same-request idempotency (5-minute window).** Pass an `x-request-id` header to mark a logical request. If a second request arrives with the same `x-request-id` while the first is in-flight (or within ~5 minutes of completion), we return **HTTP 200** with the original post in the `existingPost` field — no new post is created. The official Zernio SDKs auto-generate a unique `x-request-id` per call. If you're using a generic HTTP client (curl, n8n's HTTP node, Zapier, custom code), either: - Set a unique `x-request-id` per logical call (recommended — UUIDv4 is fine) - Or simply omit the header — we'll treat each request as new  **Common pitfall**: if your workflow tool uses a single execution-level request ID and reuses it across multiple HTTP nodes (e.g. one ID for the whole run, shared across 6 different platform calls), every call after the first will look like a retry of the first and return its post. Generate a fresh ID per node.  **2. Content-hash dedup (24-hour window).** Independently, we hash `(platform, accountId, content + media URLs)` and reject duplicates within 24 hours with **HTTP 409**. This catches genuine \"same content posted twice to the same account\" cases regardless of `x-request-id`. Returns `error`, `accountId`, `platform`, and `existingPostId` so you can find the original. To intentionally re-post identical content within 24h, change something (the caption, the media, the account) — the dedup is keyed on the full content fingerprint.  Order: same-`x-request-id` retries (200) are checked first; if no idempotency match, the content-hash dedup (409) runs. 
+  # Create and optionally publish a post. Immediate posts (`publishNow: true`) include `platformPostUrl` in the response. Content is optional when media is attached, all platforms have `customContent`, every platform entry is an X Article (`platformSpecificData.article`), or every platform entry is a LinkedIn text-free reshare (`platformSpecificData.reshareUrl` with no text). See each platform's schema for media constraints.  ## Scheduling  Pick one of `scheduledFor` (schedule), `publishNow: true` (publish synchronously) or `queuedFromProfile` (next queue slot). With none of them and `isDraft` unset, the post is saved as a draft. `platforms` is required unless the post is a draft. `isDraft: true` wins over `publishNow` and `scheduledFor` (the post is saved, never published); `publishNow: true` wins over `scheduledFor`. A `scheduledFor` already in the past is not rejected: the post is published synchronously in the same request, exactly like `publishNow`.  ## Idempotency  Two layers of duplicate-protection apply, so safe-to-retry callers (network blips, n8n / Zapier retries, etc.) don't accidentally double-post.  **1. Same-request idempotency (5-minute window).** Pass an `x-request-id` header to mark a logical request. If a second request arrives with the same `x-request-id` while the first is in-flight (or within ~5 minutes of completion), we return **HTTP 200** with the original post in the `existingPost` field — no new post is created. The official Zernio SDKs auto-generate a unique `x-request-id` per call. If you're using a generic HTTP client (curl, n8n's HTTP node, Zapier, custom code), either: - Set a unique `x-request-id` per logical call (recommended — UUIDv4 is fine) - Or simply omit the header — we'll treat each request as new  **Common pitfall**: if your workflow tool uses a single execution-level request ID and reuses it across multiple HTTP nodes (e.g. one ID for the whole run, shared across 6 different platform calls), every call after the first will look like a retry of the first and return its post. Generate a fresh ID per node.  **2. Content-hash dedup (24-hour window).** Independently, we hash `(platform, accountId, content + media URLs)` and reject duplicates within 24 hours with **HTTP 409**. This catches genuine \"same content posted twice to the same account\" cases regardless of `x-request-id`. Returns `error`, `accountId`, `platform`, and `existingPostId` so you can find the original. To intentionally re-post identical content within 24h, change something (the caption, the media, the account) — the dedup is keyed on the full content fingerprint.  Order: same-`x-request-id` retries (200) are checked first; if no idempotency match, the content-hash dedup (409) runs. 
   # @param create_post_request 
   # @param [Hash] opts the optional parameters
   # @option opts [String] :x_request_id Optional client-generated request identifier for safe retry (idempotency). When two requests carry the same value, the second is treated as a retry of the first and returns the original post (HTTP 200) instead of creating a duplicate. Window is ~5 minutes from the first request. Generate a UUID per logical call. SDKs do this automatically; HTTP clients should set it themselves or omit it. See the operation description for the full idempotency contract. 

data/spec/api/tracking_tags_api_spec.rb

@@ -48,7 +48,7 @@ describe 'TrackingTagsApi' do
 
   # unit tests for create_tracking_tag
   # Create a tracking tag
-  # Meta: creates a Meta Pixel on the given ad account (`POST /act_{id}/adspixels` — `name` is the only input). Returns the created tag including its install `code`. The pixel is owned by the Business Manager that owns the ad account; a pixel created on a personal (non-BM) ad account ends up with `ownerBusinessId: null` and can't be shared with other ad accounts.  Creating a Meta pixel does NOT install it — install the returned `code` snippet on the site, or send events server-side via `POST /v1/ads/conversions`. The check `installed` is derived from `lastFiredTime`.  OpenAI Ads: creates an OpenAI pixel AND provisions a Conversions API key for it in the same call (`adAccountId` is required by this endpoint but ignored — one API key maps to exactly one ad account, so there's nothing to select). Returns 422 (`FEATURE_NOT_AVAILABLE`) if the ad account isn't enabled for pixel management; contact your OpenAI partner representative to enable it. There is no delete API for OpenAI pixels. If the pixel is created but the Conversions API key provisioning then fails, the pixel is left live on OpenAI (it cannot be cleaned up) and the error message names the surviving pixel id and warns against retrying, since a retry would create a second, orphaned pixel.  NOT idempotent on either platform: each call creates a new pixel (and, for OpenAI, a new Conversions API key). Do not retry blindly on timeout. Meta (platform `metaads`) and OpenAI Ads (platform `openaiads`); other platforms return 405. 
+  # Meta: creates a Meta Pixel on the given ad account (`POST /act_{id}/adspixels` — `name` is the only input). Returns the created tag including its install `code`. The pixel is owned by the Business Manager that owns the ad account; a pixel created on a personal (non-BM) ad account ends up with `ownerBusinessId: null` and can't be shared with other ad accounts.  Creating a Meta pixel does NOT install it — install the returned `code` snippet on the site, or send events server-side via `POST /v1/ads/conversions`. The check `installed` is derived from `lastFiredTime`.  OpenAI Ads: creates an OpenAI pixel AND provisions a Conversions API key for it in the same call (`adAccountId` is required by this endpoint but ignored — one API key maps to exactly one ad account, so there's nothing to select). Returns 422 (`FEATURE_NOT_AVAILABLE`) if the ad account isn't enabled for pixel management; contact your OpenAI partner representative to enable it. There is no delete API for OpenAI pixels. If the pixel is created but the Conversions API key provisioning then fails, the pixel is left live on OpenAI (it cannot be cleaned up) and the error message names the surviving pixel id and warns against retrying, since a retry would create a second, orphaned pixel.  NOT idempotent on either platform: each call creates a new pixel (and, for OpenAI, a new Conversions API key plus, with `defaultEventType`, a new conversion event setting). Do not retry blindly on timeout. Meta (platform `metaads`) and OpenAI Ads (platform `openaiads`); other platforms return 405. 
   # @param account_id Ads SocialAccount id (platform `metaads` or `openaiads`).
   # @param create_tracking_tag_request 
   # @param [Hash] opts the optional parameters