Changelog

​

Platform refusals now return 422 with the reason, instead of an empty 502

• Refusals now return 422 with the platform’s reason in error.message. This covers the social account, published post, WhatsApp, Google Business, Reddit, reviews, ads, SEO, avatar and video AI endpoints. The error code values are unchanged (PLATFORM_ERROR, PLATFORM_UPSTREAM_ERROR, PROVIDER_ERROR, CREATE_FAILED, SEO_PROVIDER_ERROR, PLATFORM_DELETE_FAILED).
• 502 now only means the platform could not be reached at all. It still arrives without a body; retry after a short delay.
• AI generation failures (hooks, captions, B-roll, emphasis, thumbnails) return 422 with retryable: true, because a second attempt can succeed.
• PATCH /social/accounts/{account_id}/facebook/page saves each field separately. Facebook could store some fields and refuse a later one while the request reported a failure. A refusal now stops at that field and returns details.field and details.saved_fields, and the success response lists the fields saved.
• If your integration branches on 502, treat 422 with one of the codes above as a refusal to fix, not an outage. See Errors.

​

Connected accounts are billed by the day, and the rates are now documented

• What you pay - each connected social account is billed from your Developer wallet: $6 each for the first 10,$3 for accounts 11 to 100, $1 above that. Marginal, so 15 accounts held for a full month is$75. See Billing & Credits.
• Accounts are counted by the day. An account is billed for each day it stays connected, so a part month costs a part price: 15 accounts connected for half a month bills 7.5 account-months, $45. Connect on the 20th and you pay for eleven days. A full month costs the same as it always did.
• Disconnecting stops the charge; pausing does not. Pausing a profile stops it publishing, but its accounts stay connected and stay billable. If you no longer need an account, disconnect it.
• The Profiles tab and the Wallet tab in the Developer Dashboard now show your current rates, so what you pay is visible next to the accounts and next to the balance it is charged against.

​

Posts are screened against the Content Policy before they are created

• Prohibited content is refused at creation with 422 CONTENT_POLICY_VIOLATION, before anything is scheduled or published. The response links the Content Policy and the error is not retryable: edit the post, or contact support if you think the decision is wrong.
• Links to adult subscription platforms are refused. This is a check on the links in your caption and link field, so ordinary posts that merely mention such a service in passing are unaffected.
• Duplicate detection now looks across your profiles, not just inside one. The existing 24-hour duplicate guard only ever compared posts within a single workspace, which meant the same content sent to many profiles was invisible to it. Publishing identical content to several of your profiles in quick succession is still allowed and still publishes; it is now recorded for review.
• New error code CONTENT_POLICY_VIOLATION - HTTP 422, not retryable. See Errors.

​

Request limits now scale with your connected accounts, and posting is capped per account

• Requests per minute by connected accounts - 0 to 2 accounts get 60, 3 to 2,000 get 600, and 2,001 or more get 1,200. The limit moves as soon as you connect or disconnect an account. There is still no separate request limit per platform. A custom limit configured on your key continues to override the table.
• Analytics reads get a per-second ceiling - your per-minute allowance divided by 60, never below 6. It applies to every endpoint requiring the analytics:read scope, so a dashboard refresh cannot spend a whole minute’s budget in one burst and then stall. Exceeding it returns 429 with Retry-After: 1, and the rejected request does not count against your per-minute allowance.
• Each connected account now has a daily posting cap - Threads 250, Instagram 100, Facebook 100, X 50, Pinterest 25, TikTok 15 video plus 15 photo as separate allowances, and 50 for every other platform. Caps are per account, not a shared pool, so connecting more accounts raises your total throughput.
• Every account is also limited to 25 posts per hour across all platforms, so a day’s allowance cannot be published in a single burst.
• Capped accounts are held back, not the whole request. When you publish to several accounts at once, the accounts still under their caps go through and only the capped ones are refused, before the platform is called. The response names the limit that was reached and when to retry.
• Two error codes are now listed in Errors that were missing or wrong. RATE_LIMIT_EXCEEDED means you exceeded your own request limit. PLATFORM_RATE_LIMITED means a connected platform is temporarily limiting publishing for that account, is retryable after its cooldown, and had never been documented despite being returned by the publishing endpoints. The 429 example in the OpenAPI spec showed a code the API does not return and now shows RATE_LIMIT_EXCEEDED.

​

Facebook Reels over the daily limit are refused up front, with the reason

• Check the allowance - GET /social/accounts/{account_id}/facebook/reel-limit returns limit (30), used, remaining and next_available_at. used counts Reels published for the Page through the API or the app in the last 24 hours plus Reels already scheduled inside that window. next_available_at is set only when the Page is at the limit, and says when one more Reel fits. Reels posted to the Page outside this platform are not counted, so Facebook can still refuse a Reel. Facebook accounts only; any other account gets 422 VALIDATION_ERROR. Requires scope social:read.
• Reels over the limit are refused when you create or schedule them. A post with platform_options.facebook.type set to reel is refused when a selected Page would be at the limit at the post’s publish time (Reels published plus Reels already scheduled in the 24 hours before it). The response is 422 PLATFORM_DAILY_LIMIT_REACHED with a message naming the Page and when it can post a Reel again, and details carrying account_id, limit, used and next_available_at. Nothing is created.
• Editing is checked too. PATCH /social/posts/{post_id} refuses an update that would make a scheduled Reel go over the limit, with the same 422 PLATFORM_DAILY_LIMIT_REACHED and details. The post being edited is not counted against itself.
• A scheduled Reel that still hits the limit fails with the reason. That account’s result fails with error code PLATFORM_DAILY_LIMIT_REACHED and a message starting “Facebook daily Reel limit reached”. It is not retried automatically.
• New error code PLATFORM_DAILY_LIMIT_REACHED - HTTP 422, not retryable. Publish after details.next_available_at, or send the post as a different type. See Errors.

​

Manage a Facebook Page’s messages, profile picture and cover photo

• Read the messaging setting - GET /social/accounts/{account_id}/facebook/page/settings returns users_can_message, or null when Facebook did not report it.
• Turn messaging on or off - PATCH /social/accounts/{account_id}/facebook/page/settings with users_can_message. false hides the Message button and blocks replies in chats that already exist; true restores both.
• Set the profile picture - POST /social/accounts/{account_id}/facebook/page/picture with an image url. Facebook downloads the image itself, and no feed story or follower notification is created.
• Set the cover photo - POST /social/accounts/{account_id}/facebook/page/cover with url and an optional offset_y (0-100, default 50). No feed story or notification. It needs the business permission on the connection; connections without it get 403 CONNECTION_SCOPE_MISSING with reconnect_required: true, and reconnecting fixes it. A cover can be replaced through the API but not removed.
• Images are validated. JPG, PNG, GIF, BMP or TIFF, 10 MB at most, and a cover of at least 400 x 150 px. Anything else is a 422 VALIDATION_ERROR with details.field set to url and a details.reason saying why.
• GET /social/accounts/{account_id}/facebook/page now returns picture and cover, and its response fields are documented. cover is absent when the Page has no cover photo.

​

Every endpoint says which scope it needs, and 30 more are listed

• Every endpoint page now states its scope, in the same “Requires scope contacts:write.” form that some pages already carried by hand. The three endpoints needing two scopes say both, and /me, /me/usage, /me/balance and /me/billing now say plainly that any valid key works.
• The spec carries x-scopes on every operation, so tooling can read the requirement instead of parsing prose. It is a vendor extension, so it changes nothing for existing OpenAPI clients.
• Thirty endpoints that were live but missing from these docs are now listed. WhatsApp Flows (create, update, publish, deprecate, preview and the flow JSON), the WhatsApp sandbox sessions, the block list, and number bridging; automation versions, version restore and duplicate; POST /media/{media_id}/confirm; comment like, unlike and moderate; and deleting a direct message. They worked before, they were simply not documented.

​

Facebook Stories

• One photo or one video. Video is MP4, 9:16, up to 60 seconds; photo is up to 10MB.
• No caption. Neither story endpoint takes a message, description or overlay, so the post text is not published - put the wording in the media itself. The create response returns a warnings entry when a story post carries text.
• The media must be new. Meta refuses a photo or video that has already appeared in a published post, and refuses media served from its own CDN (fbcdn.net) - host your own copy.
• post_url comes back null. A story has no permanent page and expires after 24 hours; post_id is always returned.

​

link on a post is published instead of dropped

• link now reaches the platform. On a Facebook text post it publishes as a real link post, so Facebook renders the preview card for it.
• On a post that carries media, the URL is appended to the post text. The attachment is already the card there and Facebook’s publishing API has no link parameter for it, so the URL is kept in the copy rather than dropped. It is not added twice if your text already contains it.
• Platforms that cannot carry a link now tell you so. They come back in data.warnings on the create response, keyed by platform, instead of the link quietly disappearing for that leg of the post.
• platform_options.<platform>.link wins over a request-level link, so you can send one default and override it per platform.
• A malformed link is now a 422 rather than a silent drop. Links must be http/https, carry a host, and stay under 2,048 characters.

​

Facebook type: "feed" works, and an unknown post type now says so

• "feed" is now accepted, along with "video", "photo", "image", "text" (all the same as "post") and "reels" (the same as "reel"). Existing calls that used any of these start working with no change on your side. The same aliases apply to Instagram, plus "stories" for "story".
• A post type we cannot publish now returns 422 POST_TYPE_UNSUPPORTED, and the message lists the values that platform accepts. It used to be a 500 telling you to retry, which could never help.
• Facebook type: "story" is now refused. It was previously accepted and then published to the timeline instead - there is no Facebook Stories publishing behind it. Instagram stories are unaffected and still publish normally.

​

Ad metrics now cover one window on every platform

• Every platform now reports the same last 28 days. If you read these fields for Google campaigns, the values will drop - they were lifetime totals, not a recent window. TikTok and LinkedIn campaigns will show real figures for the first time.
• GET /ads/analytics gained a by_campaign block - the same per-campaign figures, scoped to whatever date_from/date_to you ask for. Use it for any window other than the fixed 28 days, or to compare campaigns over a specific period.

​

Bulk campaign status: 50 per call, and a 207 for partial batches

• The per-call limit is now 50 campaigns, down from 100. Sending more returns 422. The old limit was one this endpoint could not actually honour: every id costs a live write to the ad platform, and Meta’s per-ad-account budget is spent long before 100 - so the tail of a large batch came back Meta rate limit reached and looked like your fault. 50 fits inside that budget, so every id you send can actually succeed. Split larger jobs across calls.
• A partly-failed batch now answers 207, not 200. 200 means every id succeeded; 207 means at least one didn’t. The body shape is unchanged either way, so you can keep reading per-item results exactly as before - but you no longer have to parse the body to find out whether anything failed.

​

DELETE requests that send a body must declare Content-Type

​

Ads analytics, audience creation, targeting search, Boost Post, and Click-to-Message/Call

• GET /ads/analytics - spend/impressions/clicks/conversions summary, a by-platform breakdown, a daily spend chart, and period-over-period trends.
• POST /ads/audiences - real audience creation on Meta (Custom/Lookalike) or Google (remarketing/CRM user lists), not just the read-only listing from earlier today.
• GET /ads/targeting-search - Meta interest type-ahead, for building a campaign’s targeting.interests.
• Boost Post - POST /ads/campaigns now accepts creative.object_story_id ("{page_id}_{post_id}", from the new GET /ads/pages/{page_id}/posts) to turn an existing organic Page post straight into an ad - no new creative to build.
• Click-to-Messenger / Click-to-Call - settings.destination_type: "messenger" with a MESSAGE_PAGE CTA opens a Messenger chat instead of a link; a CALL_NOW CTA plus settings.phone_number (E.164) dials a number instead.

​

Ads API - campaigns, ad sets, ads, audiences, pixels, lead forms, and creatives

• Campaigns, ad sets, ads - full CRUD plus pause, resume, duplicate, and archive on each, and POST /ads/campaigns/bulk-status for pausing or resuming up to 100 campaigns in one call (per-item results, never all-or-nothing).
• Creating a campaign - POST /ads/campaigns with platform: meta and a page_id launches a real campaign on Meta. Every other platform, or Meta without a page_id, creates a local draft - only Meta has live launch wiring today.
• Audiences, pixels, lead forms - GET /ads/audiences and GET /ads/pixels are read-only mirrors of what’s already on the platform. POST /ads/lead-forms creates a real Meta Instant Form (standard question fields, requires a privacy policy URL).
• Creatives - a standalone asset library independent of any specific ad. POST /ads/creatives takes an already-hosted file_url - upload bytes through POST /media/upload-direct first, this endpoint doesn’t handle raw uploads.
• Accounts & diagnostics - GET /ads/accounts lists connected ad accounts; GET /ads/accounts/diagnostics adds live per-account API rate-limit usage and last-sync health. GET /ads/audit-log supports campaign_id to scope the log to one campaign and everything under it.
• Estimate - POST /ads/estimate returns a real Meta audience-size range for a targeting spec before you launch. Every other platform returns available: false rather than an error, so you can branch on it cleanly - Google’s forecasting tools need a keyword seed this endpoint doesn’t collect, TikTok has no published estimate API for standard campaigns, and LinkedIn’s geo-targeting IDs have no stable public mapping to resolve against yet.

​

Media presign now works, plus a confirm step

​

WhatsApp sandbox and bring-your-own-number bridge

• Sandbox - test WhatsApp end-to-end without connecting your own number. POST /whatsapp/sandbox/sessions activates a phone against a shared SmartlyQ-owned number (they reply to prove ownership), then POST .../sessions/{session_id}/send re-fires the locked sandbox template to actually see a message land. 50 sends/24h, one phone per user at a time.
• Number bridge - already bought a phone number through SmartlyQ? POST /whatsapp/numbers/{sender_id}/bridge adds it to your existing WhatsApp Business Account connection, following Meta’s real add → request-code → verify → register sequence. Once linked it’s a normal connected WhatsApp number, usable anywhere account_id is accepted.

​

WhatsApp Flows and Block Users

• Flows - build native in-chat forms (booking, surveys, lead capture) without leaving WhatsApp. POST /whatsapp/flows creates a DRAFT flow, PUT .../flows/{flow_id}/json uploads its screens, POST .../flows/{flow_id}/publish makes it sendable, and POST /whatsapp/messages with type: "flow" sends the opening CTA. Full CRUD plus a preview URL (GET .../flows/{flow_id}/preview) and deprecate.
• Block users - GET / POST / DELETE /whatsapp/block-users blocks or unblocks WhatsApp users on a connected number, and lists who’s currently blocked (up to 64,000, cursor-paginated). Meta only allows blocking someone who messaged your business in the last 24 hours; other targets come back in a failed array without failing the rest of the batch.

​

Comment moderation, message delete, and automation version history

• Comment moderation - POST /social/comments/{id}/moderate approves or rejects a comment (with an optional author ban). YouTube only - uses the same underlying endpoint POST .../hide already used, just the full status set.
• Comment likes - POST / DELETE /social/comments/{id}/like. Facebook only - Instagram’s Graph API has no comment-like edge.
• Delete a sent message - DELETE /social/conversations/{conversation_id}/messages/{message_id}. X and Bluesky only (Messenger, Instagram, and WhatsApp have no unsend API for a business-sent message). On Bluesky this removes the message from your side of the conversation only - their chat API has no unsend-for-everyone, and the response says so explicitly via a note field.
• Automation duplicate - POST /automations/{id}/duplicate. Copies the graph into a new automation, always starting as draft.
• Automation version history - GET /automations/{id}/versions (list), GET .../versions/{version} (one, with its graph), POST .../versions/{version}/restore. A snapshot is taken automatically before every graph edit, so you can always see - and undo - past changes. Restoring is itself just another edit, so it’s never destructive.

​

WhatsApp is now priced per destination and message type

"pricing": { "category": "utility", "market": "United States", "calling_code": "1", "rate": "0.003600" }

• You are charged only for a message accepted for delivery. A send rejected by WhatsApp is refunded automatically, and validation failures are never charged at all.
• Free-form replies are billed as service, priced at the destination market’s utility rate, so a service reply to the US and one to Germany cost different amounts just like templates do.

​

Per-platform management: pages, boards, playlists, mentions, flairs

• Facebook page - GET and PATCH /social/accounts/{account_id}/facebook/page. Read the page’s about, description, category, contact details, address, hours and follower counts; edit the ones you want, sending only what changes.
• Pinterest - POST /social/accounts/{account_id}/pinterest/boards creates a board to pin into.
• YouTube - PATCH /social/accounts/{account_id}/youtube/playlists/{playlist_id} renames a playlist, edits its description, or changes its visibility. YouTube’s own update replaces every field you submit, so we read the playlist first and merge rather than blanking what you left out.
• Mentions - GET /social/accounts/{account_id}/mentions lists posts where a Facebook page or Instagram account was tagged, and POST .../mentions/{mention_id}/reply answers one. X keeps its own richer endpoint.
• Reddit flairs - GET /social/accounts/{account_id}/reddit/subreddits/{subreddit}/flairs. Many subreddits reject a submission with no flair; read the flairs, then pass the id as platform_options.reddit.flair_id when you post.
• WhatsApp template library - GET /whatsapp/template-library browses Meta’s prewritten, pre-approved templates, and POST /whatsapp/templates/from-library adopts one under your own name. This skips the draft-and-wait-for-review cycle.

​

Developer logs, YouTube Analytics, webhook replay

• GET /analytics/youtube/channel-insights - views, watch time, average view duration and percentage, subscribers gained/lost, engagement.
• GET /analytics/youtube/daily-views - the same headline metrics broken down by day.
• GET /analytics/youtube/video-retention - the retention curve for one video, plus how it compares with similar videos.
• GET /analytics/youtube/demographics - viewer split by age bracket and gender.

​

WhatsApp sends are now billed

​

WhatsApp Business messaging (Phase 1)

• Connect a WhatsApp Business number - POST /social/connect/whatsapp with { waba_id, phone_number_id, access_token }.
• Send - POST /whatsapp/messages: text and media (session messages, inside the 24-hour window) and approved templates (any time).
• Receive - inbound messages and delivery receipts arrive on your webhooks and populate the in-app Inbox. New events: message.delivered, message.read, message.failed (joining message.received).
• Manage - list/create message templates (/whatsapp/templates), read/update the business profile (/whatsapp/business-profile), and list phone numbers (/whatsapp/phone-numbers).

​

WhatsApp: interactive buttons, reply threading, reactions, location, contacts

• interactive_buttons - up to 3 tappable reply buttons; the customer’s tap arrives as a normal inbound message.
• interactive_list - a tappable list picker, up to 10 rows across sections.
• location - share a pin (latitude/longitude, optional name/address).
• contacts - share one or more contact cards.
• reaction - react to (or remove a reaction from) any message. Inbound reactions from the customer now arrive on the reaction.received webhook instead of being dropped.
• context_message_id - pass on any send type to thread it as a quoted reply under a prior WhatsApp message id.

​

X reply threads with media

​

X (Twitter) comment threads, and more

• X comment threading fixed - replies on X posts now nest correctly. Previously the reply tree never linked (we keyed on the replied-to user instead of the parent tweet), so X threads came back flat. Reply nesting now works for every platform except Pinterest (whose comments are inherently flat). This fix applies to the app’s comment view as well as the API.
• GET /social/comments/{post_id} - fetch one post’s comments as a nested thread by id, instead of filtering the full comments list.
• PUT / DELETE /contacts/{id}/fields/{slug} - set or clear a single contact custom field by its slug, without sending the whole attributes object.
• GET /me/billing - a read-only superset of /me/balance: balance breakdown, monthly cycle reset, auto-recharge config, and card-on-file status with an at-a-glance payment.status.

​

Profile update and direct media upload

• PATCH /profiles/{id} - rename a profile or change its external_id without recreating it (renaming keeps the backing workspace name in sync). Fills the last gap in profile management.
• POST /media/upload-direct - upload a file in a single multipart/form-data request, no presign round-trip. Stored straight to your media library and returned in the same shape as GET /media/{id}; the type is detected from the file’s actual bytes, up to 200MB.

​

10 new webhook events

• Posting - post.scheduled (a post was queued for later), post.cancelled (a scheduled post was deleted before publishing), post.recycled (a recycling chain spawned its next occurrence), and post.external.created / post.external.updated for posts authored natively on the platform and picked up by external sync.
• Inbox - message.sent (outbound DM delivered), conversation.started (a new thread opened), reaction.received (an emoji reaction added or removed).
• Reviews - review.new and review.updated for Google Business reviews and replies.

​

Idempotent creates, per-platform stagger, richer platform options

• Idempotency keys - send X-Idempotency-Key (or X-Request-Id) on POST /social/posts / /schedule; a retry with the same key returns the original post (200, idempotent_replay: true) instead of double-posting. Backed by a unique constraint, so even concurrent retries can’t create twice. Works alongside the existing 24-hour duplicate-content guard (409 DUPLICATE_CONTENT + allow_duplicates). New Idempotency guide.
• Per-platform stagger - on the schedule endpoint, any platform can carry its own scheduled_time inside platform_options: one call, each network publishing at its own moment (response lists the created staggered[] legs).
• Platform options, documented and extended - new Platform options guide covering every per-platform key. Newly added: Telegram parse_mode/silent/disable_link_preview/protect_content, Reddit flair_id/flair_text, YouTube tags/category_id/contains_synthetic_media (AI disclosure), Instagram share_to_feed for Reels.

​

Connect Telegram by API, Discord headlessly

• Telegram credential connect - POST /social/connect/telegram with { "bot_token", "chat" } connects the channel immediately (Telegram has no OAuth; this is the same verify-then-save flow as the dashboard modal: bot verified with Telegram, posting rights required, private chats rejected, plan limit enforced, token encrypted at rest). Built for agencies automating workspace onboarding.
• Discord headless connect - POST /social/connect/discord mints the server-webhook authorize URL like any OAuth platform.

​

Telegram and Discord publishing

• telegram - publishes through your own bot (created with @BotFather) to its channel or group: text up to 4,096 characters, single media or 2-10-item albums sent by URL. Connected from the dashboard’s Social Accounts page.
• discord - publishes through a channel webhook on your server: text up to 2,000 characters, up to 10 images as embeds, posting under your workspace brand’s name and logo when one is set.

​

Auto-transcode, publish progress, and exact failure reasons

• Auto-transcode - media that a platform would reject for a fixable reason is converted automatically before publishing: video that isn’t H.264/AAC MP4 is re-encoded (web-optimized, moov-front), frame rates are brought into each platform’s documented range (raised to 30fps below TikTok/Instagram’s 23fps floor, capped at 60fps), oversize videos are shrunk under the platform’s byte cap, and images in formats a platform rejects are converted (e.g. WEBP to PNG for LinkedIn). What was fixed is reported per platform in the post’s post_urls._transcodes and in the transcoded[] list on post.published / post.partial / post.failed webhook payloads. Changes that would alter your content - trimming duration, cropping aspect ratios - are never made automatically; those still return a precise error telling you what to change.
• Publish progress - posts now expose publish_stage (validating → processing_media → publishing) while a publish is running, so GET /social/posts/{id} shows where a slow publish is instead of a bare processing.
• Exact failure reasons, end to end - a failed post always carries its reason now: whole-post failures persist an explanation in post_urls._errors, immediate (non-scheduled) posts store per-platform permalinks and errors just like scheduled ones, and webhook failure payloads include error.detail with the exact pre-publish reason (e.g. "Twitter/X caption is 312 characters; the limit is 280. Trim 32 characters and retry.") whenever the failure came from SmartlyQ’s own checks.

​

Rich DMs, comment-to-DM automations, connection selection, deep insights

• Structured DMs - POST /social/conversations/{id}/messages now takes buttons (Facebook button template, up to 3 links) and quick_replies (Facebook + Instagram chips, up to 13), plus a typing indicator at POST .../typing.
• Comment-to-DM - POST /social/comments/{comment_id}/private-reply DMs the comment’s author (Meta private replies, FB + IG). New comment_created automation trigger + action.private_reply runner action: build “comment X gets an automatic DM” flows in the automation builder.
• Messaging surfaces - Messenger persistent menu and Instagram ice breakers, full CRUD under the account.
• Connection selection - GET .../connect-options + POST .../connect-select re-point a Google Business connection at any location of its parent account; platforms with entity-bound tokens report why they can’t switch without reconnect.
• Deep insights - GET .../facebook/page-insights (any Meta page metric, passthrough) and GET .../instagram/audience (follower demographics by city/country/age/gender).

​

Subreddit eligibility, X mentions, contact channels

• Subreddit check - GET /social/accounts/{account_id}/reddit/subreddits/{subreddit} returns the community’s rules of engagement plus a computed can_post verdict for your connected account (banned? restricted? what submission kinds?).
• X mentions - GET /social/accounts/{account_id}/x/mentions lists recent posts mentioning the account, with engagement metrics.
• Contact channels - GET /contacts/{id}/channels shows which channels a contact actually communicates on, with volume and last activity.
• Custom field update - PATCH /custom-fields/{id} edits a field definition (the key stays immutable).
• Place-action update - PATCH /social/accounts/{account_id}/gmb/place-actions changes a link’s URI in place.

​

Google Business Profile management

​

Webhooks scopes are now grantable

​

Edit published posts, external sync, live insights

• Edit published - POST /social/posts/{post_id}/edit edits the post natively on the platform. Facebook works today; X (paid-tier API) and Reddit (extra scope) report unsupported per platform instead of failing.
• YouTube metadata - POST /social/posts/{post_id}/update-metadata updates title/description/tags, adds to a playlist, and sets a custom thumbnail after publish.
• External post sync - POST /social/posts/sync-external imports posts published natively on Facebook, Instagram, Threads, YouTube or TikTok (per-account opt-in); they appear in GET /social/posts?status=external with analytics.
• Live account insights - GET /social/accounts/{account_id}/insights returns platform-fresh follower/impression/reach/engagement metrics for every provider-backed platform.

​

Per-platform post options, X retweets, story insights, safe retries

• platform_options - create, schedule, and bulk rows now accept the same per-platform options object the web composer uses: TikTok privacy/duet/stitch, per-platform caption overrides, custom video thumbnails, and more. Publish handlers consume it directly.
• X engagement - POST /social/accounts/{account_id}/x/retweets and its DELETE counterpart retweet/un-retweet with the connected account.
• Story insights - GET .../instagram/stories/{story_id}/insights with a passthrough metrics parameter.
• Delete review reply - DELETE /reviews/{review_id}/reply removes the reply on Google Business.
• Idempotency, documented - every write endpoint has always honored X-Idempotency-Key (24h replay window, never double-billed); it is now documented in the API intro.

​

Reddit research tools, Instagram stories, Facebook reactions

• Reddit - four research endpoints under /social/accounts/{account_id}/reddit/: search (optionally restricted to a subreddit), feed (hot/new/top/rising), subreddits (your subscriptions), and subreddits/{subreddit}/rules - check the rules before you submit.
• Instagram stories - GET /social/accounts/{account_id}/instagram/stories lists the account’s currently live stories.
• Facebook reactions - GET /social/accounts/{account_id}/facebook/post-reactions returns the per-type breakdown (like, love, wow, haha, sad, angry, care) for any published post.

​

Per-platform lookups

• Pinterest boards - GET /social/accounts/{account_id}/pinterest/boards
• YouTube playlists - GET /social/accounts/{account_id}/youtube/playlists
• Instagram publishing limit - GET /social/accounts/{account_id}/instagram/publishing-limit (daily quota total/remaining)
• Google Business performance - GET /social/accounts/{account_id}/gmb/performance?days=28 (impressions by surface, deltas, daily series)
• Google Business search keywords - GET /social/accounts/{account_id}/gmb/search-keywords

​

Automations API + contact bulk import

• Operate your automations - new /automations group: list and inspect automations built in the visual builder, activate/pause them, queue a manual run with POST /automations/{automation_id}/trigger (optional JSON payload), and read run history down to per-step execution logs.
• Bulk import - POST /contacts/bulk imports up to 100 contacts through the same email/phone upsert as single create - re-importing a file is idempotent, with per-row created/updated/failed results.
• Delete - DELETE /contacts/{id} soft-deletes (recoverable from Deleted contacts in the app).

​

Inbox: search, detail, archive

• Search - GET /social/conversations/search?q= scans participant names and message content across the whole inbox and returns the latest matching message per conversation.
• Detail - GET /social/conversations/{conversation_id} adds a single-conversation view with incoming/outgoing counts.
• Archive - PATCH /social/conversations/{conversation_id} with { "status": "archived" } (or "open" to restore).
• Drill-down analytics - GET /analytics/inbox/conversations (+ /{conversation_id}) closes out the inbox analytics suite with per-conversation volume and response times.

​

Reviews API

• List - GET /reviews with rating / reply-status / account filters.
• Reply - POST /reviews/{review_id}/reply publishes your reply on Google Business.
• Sync - POST /reviews/sync pulls fresh reviews on demand, per account or workspace-wide.

​

Inbox analytics

​

Analytics that answer questions

• Daily metrics - GET /analytics/daily-metrics: per-day aggregates + platform breakdown + posts published.
• Best time to post - GET /analytics/best-time?timezone=...: 7x24 engagement heatmap and your top 5 slots.
• Post timeline - GET /analytics/posts/{post_id}/timeline: every metric snapshot for one post, per platform.
• Content decay - GET /analytics/content-decay: average share of final engagement by post age (day 0-13).
• Posting frequency - GET /analytics/posting-frequency: weekly post count vs average engagement.

​

Account groups and profile moves

• Account groups - full CRUD under /social/account-groups: name a set of connected accounts (a client, a brand) and address it with one id. Up to 50 groups per workspace, 100 accounts per group; membership is validated against your workspace on every write.
• Move to profile - POST /social/accounts/{account_id}/move relocates a connected account between your developer workspace and your profiles (profile_id: 0 moves it back). Requires social:write + profiles:manage, developer context only, and refuses with 409 while the account has scheduled or in-flight posts.

​

Account insights

• Bulk health - GET /social/accounts/health reports every connected account’s token health in one call: healthy / expiring / expired / paused tallies plus per-account detail. No more N+1 health polling.
• Follower stats - GET /social/accounts/follower-stats?days=30 returns daily follower history, growth, and growth percentage per account from the platform’s analytics snapshots.
• Rename - PATCH /social/accounts/{account_id} updates the account’s display name.
• TikTok creator info - GET /social/accounts/{account_id}/tiktok/creator-info surfaces live privacy levels, comment/duet/stitch availability, and max video duration - the fields TikTok requires you to show before posting.

​

Bulk scheduling and duplicate protection

• Bulk schedule - POST /social/posts/bulk schedules up to 50 posts in one call, from a JSON posts array or an inline csv string (header: content, platforms, account_ids, scheduled_time, media_urls, link). Billed one post unit per row x platform. A structural problem in any row rejects the whole batch with 422 before anything is created - and the charge is refunded.
• Free batch dry-run - POST /social/posts/bulk/validate returns a per-row report (structure, per-platform caption/media limits, duplicate check) without creating or billing anything.
• 24h duplicate-content guard - POST /social/posts and POST /social/posts/schedule now reject content identical to a post created in the same workspace within the last 24 hours with 409 DUPLICATE_CONTENT (charge refunded). Pass allow_duplicates: true to override. This catches retry loops and mis-wired crons before they spam your channels.

​

Evergreen post recycling

• Recycle on schedule - POST /social/posts/schedule now accepts an optional recycle object: { interval_hours, max_repeats?, until? }. After each occurrence publishes, the next one is scheduled automatically. A bound is required (max_repeats up to 100 and/or until up to 2 years out) - no unbounded chains.
• Stop a chain - DELETE /social/posts/{post_id}/recycle clears the config across the whole chain and cancels any not-yet-published occurrences back to draft. Works from any post in the chain.
• Occurrences inherit content, media, accounts, UTM tags, and approval status; GET /social/posts/{post_id} shows recycle_count and recycle_parent_id for lineage.

​

Pre-flight validation

• Validate a post - POST /social/validate/post dry-runs the exact checks the create path uses and returns a per-platform report: character count vs. the platform’s caption limit, required-media rules, and media extension screening. Nothing is created.
• Validate a media URL - POST /social/validate/media confirms a URL is publicly reachable and reports its content type, byte size, and detected kind (image/video). Private and internal hosts are rejected.

​

Posting queues and unpublish

• GET/POST /social/queues, GET/PUT/DELETE /social/queues/{queue_id} - manage queues (slot map {"Mon": ["09:00"], ...} + IANA timezone)
• GET /social/queues/{queue_id}/next-slot and /preview?count=N - see upcoming open slots
• POST /social/posts/schedule now takes queue_id instead of scheduled_time: the next open slot is resolved server-side and the post occupies it (FIFO), so concurrent calls fill consecutive slots
• Bonus: scheduled_time now honors an optional timezone field (previously UTC-only)

​

Webhooks: update, test, and delivery logs via API

• PUT /webhooks/{id} - change the URL or subscribed events, or pause/resume deliveries (status: active | paused); re-activating also recovers an endpoint auto-paused after repeated failures
• POST /webhooks/{id}/test - sends a webhook.test event through the real signing pipeline and returns the result synchronously (delivered, response_code, response excerpt)
• GET /webhooks/logs - paginated delivery log across your endpoints with the full envelope, response code/body excerpt, attempt count, and next retry time; filter by webhook_id, event, or status
• job.completed / job.failed now actually fire - these events were in the catalog but had no emit point; every async job now emits exactly once on its terminal transition with {job_id, type, status, error?}
• Stricter validation: POST /webhooks and PUT /webhooks/{id} reject unknown event names outright instead of silently dropping them
• Guardrail: webhook routes reject the X-Profile-Id header - webhooks live on your developer workspace and receive profile events via fan-up

​

Webhooks: unified 25-event catalog with machine-readable schemas

• The Webhooks guide now documents the complete 25-event catalog (posting, accounts, inbox, jobs, billing & keys, CRM) with the data fields each event carries
• Every event now ships a JSON payload schema in the OpenAPI spec’s standard webhooks object - SDK generators and AI agents can consume delivery shapes directly from openapi.json
• POST /webhooks now documents the exact allowed events values (enum) instead of a free-form string array
• Corrected legacy event names that appeared in older docs (social.posted → post.published, wallet.low → balance.low); the delivery envelope is documented as {id, event, created_at, data} with the X-SmartlyQ-Event-Id dedupe header
• Documented previously-missing delivery semantics: Retry-After honored on 429 (capped 1h), dead-letter after the 5th attempt, auto-pause after 10 consecutive failures, 90-day delivery retention, 10 webhooks per workspace

​

Profiles: build your own multi-tenant product

• POST /profiles, GET /profiles, GET /profiles/{id}, GET /profiles/{id}/accounts, pause / resume / delete
• POST /profiles/{id}/connect-link - hosted, single-use connect page for your customer
• POST /profiles/{id}/connect/{platform} - raw per-platform OAuth URLs for your own UI
• X-Profile-Id header on existing endpoints - data scopes to the profile; billing, rate limits and logs stay on your account
• GET /me/account-billing - live billable-account count and charge estimate
• Per-account monthly billing from your API wallet: $6 each for accounts 1-10, $3 for 11-100, $1 from 101 up
• New webhook events account_billing.charged / account_billing.failed, plus every in-profile event now fans up to your webhooks with profile_id attached
• New scopes: profiles:read, profiles:write, profiles:manage

​

More platform targets + pre-publish validation

​

SaaS plan reads + bulk sub-account actions

• GET /saas/plans and GET /saas/plans/{id} - list the SaaS plans configured on your account
• GET /workspaces/{id}/subscription - a workspace’s current plan and status
• GET /workspaces/{id}/wallet - a workspace’s credit wallet balance
• POST /workspaces/bulk - pause, resume, or delete many workspaces in one call (SaaS-plan gated)

​

Workspace lifecycle management

• POST /workspaces - provision a new sub-account
• GET /workspaces and GET /workspaces/{id} - list and inspect
• POST /workspaces/{id}/pause and /resume - suspend and restore access
• POST /workspaces/{id}/disable-saas - detach a workspace from your SaaS plan
• DELETE /workspaces/{id} - guarded delete with async teardown

​

CRM API: contacts, opportunities, custom fields

• Contacts: create, list, get, update, tag management, notes, POST /contacts/{id}/enroll (enroll in an automation), and POST /contacts/{id}/messages (log a message to the timeline)
• Custom fields: GET/POST /custom-fields, DELETE /custom-fields/{id}
• Pipelines and opportunities: full CRUD plus POST /opportunities/{id}/status for stage moves
• Outbound CRM events are delivered through your existing webhooks

​

Presentations API

• POST /presentations/generate - builds a complete deck (3 to 12 slides, language and tone options) and returns the presentation id plus edit and share URLs
• GET /presentations, GET /presentations/{id}, DELETE /presentations/{id}

​

Async SEO lookups

​

AI visibility endpoints

• POST /seo/ai-audit - audit how visible a domain is to AI assistants; also delivers a PDF report by email
• POST /seo/brand-lookup - how a brand appears across search and AI surfaces
• POST /seo/prompt-explorer - discover the prompts where a domain is (or is not) cited

​

Shorts + video editing AI

• POST /shorts/generate - split a long video (or a source URL) into ranked viral clips; poll GET /shorts/{uid}
• POST /videos/hook - a scroll-stopping overlay line for a video
• POST /videos/broll-suggest and POST /videos/emphasis - B-roll and emphasis suggestions from a word-level transcript
• POST /videos/viral-thumbnail - generate a thumbnail from a title
• POST /content/caption - platform-tuned social captions

​

Logs overhaul

​

Billing correctness hardening

​

Webhooks: unified event catalog + signed envelope

​

SEO API launch

​

Playground + automatic refunds

• The in-app API Playground can now run real requests against any of your keys (scopes, billing, and rate limits all apply; write calls need explicit confirmation)
• Charges are taken upfront and automatically refunded if the request fails
• Wallet ledger rows now carry human-readable descriptions

​

Headless connect for all 13 platforms

• GET /social/connect/{platform} - start a headless OAuth connect for any of the 13 platforms and poll connection status
• GET/POST /webhooks and DELETE /webhooks/{id} - manage webhook subscriptions from the API, including a deliveries index and dead-letter view
• Post results now surface per-platform publish failure reasons
• Error envelope extended with retryable, fix, and docs_url fields
• Platform posting rate limits are enforced at create time with clear errors

​

Comments, DMs, and account lifecycle

• Comments: GET /social/comments, POST .../reply, POST .../hide, DELETE /social/comments/{id}
• Inbox: GET /social/conversations, GET/POST .../messages, POST .../read
• Accounts: GET .../health, GET .../reconnect-url, POST .../pause, POST .../resume, DELETE /social/accounts/{id}
• POST /social/posts/{post_id}/retry - retry only the platforms that failed