SynqDocs
Changelog

API and MCP changelog

What changed in each version of the management API's and the account API's contracts, and in the MCP server's tools.

Every change to Synq's public contracts, a day at a time, newest first, each dated by the day it reached Synq's code: the management API, the account API and the MCP server's tools. Under each day, each version lists its changes one a line. For what's new in Synq as a whole, in plain words, read What's new on Synq's website. Download each contract to see it whole: the management API's, also at https://api.synq.build/v1/openapi.json, and each brand's account API at its issuer's /me/openapi.json.

A contract's version is its OpenAPI document's info.version, and the path carries its major (/v1). The minor rises with an addition (a route, an optional field, an answer or an error code) and the patch with a fix. Until Synq launched, on 2026-10-21, a breaking change was made in place and raised the minor; since then, a change that would break a caller is a new major on a new path, beside /v1. A version can reach Synq's code a little before it reaches production, which serves the version its info.version says.

Management API

2026-11-17

1.222.0

  • An API's identity_claims takes wallets: the person's wallets as { address, chain, primary }, primary first, in its access tokens (at most 10, with wallets_truncated: true when they have more) and in its API key checks (every one), so the API authorizes by wallet from the token alone. Apps get the same with the OpenID scope wallets, in the ID token and at userinfo.

1.221.0

  • PUT, POST …/announce and POST …/move on /v1/orgs/{org}/telegram-groups/{group}/window take topic_link in place of topic: any forum topic, by a link to a message in it, which Synq keeps and answers by its id in topic.
  • move's topic is optional, one of the two is sent.
  • The window's topics keeps a topic from any message in it, and a topic's name is null until a message names it, which a topic whose first message is gone never does until it's renamed.

1.220.2

  • A Telegram group window's move is a union of TelegramGroupWindowMove and null, so the component itself is never null where it is referred to (1.218.0 made the component nullable).
  • What is sent doesn't change.

1.220.1

  • The community messages' look's icon_url, a Discord embed's author circle, is the brand's icon, else its logo only where that logo is square, else null, and the embed shows the name alone: a wide wordmark is never cut into the circle.
  • A brand's icon_url says so.

1.220.0

  • An org may start with no brand, to receive one moved from another org: POST /v1/orgs takes first_brand: false, which makes it with none and no issuer_slug (400 at issuer_slug with both). The org's default_brand_id, in GET /v1/orgs, POST /v1/orgs, GET /v1/orgs/{org} and PATCH /v1/orgs/{org}, is null while it has no brand: read it as "no brand yet". The first brand made there (POST /v1/orgs/{org}/brands) or moved in becomes its default, with is_default: true.

1.219.0

  • POST /v1/orgs/{org}/brands/{brand}/transfers takes move_now and preview_hash: the owner of both orgs moves the brand at once, asked and accepted as them in one step.
  • GET …/brands/{brand}/transfer-preview takes to_org, new_default_brand and close_from_org, and for an org the person owns too answers its side with to_org and preview_hash.

1.218.0

  • POST /v1/orgs/{org}/telegram-groups/{group}/window/move moves an announced window's countdown to another forum topic, or General: topic is the new one at once, every later reminder goes there, and within minutes, outside quiet hours, Synq posts and pins the countdown there, unpins the one it left and edits that to point to it.
  • The window's move says what waits and waits_until when quiet hours hold it.
  • PUT …/window's 409 for topic after announcing names the move.
  • The audit action and webhook event telegram_group.window_moved.
  • The MCP operation move_telegram_window.

2026-11-16

1.217.0

  • POST /v1/orgs/{org}/billing/plan, an upgrade whose payment the person's bank wants to confirm (3-D Secure), answers 402 payment_requires_action as ending a trial does: hosted_invoice_url, the open invoice and expires_at, and nothing changes until they confirm it, then the upgrade applies, with the email and org.plan_changed by whoever asked.
  • A declined card is still payment_failed, and any other change calls a waiting payment off. The payment's fields, in that problem and in GET …/billing's payment_requires_action (now for a paid plan's upgrade too), add change (end_trial or change_plan), plan and interval: what paying does.

1.216.0

  • An app's source adds api, for one the org made with this API (an org API key, an MCP host, npx synqauth init), beside dashboard, for one made in the dashboard.
  • POST /v1/orgs/{org}/discord-servers/{server}/roles/{role}/window/announce and POST /v1/orgs/{org}/telegram-groups/{group}/window/announce post in the background, so the caller may go, and answer 202 with the window's new announce_queued_at.
  • The window's announce_failure says why when nothing was posted.

1.215.0

  • GET /v1/orgs/{org}/audit-log's resource, a member's or former member's id, also finds the invitations to their address and an ownership they handed on, and the org's own id everything about the org, its handover included.
  • A PATCH sent enabled or disabled names the resource's own …/enable and …/disable, and a key that is a word of a missing field's name (type for app_type) gets its "Did you mean".

1.214.0

  • POST /v1/orgs/{org}/billing/trial/end, when the person's bank wants to confirm the payment (3-D Secure), answers 402 payment_requires_action with hosted_invoice_url, Stripe's page where they confirm it, the open invoice and expires_at: nothing is charged yet and the trial carries on, and once they confirm it Stripe takes the payment and the trial ends, with the email and org.trial_ended, by whoever asked. GET …/billing says payment_requires_action while it waits. A declined card is still payment_failed.

1.213.0

  • GET /v1/orgs/{org}/webhooks answers warnings: brands_limited when the credential has org.webhooks.view in some brands alone, so the list leaves out webhooks for All brands and for other brands.
  • Turning a webhook off (POST …/webhooks/{webhook}/disable) fails its deliveries still waiting at once, with no next_attempt_at.

1.212.0

  • POST /v1/orgs/{org}/billing/trial/end ends a trial now and pays for its plan: Stripe charges the first period today on the saved card, nothing prorated, and the answer has the paid invoice.
  • A declined card is payment_failed and the trial carries on.
  • Refused with no_trial, card_required, or conflict while the trial is set to end or a move down waits for its end. POST …/billing/trial/end/preview says what it charges today, on which card, and when the next charge is. The audit action and webhook event org.trial_ended.

1.211.0

  • POST /v1/orgs/{org}/billing/plan with the plan the org is on keeps it: it renews a plan set to end, bringing back a downgrade that end called off, or calls off a waiting downgrade (applies: now; still conflict when nothing waits).
  • GET …/billing says called_off_change while canceling, the downgrade the end called off, which renewing in the billing portal brings back too.
  • The plan preview's action: keep, and its quotas.audit_retention_days.
  • The org's owners and admins get an email for every plan change.

1.210.0

  • A brand move's preview says, on the brand's own org's side, roles_ending: how many of its members, and of its pending invitations, hold a role in the brand itself, which ends at the move (null on the target's side).
  • A sending domain's pending_dns with every required record found is checked again 1, 5 and 15 minutes and an hour after first finding them all.

2026-11-15

1.209.0

  • A body that isn't JSON is 400 invalid_json, saying where it broke, by line and column, and what JSON needs there, and a body sent without Content-Type: application/json (as another type, or with none) is 415 unsupported_media_type, naming the type sent and the one taken, on every route that takes a body: both were 500 internal_error, and nothing ran.
  • A validation_failed field left out says it's required, with the values it takes where it has a list, a plan field the plans of the catalog that fit.

1.208.0

  • The audit action and webhook event org.contacted: Synq's staff contacted the org's owners, metadata.topic (starter_past_allowance: free Starter past its monthly active users, about Pro), note and monthly_active_users.
  • Nothing about the org changes, and its sign-in never stops or slows.

1.207.0

  • A webhook delivery says max_attempts and, while it's being tried again, next_attempt_at: Synq's own retry schedule (5 seconds, 5 minutes, 30 minutes, 2 hours, 5 hours), no longer the job runner's default backoff.

1.206.0

  • PATCH /v1/orgs/{org}/brands/{brand}/sign-in-page takes place, only the ways to sign in that move, each to its placement and, with position, its place among that placement's, on top of the page as it is (a methods list names every way).
  • A 400 names every field a new or changed app gets wrong at once, a redirect URI at its own pointer (/redirect_uris/0), and a webhook's an unknown event's near match and a private URL's one refusal.
  • api_key_revoked names the key and when, and plan_feature_unavailable the route to the plan that has it.

1.205.0

  • PATCH /v1/orgs/{org} takes default_brand_id, another of the org's live brands to make its default, so the old default can then be deleted on its own.
  • DELETE /v1/orgs/{org}/brands/{brand}'s 409 for the default brand says so.

1.204.0

  • POST /v1/orgs/{org}/billing/plan takes the free plan, which ends the paid one at the end of its period (a trial's last day), as cancelling in the portal does.
  • On a trial a change prorates nothing and keeps the trial to its end.
  • A paid plan chosen while the plan is set to end calls the end off.
  • A plan set to end calls a waiting downgrade off, so GET …/billing never has scheduled_change while canceling.

1.203.0

  • Who left an org: GET /v1/orgs/{org}/former-members lists everyone who left it or was removed and isn't a member again, newest first, from the audit log's member.left and member.removed entries, so as far back as the org's plan keeps its log: who they were, the role they had, joined_at and left_at, departure (left or removed) and removed_by.
  • The audit log's actor filter takes their id, and get_configuration's section former_members and list_audit_log's actor (by email) find them.

1.202.0

  • GET /v1/orgs/{org}/billing/usage names the apps that hold the plan's places, apps.held_by (newest first, as plan_quota_exceeded's held_by; null when the plan has no app limit), so the dashboard's New app says a full plan before the form in the refusal's words, naming what to change or delete.

2026-11-14

1.201.0

  • POST /v1/orgs/{org}/brands/{brand}/sign-in-preview takes app_id, the brand's app the preview is for: the page names that app as its own sign-in does, never Synq's preview app, and an app not in the brand answers 404.
  • A change added to a waiting request (POST …/approval-requests/{request}/changes) that only the plan a trial or plan change it holds moves the org to takes joins the bundle, to be made after the move, even where approvals are off, rather than made at once and refused.
  • configuration.update's set_theme checks the plan when it's asked for, as its route does.
  • A plan refusal for a change that can join a request says to add it to the trial's or plan change's.

1.200.2

  • A validation_failed problem's errors names each field a body doesn't take at its own pointer (/redirect_uri), and the field it likely meant where one is near its name, on a route whose fields are all optional too, such as a PATCH.
  • A value of the wrong type gets its invalid_type alone, saying the type it takes and the one it got.
  • A field's code is always one of invalid_type, too_small, too_big, invalid_format, invalid_value (a route's own check included) and unrecognized_keys.
  • A malformed {app} is invalid_format, as every other id in a path is.

1.200.1

  • The plan feature team.brand_roles is described as roles in one brand at a time, the name Pricing, the docs and the dashboard give it, in inviting, changing a member's roles and the MCP's request_invite.

1.200.0

  • Downloading the audit log (GET /v1/orgs/{org}/audit-log/export) is on every plan, as far back as the org's plan keeps entries: since may be left out, to start at the oldest entry kept, and an earlier one starts there too.
  • until stops at now.
  • format takes json, one array of ExportedAuditEvent.
  • It needs org.auditLog.export, as before, and the plan feature integration.audit_log_export is gone.
  • The plan feature integration.audit_log_streams, streaming the log to a SIEM, is Enterprise's and coming.

1.199.1

  • A Telegram window whose 7-day reminder is dropped, as a 7-day one's is, sends its message to everyone the bot can reach with the 3-day reminder instead: a schedule step's message_reachable says so, and message_reachable says when they go.

1.199.0

  • POST /v1/orgs/{org}/api-keys/{key}/rotate rotates an API key: a new key with its name, permissions, brand roles and IP allowlist, shown once, while the old one keeps working for overlap_seconds (a day by default, up to 7 days, 0 for none, as an app's secret rotation takes it), then answers 401 api_key_rotated, naming the key that took over.
  • An API key's replaced_by and replaces link a rotation's keys.
  • A revoked, expired or rotated key answers 409 conflict, saying which.
  • The audit log's and webhooks' api_key.rotated and api_key.expired, Synq's record of a key's end as it comes.
  • The MCP operation rotate_api_key, which always asks, the new key shown to the person on the approval page.

1.198.0

  • An org's development app is free: an app whose redirect URIs are all on localhost, 127.0.0.1 or [::1] (App.development) doesn't count toward the plan's apps, one per org on every plan (GET /v1/plans' quotas.development_apps; usage's apps.development), and one given a redirect URI anywhere else counts from then on.
  • plan_quota_exceeded for apps names the apps that hold the places (held_by) and how to free one, and PATCH …/apps/{app} may answer it.

1.197.1

  • Free Starter bills nobody past its allowance: GET /v1/plans answers its price.mau_overage_micros null, and a plan's quotas.monthly_active_users and usage's monthly_active_users.over say users above the allowance are never refused, and billed only on a plan with an overage price.

1.197.0

  • Ending a member's sessions in an org: POST /v1/orgs/{org}/members/{user}/end-sessions, after which a Synq access token from a sign-in before then answers 403 fresh_sign_in_required in that org, saying so, until the person signs in again.
  • A member's sessions_ended_at.
  • The audit action member.sessions_ended.
  • configuration.update's operation end_member_sessions.
  • A setup code works only while whoever made it may still change the app (a member who left or was removed, lost org.apps.edit or had their sessions ended, or a key revoked, leaves one that answers 404).

1.196.0

  • What an invite offers (POST /v1/invites/lookup, GET /v1/invites) says what it gives: role_about, what the role across the org lets them do, and brand_roles, each brand by its name with its role's name and what it lets them do.
  • The invite's email says the same.

1.195.0

  • An approval request made at once (applied_at_once) answers expires_at null: it never waited, so nothing about it expires.

1.194.0

  • A permission that changes something comes with the one that reads it: an API key or an org's own role given org.brands.edit holds org.brands.view too, and given org.edit, org.read, as every built-in role does, across the org and in each brand's permission set.
  • Making one refuses the view as it would the change, naming the change first.
  • An approval request's words list what the key or role will hold.

1.193.1

  • Asking for a key, a role or a member's roles with a permission the caller doesn't hold answers insufficient_permissions saying why (nobody gives more than they hold, a key only what it was made with) and how to get it made.
  • A brand's or a webhook's 404 names the id, says it may be one the credential can't see, and gives the route that lists the ones it can.
  • A webhook delivery's 404 names it, its webhook and the route that lists its deliveries.

2026-11-13

1.193.0

  • POST /v1/orgs/{org}/brands/{brand}/apps/{app}/setup-email emails the calling person's own verified address a link to the app's setup on the dashboard, to open on their computer, and says where it went, at most 5 an hour for each person (mail.setup_email).
  • An API key, an address that can't be emailed, or a person with no verified address is refused, saying why.

1.192.0

  • An approval window, like GitHub's sudo mode: once an approval relies on a fresh sign-in, the person's approvals in the same dashboard session skip signing in again until 2 hours after it, closing early when the session ends or signs in again.
  • GET /v1/approval-window says whether it's open and until when, and an approval request's relied_on_sign_in says which sign-in approving it relied on, as its approval_request.approved row's signed_in_at and within_approval_window do.

1.191.3

  • Asking for a change the org's plan can't take (a webhook, a token gate, a sending or custom domain, a token gate's window announced, or a new app or brand past the plan's quota) is refused at once with 403 plan_feature_unavailable or plan_quota_exceeded, whose detail names the plan that allows it and how to move there (its trial, checkout or upgrade), never left for the person to approve.
  • A trial or plan change the same request holds counts.

1.191.2

  • Deleting an org (DELETE /v1/orgs/{org}) says what happens to a paid plan: its Stripe subscription is canceled at once, with nothing prorated and no final invoice.

1.191.1

  • A path's {app} that is neither an app_ id nor a metadata document's URL answers 400 validation_failed before any lookup, as every other id in a path does, and an app's 404 names the app and the route that lists the brand's apps.
  • An API key's insufficient_permissions names the key and says how to make one that has the permission, and revoke it.
  • Keys a body doesn't take suggest the missing fields they likely meant.
  • source says what each value means.
  • The contract's descriptions name no tickets.

1.191.0

  • Setup codes: POST …/apps/{app}/setup-code makes one for a brand's own web app, and POST /v1/setup-codes/redeem, with no credential but the code, adds a project's https loopback addresses to the app and answers its issuer and a new secret, once: what npx synqauth init --code does with the app onboarding made.

1.190.1

  • An org's email over a mail limit (a reply-to confirmation, an invitation) answers 429 rate_limited with the limit's name in reason and, in detail, how many it allows in what window and whose limit it is.
  • A reply-to confirmation counts against the brand's, the org's and the address's limits, as an invitation does, never the caller's network.

2026-11-11

1.190.0

  • A user's consents (GET …/users/{user}/consents) carry scope_descriptions, everything the user allowed each app in the consent page's words.

1.189.1

  • More of what always asks as sign-in security: turning a token gate off, deleting it, or taking a brand, app, Discord role or Telegram group off it (compared with the gate when asked).
  • Account linking loosened: a longer link_reauth_window (compared with the brand's), link_conflicts: move, merge_empty_accounts and move_proved_identities on, a provider's link_by_email or email_authoritative on, and a brand's own provider's endpoints or its subject or email claim. A request names what loosened in its audit rows' loosens.

1.189.0

  • AI agents' changes apply at once by default: …/agent-approvals' members_may_turn_off is require_approval ("Require approval for every AI agent change", off by default, turning it off with a fresh sign-in), /v1/agent-approvals' ask_to_approve is off by default and loses can_turn_off, and turning it off takes a fresh sign-in alone, so the error code agent_approvals_required is gone.
  • An approval request's asks_because gains sign_in_security (an app's redirect and sign-out addresses and how it proves itself, custom sign-in, sending and verified domains, and a sign-in protection turned off), which always asks and takes a fresh sign-in to approve, as fresh_sign_in says.
  • The configuration operation add_custom_domain asks for a brand's custom sign-in domain, checked as a dry run when asked.

1.188.0

  • The dashboard's previews answer values, never HTML: POST …/theme/preview, …/sign-in-page/preview and …/member-profile/preview lose html and content_security_policy for look (HostedPageLook, the brand's look as its pages are drawn in, shared by the three) and, on the sign-in page's and the member profile's, view (SignInPagePreviewView, the signin.page view as the drafts settle it; MemberProfilePreviewView, the member.profile view of a made-up member), which the dashboard draws with @synq/sign-in-ui and @synq/member-ui.
  • The sign-in page's preview answers 200 instead of 503, and its request's view component is SignInPagePreviewState.

1.187.0

  • A brand's theme loses layout, method_order and panel_text: the sign-in page is always centered, and its placement on …/sign-in-page orders the ways in. BrandTheme (GET and PATCH …/theme, and the theme removing a default avatar or the background answers) no longer has them, and BrandThemeUpdate (PATCH …/theme, POST …/theme/preview and …/sign-in-page/preview's theme) refuses them.

1.186.0

  • A person's connected apps: GET /v1/connected-apps lists Claude, ChatGPT and the other apps connected to their Synq account, each with its name and where that comes from, its scopes in plain words, when it connected and was last used, and how its changes are made in each of their orgs.
  • DELETE /v1/connected-apps/{connection} disconnects one, ending its grants and refresh tokens, recorded as user.consent_revoked with by: connected_apps.

1.185.1

  • A token gate's activity conditions count compressed tokens: a wallet is in a transaction that opened or closed a compressed token account of its own, as Helius's indexer says, so address_activity counts compressed tokens sent and received, and role: any the transactions they reached it in.
  • A compressed NFT's owner was one of its accounts already. Each wallet's newest 1,000 such transactions are read, as of its own, and capped says so.

1.185.0

  • One word for an approval request: its ids are apr_… (were chg_…), the audit actions and webhook events change_request.created, .approved, .declined, .applied and .change_added are approval_request.…, their resource type is approval_request, and the routes' words say approval request.

1.184.0

  • Bundles: POST …/approval-requests/{request}/changes adds a change to one of the person's requests still waiting, which becomes a bundle (kind: bundle) they approve once, its changes made in order, all or none, each with its own title, preview, details and result.
  • An invitation, an API key, a new brand and a change that makes a secret go alone.
  • Recorded as change_request.change_added.

1.183.0

  • An approval request's last_refusal: the last time approving it was refused by the change's own route, its code, detail and when, so the agent that asked hears why it waits again.
  • invalid_hostname says which rule a custom domain broke.

1.182.0

  • People may turn off approving their AI agents' changes, where their org lets them: GET and PATCH …/agent-approvals (the org's members_may_turn_off, with org.sso.edit to change it, and the caller's your_approvals, ask or apply_at_once), GET and PATCH /v1/agent-approvals (the person's own ask_to_approve, and can_turn_off), both changed from the dashboard alone, loosening with a fresh sign-in.
  • A request asked with approvals off and about neither money nor people, making no secret, is made at once: approved, applied_at_once, recorded as change_request.applied.
  • Each request's asks_because.
  • The error code agent_approvals_required.
  • The audit actions org.agent_approvals_updated and member.agent_approvals_updated.

1.181.1

  • An API key's GET …/approval-requests answers an empty list, not 403: a key asks for no change, so it has none.

1.181.0

  • A person's approval requests: GET …/approval-requests, theirs alone, newest first, status=awaiting_approval for those still waiting.
  • Each request's fresh_sign_in, and approving takes a sign-in from the last 5 minutes only for a change to money or people (billing and plans, members and invitations, roles, API keys, deleting or moving a brand).

1.180.0

  • An approval request's configuration.update takes every approval operation of the catalog: a brand's own sign-in providers changed and deleted, and the providers its app verifies added, changed, turned on or off and deleted.

1.179.0

  • An approval request in words: its title, named for what it changes ("Make a token gate", "Announce a Discord window"), a preview in plain words with names for every operation (what changes, who it affects, how to undo it), and details, each field it sets by its label with its values in words.

1.178.0

  • Sending domains belong to a brand: listed, added, read, checked and deleted under …/brands/{brand}/email-domains with org.emailDomains.view and org.emailDomains.edit in the brand (Brand admin holds both), each answering its brand and in_use in place of used_by.
  • The org's own /v1/orgs/{org}/email-domains, …/{domain} and …/{domain}/check are gone.
  • A name already held is 409 email_domain_unavailable with its reason: another_brand names that brand of the org (brand_id, and in detail), another_org never names the org, this_brand says it's there, and the first two carry a subdomain to add instead (suggested_domain, the EmailDomainProblem schema).
  • A brand's sender takes only its own domains.
  • Deleting a brand deletes its domains (brand_deleted).
  • A brand's move takes every one of its domains, which its preview names in sending_domains, so sending_domain_shared blocks no move.

1.177.0

  • An approval request's asked_from_name: the name of the app it was asked from, as that app gave it to Synq's sign-in (an MCP host such as Claude, by its registration or its client ID metadata document), or null, so the dashboard says who asked.

1.176.0

  • A brand's next sign-in email, drawn: GET …/brands/{brand}/email/preview, with org.brands.view, answers its subject, effective and the whole HTML document as the mailer sends it now, with a sample code, and the policy to show it under.

1.175.0

  • Users: each session's signed_in_apps, the apps of its apps named and saying what each is (kind: one of the brand's apps, one of Synq's own such as the sign-in preview, an app known only by its metadata document, or one deleted since, named as the audit log recorded it).

1.174.0

  • A brand's sign-in page is the one place a way to sign in is on or off: PATCH …/sign-in-page turns each one on or off, and its impact works.
  • The brand's built_in_methods (on Brand, BrandCreate and BrandUpdate), a sign-in provider's enabled, a brand's own provider's enabled, their POST …/enable and …/disable routes and the approval kind brand.sign_in_provider are gone.
  • offered says whether the page has a provider on.
  • A way off for everyone is refused everywhere by name, one off for new people signs in only someone who has it and is added to no account.
  • Deleting a brand's own provider that is its last way on is 422 no_way_to_sign_in, and putting Matrica on without the tenant's own app 422 own_app_required.
  • The preview still answers 503 until the hosted pages, in their own app, draw it.

1.173.0

  • Notices a person hides for themselves in Synq's dashboard: GET /v1/notices/{notice} and POST /v1/notices/{notice}/hide, a person's credential only, for add_passkey, their account's "Add a passkey" to-do.
  • A brand's notice nextjs_app, the "Make your Next.js app" card after onboarding.

1.172.0

  • A second notice a person hides for themselves in a brand: website_logo_prompt, the brand overview's "Use your website's logo" prompt in the dashboard, whose "Not now" keeps it hidden for them on every device.

1.171.0

  • The invites waiting for a person: GET /v1/invites, those sent to their verified address, each with what it offers and its id, and POST /v1/invites/{invite}/accept to accept one by its id (404 for another address's).
  • Accepting into an org they are in already answers 409 conflict with its org_id.

1.170.0

  • A webhook's short name: name on a webhook, at most 60 characters or null, which making and changing one take (createWebhook, updateWebhook and the configuration operations create_webhook and update_webhook).
  • The audit log's and webhooks' webhook.created and webhook.deleted carry it.

1.169.0

  • What an invite's link offers: POST /v1/invites/lookup, public, the token in the body, answering the org's name, the role and its name, the inviter's name and the expiry, or 404 once the invite is used, revoked or expired, or its org is gone.
  • A few a minute from one address, or from one person through Synq's dashboard.

2026-11-10

1.168.0

  • A brand's sign-in page, its contract first: GET and PATCH …/brands/{brand}/sign-in-page (where each way to sign in goes, shown, more or off with off_for everyone or new_people, in one ordered list; the step after the email address, email; what people coming back see, returning), GET …/sign-in-page/impact (who each way affects) and POST …/sign-in-page/preview (the page in any state, from a draft), with the codes too_many_shown and no_way_to_sign_in.
  • The two reads answer what the brand has set now, and the change and the preview answer 503 service_unavailable until the model lands.

1.167.0

  • A brand's own default avatars are Pro and up: the plan feature branding.default_avatars, which uploading and finalizing a default_avatar file want (403 plan_feature_unavailable).
  • A plan without it keeps the set, its theme's not_shown names default_avatars, its pages draw Synq's own in default_avatar_style (on every plan), users' default_picture is absent, and removing one still works.
  • A brand move's plan_changes names it.

2026-11-09

1.166.0

  • A notice a person hid for themselves in a brand: GET …/brands/{brand}/notices/{notice} and POST …/notices/{notice}/hide, a person's credential only, with org.brands.view.
  • setup_checklist is the brand overview's "Finish setting up" checklist in the dashboard, hidden for them on every device and never shown again by itself.

1.165.0

  • Where verified members go: a Discord server's verified_channel_id, set with updateDiscordServer's verified_channel (a text channel of the server, or null for the server itself) and the configuration operation update_discord_server, which the member profile's Back to Discord opens once a role is given.

1.164.0

  • Three more Telegram messages take the gate's rule, {asks_for}: the announcement, not_yet and grace_started, as Synq's own words now say what qualifies.
  • Synq's wording of every Telegram and Discord message, each one's default, is friendly and gate-neutral: verified, never holders.

1.163.0

  • Moving a way in on its own proof: a brand's move_proved_identities, on by default (off for a brand whose tenant chose link_conflicts: refuse): a wallet or a provider's account another user has, who keeps another way in, moves to the person adding it on the proof they just made, with no code.
  • The configuration operation set_brand_sign_in_policy takes it.
  • The audit log's and webhooks' user.identity_unlinked and user.identity_linked carry on_own_proof: true for such a move.

1.162.0

  • A brand's own OpenID Connect and OAuth 2.0 providers are Scale and up: the plan feature auth.custom_providers, which adding one and replacing its app (PUT …/app) want, in place of auth.byo_connections, which stays Pro and up for an app at Synq's providers.
  • A brand move's plan_changes names it.
  • Accounts the tenant's app verifies stay on every plan.

1.161.0

  • An app's own list of ways to sign in names the brand's own providers: sign_in_methods in createApp and updateApp, an approval request's app.sign_in_method method and the configuration operation set_app_sign_in_methods take custom-… ids beside Synq's, at most 32.
  • An id the brand has no such provider for, or one its app verifies, is validation_failed at its place in the list.
  • Deleting a provider takes it off every app's list (each an app.updated with provider_deleted), and is 409 sign_in_method_in_use, naming the apps, while an app takes no other way.

1.160.0

  • Adding a way in without signing in again: a brand's link_reauth_window is 2 hours by default (was 10 minutes) and at most a day (was an hour), counted from a sign-in on the device, whichever way it was made.
  • merge_empty_accounts is on by default, and every brand whose tenant never set it takes it.
  • The audit log's user.identity_linked and user.merged carry confirmed_by and the new_device and new_ip signals.

1.159.0

  • Identities the tenant's app verifies: …/brands/{brand}/app-verified-providers (a name, an icon, sign_in_tickets: linking alone, or linking and sign-in links), POST …/link-codes/redeem (the code in the body), POST …/users/{user}/identities (added by the tenant's server), POST …/sign-in-tickets (a link for one of the brand's own apps and one of its redirect URIs, 2 minutes, once).
  • A linked account's added_by.
  • The permissions org.users.identities.edit and org.users.signInTickets.create.
  • The codes link_code_invalid and identity_in_use.
  • The audit log's and webhooks' user.identity_pending, user.identity_rejected, user.sign_in_ticket_created and user.sign_in_ticket_used, and user.identity_linked's by: app and by: server.

1.158.0

  • A brand's own sign-in providers: /v1/orgs/{org}/brands/{brand}/custom-sign-in-providers, OpenID Connect issuers and OAuth 2.0 servers through the tenant's own app, listed, made (org.connections.edit, auth.byo_connections, a person's fresh sign-in), read, changed, turned on and off, their app replaced (PUT …/app) and deleted with their linked accounts.
  • The codes provider_url_unsafe, provider_discovery_failed and sign_in_provider_exists.
  • The file purpose provider_icon.

1.157.0

  • An approval request of kind configuration.update takes the operation send_brand_transfer_notice: emailing a moved brand's users once, asked from an MCP host and approved by the new org's owner.
  • Asking refuses a move that wasn't accepted into the org, a brand no longer the org's, and a notice already asked for.

1.156.0

  • What a brand calls its members is the brand's, made in place: the community messages' frame and PATCH carry members_called (plural and singular, Synq's members and member by default), every bot message takes {members} and {member}, and a Telegram group's and a Discord role's window no longer take or answer members_called.

1.155.0

  • Claiming a development org into an org you have, as a brand: POST /v1/claimable-orgs/claim-into, with the claim token and org, one the caller owns or is an admin of, with a fresh sign-in and room under its plan for another brand (plan_quota_exceeded, naming the org): the development org's brand joins it with its apps, keys and users, its id, issuer and client ids the same, and the development org closes.
  • POST /v1/claimable-orgs/lookup answers into_orgs, the orgs it can join, each with its role, plan, brands, brand_limit and refusal.
  • The audit log's and webhooks' brand.claimed, from npx synqauth init.

1.154.0

  • Telling a moved brand's users: POST /v1/orgs/{org}/brand-transfers/{transfer}/notice, the new org's owner, once, after the move: Synq emails each of the brand's users with a verified address, from the brand's own sender, in background batches within the notice's own mail budget.
  • A request's notice (when asked, when the last went, how many it reached).
  • The audit log's and webhooks' brand.transfer_notice_sent, in the new org.

1.153.0

  • Brands' wallet_name_usernames: whether people's wallets' on-chain names (a Seeker ID's .skr) are offered first as usernames, on by default.

1.152.0

  • An approval request of kind configuration.update takes the operation accept_brand_transfer: accepting a move into the org, asked from an MCP host with the request's preview_hash and approved by the org's owner, whose approval confirms the data-responsibility line its preview says.
  • Asking checks the hash is the request's now and needs org.brands.transfer across the org.

1.151.1

  • Brand moves: close_from_org on the org's last brand closes the org when the move is accepted, as DELETE /v1/orgs/{org} does, recorded as org.deleted naming the move.
  • from_org_empty says it closed. The descriptions say so.
  • The contract doesn't change otherwise.

1.151.0

  • Billing: cancel_at, when a plan canceled in the billing portal ends, which canceling now ends at.
  • Stripe's portal cancels by that date, not at the period's end.
  • trial_ends_at stays while a canceled trial runs out.

1.150.0

  • The Telegram bot's "Verified already": community messages' telegram verified_here, its answer to a Verify press from someone verified in the group.

1.149.0

  • Exporting the audit log: GET /v1/orgs/{org}/audit-log/export, every entry between since and until (at most 366 days), oldest first, the org's own and every brand's, each with its brand's id and name and the org's id, as NDJSON or CSV, streamed.
  • Needs org.auditLog.export, a new org permission, and the Enterprise feature integration.audit_log_export.
  • Recorded as org.audit_log_exported.

1.148.0

  • Accepting a brand move: POST /v1/orgs/{org}/brand-transfers/{transfer}/accept, the target's owner, with confirm_data_responsibility and the preview_hash they read, moves the brand at once, with its users, apps, issuer, domains, communities, bots and token gates, and ends the old org's grants on it.
  • transfer_preview_changed (409), a new code, when what moves or changes isn't what the preview showed.
  • A request's reason and from_org_empty.
  • preview_hash leaves out the user counts.
  • An approval request's cancelled status and reason, when the brand it names moved.
  • The audit log's and webhooks' brand.transfer_accepted in both orgs, to All brands endpoints alone.

1.147.0

  • Brands: an icon beside the logo, icon_url, uploaded with the file purpose brand_icon (cut to a square, kept at most 512 × 512) and removed with DELETE …/icon.
  • It is the bots' Discord author icon and the pages' tab and home-screen icon, before the logo.
  • A bot frame's look has icon_url, what the embed's circle shows.

1.146.0

  • Verified domains, the first step to enterprise team sign-in: GET and POST /v1/orgs/{org}/domains, GET and DELETE …/domains/{domain}, and POST …/domains/{domain}/verify, a domain an org proves it owns with a TXT record at _synq-verification.<domain>, held by one org at a time and read again daily.
  • Adding and verifying one need team.sso (Enterprise), reading and deleting never do.
  • The permissions org.sso.view and org.sso.edit, the org's alone.
  • The codes org_domain_invalid, org_domain_exists, org_domain_limit_reached and org_domain_verified_elsewhere.
  • The org_domain.* events.

1.145.0

  • An approval request of kind configuration.update takes the operations request_brand_transfer, decline_brand_transfer and cancel_brand_transfer: moving a brand to another org, asked from an MCP host and approved by the org's owner, whose approval confirms the data-responsibility line its preview says.
  • Asking one needs org.brands.transfer across the org.

1.144.0

  • Provider tokens and linking-only providers: a brand's sign-in providers' use (sign_in or link_only), keep_tokens (through the brand's or org's own app alone, 422 own_app_required; on wants a person's fresh sign-in) and kept_claims.
  • GET …/users/{user}/identities, their linked accounts with the kept claims and whether tokens are kept.
  • POST …/identities/{identity}/access-token, the person's access token at the provider, refreshed by Synq, for an org API key on a server alone (403 server_only), with the permission org.users.providerTokens.read and the codes provider_token_unavailable, provider_token_revoked and provider_unreachable.
  • The audit log's and webhooks' user.provider_token_read and user.identity_token_revoked.

1.143.0

  • Brands' merge_empty_accounts: adding a way in that another user signs in with merges that user in at once when it holds nothing else.
  • The audit log's and webhooks' user.merged, and user.deleted's by: merged.

1.142.0

  • Brands: GET …/stats' sign_ins_started_last_7_days, the sign-ins started at the brand, finished or not, for its sign-in success.
  • Its 7 days are now today and the 6 before it in UTC, for every figure over them.

1.141.1

  • The built-in member's role sees the org's plan (org.billing.view), so a member who can't change the plan sees what another would do and asks the owners for it. The contract doesn't change otherwise.

2026-11-08

1.141.0

  • Who can reach a brand: GET /v1/orgs/{org}/brands/{brand}/members, the owner and each member with a role on All brands or in the brand, with those roles alone, for its Access page.
  • Needs org.members.view in the brand.

1.140.0

  • The caller's roles: GET …/permissions' role, the caller's org role (null for an API key), and brand_roles, its roles per brand or on All brands (an owner's Brand admin on All brands, always).
  • An org.invite change request's brand_roles and the org role billing, its preview naming each brand, and a brand the person can't reach refused at its field.

1.139.0

  • Brand-scoped API keys and webhooks: a key's brand_roles, a role or a permission set per brand or on All brands, at most the maker's in each.
  • Left out, its permissions on All brands, which only the owner (or a key for All brands) gives, else 403 all_brands_owner_only, a new code.
  • A key for some brands reads the org alone across it (org.read), else 400.
  • A credential sees and revokes the keys within its brands.
  • A webhook's brands, null for All brands, which alone gets the org's own events and wants org.webhooks.edit across the org.
  • An endpoint for some brands gets their events alone, and a credential sees and changes the endpoints within its brands.
  • An org.api_key change request's brand_roles.
  • A change request's audit entries are its brand's, and a key's or endpoint's are its one brand's, where it has one.

1.138.0

  • Members' brand roles: a member's and an invite's brand_roles, a role per brand or on All brands (brand null), Brand admin, Developer, Support, Viewer or the org's own.
  • Making an invite and changing a member (PATCH …/members/{user}, role and brand_roles each optional) take them, never beyond the caller's in that brand, and left out give the org role's own (Brand admin on All brands for an admin, Viewer for a member, none for billing).
  • One brand at a time wants the plan feature team.brand_roles (Scale and up), All brands any plan.
  • The built-in org role billing (the plan, invoices and the org's audit entries).
  • A role's level (org, brand or any) and the brand roles in GET …/roles.
  • GET …/permissions' brand_permissions, what the caller may do on All brands and in each brand it holds a role in.

1.137.0

  • Brand moves: a request's cancelled_by may be staff, when Synq's staff cancelled it with a reason both orgs' audit logs show.

1.136.1

  • Brands: link_conflicts: move merges the other account into theirs where the way in is its only one, after a page that shows what comes over and the step-up, rather than deleting it to move the way in.
  • A move waits for the step-up too. The description says so.
  • The contract doesn't change otherwise.

1.136.0

  • Per-brand roles: a member's and a key's permissions are across the org (its org role, or a key's own) and per brand (its brand roles, on one brand or on All brands, those made later included).
  • A brand it holds no role in answers 404 on every route of the brand's, as another org's does, and drops out of the org's lists (brands, token gates, Discord servers, Telegram groups, community activity, the audit log, a sending domain's used_by).
  • The org's own actions want the permission across the org, refused in words that say so.
  • Deleting a brand and moving one are the org's own actions.
  • The audit log's org entries (no brand) want org.auditLog.view across the org.
  • The built-in member's role sees the org alone, with Viewer on All brands by default.

1.135.0

  • Users: sign_in_methods, how each user signs in (each kind of way they have, and a password), in a brand's user list and on a user.

1.134.0

  • Orgs: GET /v1/org-allowance's counted_orgs, the free orgs its owned counts, each with its plan, whether it's on a trial, whether the caller's own account owns it, and for a deleted one when it stops counting, so the claim page offers a free org to upgrade or delete, never a paid one.

1.133.0

  • Moving a brand to another org: GET /v1/orgs/{org}/brands/{brand}/transfer-preview (what moves and what changes, from the brand's org's side), POST …/brands/{brand}/transfers (an owner asks, confirming the target becomes responsible for the users' data), GET /v1/orgs/{org}/brand-transfers and …/brand-transfers/{transfer} (both directions, with the preview and, on the target's side, its plan's gaps and preview_hash), POST …/decline and …/cancel.
  • The permission org.brands.transfer, the owner's alone.
  • brand_transfer_blocked, transfer_target_unavailable and brand_transfer_ended.
  • The audit log's and webhooks' brand.transfer_requested, brand.transfer_declined and brand.transfer_cancelled in both orgs. Accepting, which moves the brand, comes later.

1.132.1

  • The cap on the orgs one person owns counts free orgs only: an org on a paid plan, Enterprise or a plan Synq set doesn't count, an org on a trial does until it's paid, and a free org deleted in the last 30 days still counts.
  • Handing over a paid org never meets the cap. The descriptions and problem details say so.
  • No code changes.

1.132.0

  • Brands: GET …/stats, a brand's users, monthly active users this month, sign-ins and new users over the last 7 days, and who signed in through each app this month, none counting the sign-in preview's.

1.131.0

  • Token gates belong to a brand: /v1/orgs/{org}/brands/{brand}/token-gates, its list and making one, …/{gate} (read, change, delete), …/{gate}/enable and …/{gate}/disable, and …/check, each within the brand.
  • A gate's brand.
  • A gate names only its own brand, that brand's apps and the servers and groups connected to it (400 at the field, naming both brands).
  • The org's own routes stay, reading across brands, and making a gate there takes brand, else its first target's brand, else the default brand.
  • A deleted brand's gates are shown nowhere.

1.130.0

  • Announced windows for gated Discord roles: GET /v1/orgs/{org}/discord-servers/{server}/windows (every gated role there whose gate gives those already holding it time, with its settings, schedule and counts), PUT …/discord-servers/{server}/roles/{role}/window, POST …/window/announce, …/window/extend, …/window/pause and …/window/resume.
  • The Discord window's messages in a brand's words (messages.discord.announcement, the reminders, names, extended, closing, announcement_closed, announcement_cancelled).
  • Each text channel's can_pin.
  • A gated role's adoption.state waiting until its window is announced, its holders taken in with the window's deadline, not 7 days.
  • "Add to Discord" asks for Pin Messages too.
  • configuration.update's operations set_discord_window, announce_discord_window, extend_discord_window and resume_discord_window.
  • The audit log's and webhooks' discord_role.window_announced, window_updated, window_reminded, window_extended, window_paused, window_resumed, window_waiting, window_deadline_started and window_closed.

1.129.0

  • An org's members, roles and API keys through approval requests: configuration.update's operations create_role, update_role, delete_role, update_member, remove_member, leave_org and revoke_api_key.

1.128.0

  • A brand's words for its bots: GET /v1/orgs/{org}/brands/{brand}/community-messages, a page of every message Synq's Telegram and Discord bots send about its groups, servers and roles, each with its text (null for Synq's), Synq's wording, its fill-ins, what it must name, its longest and the buttons Synq attaches whatever it says.
  • GET …/community-messages/frame, the brand's look and the Verify button.
  • PATCH …/community-messages, each message's text and verify_button, the Verify button's text, on a plan with branding.remove_powered_by.
  • The audit log's brand.updated names each change as community_messages.<platform>.<message> or community_messages.verify_button.

1.127.0

  • An approval request of kind configuration.update takes the communities' operations: set_discord_verify_channel, disconnect_discord_server, disconnect_telegram_group, set_telegram_window, announce_telegram_window, extend_telegram_window, resume_telegram_window and remove_own_bot.

1.126.0

  • An approval request of kind configuration.update takes the operations set_brand_sign_in_policy, delete_brand, remove_email_domain, remove_custom_domain, update_sign_in_provider, set_org_sign_in_provider_scopes, remove_org_sign_in_provider_app and remove_sign_in_provider_app.

1.125.0

  • An approval request of kind configuration.update takes the operations set_app_logout_uris, set_app_security, enable_app, disable_app, delete_app, delete_api, create_webhook, update_webhook and delete_webhook.
  • Approving create_webhook answers the new webhook's signing secret as secret, once, to the person.

1.124.0

  • A brand's users through approval requests: configuration.update's operations create_user, set_user_profile, enable_user, disable_user, revoke_user_sessions, remove_user_passkey, schedule_user_deletion, revoke_user_consent and revoke_user_api_key.

1.123.0

  • An approval request of kind configuration.update takes the operations change_plan and start_trial, whose preview says what they cost from the plan preview.

1.122.0

  • An approval request of kind configuration.update takes item_id, a second id under resource_id, and the operation delete_token_gate, which deletes a token gate once approved.

1.121.1

  • A member profile lists a server or group only with a public way in (Kelvin, 2026-11-08): PATCH …/discord-servers/{server} and …/telegram-groups/{group} refuse listed: true for one with none (400 at listed, with the fix), and listed is false for one with none, whatever the brand chose.

1.121.0

  • Synq lifts only its own mutes in a gated Telegram group: the audit log's and webhooks' telegram_member.muted_by_admin, when Synq leaves someone an admin muted as they are, which GET /v1/orgs/{org}/integrations/activity counts as removed.

1.120.0

  • GET /v1/slugs/{slug} says protected for a well-known service's name, held for its verified owner, apart from reserved, a name only Synq may take.

1.119.0

  • A token gate's test is worded by what the gate does: POST /v1/orgs/{org}/token-gates/check takes brands, apps, discord_roles and telegram_groups for a draft's words, and answers goal (get Holder in the Acme Discord, sign in to Acme, qualify), which its explanation's first line says.

1.118.0

  • A gated Telegram group's window reads its whole member list through Telegram's admin member listing where the API has an MTProto app: members_listed_at and members_list_complete on …/telegram-groups/{group}/window.
  • A request an admin let in by hand while the window runs gets its deadline.

1.117.0

  • Announced windows for gated Telegram groups: GET and PUT /v1/orgs/{org}/telegram-groups/{group}/window (the settings, the topics Synq has seen, every reminder with when it goes, and the counts: verified, still to verify, unknown, with the deadline's pacing), POST …/window/announce, …/window/extend, …/window/pause and …/window/resume.
  • A gated group's adoption.state waiting until it is announced.
  • The audit log's and webhooks' telegram_group.window_announced, window_updated, window_reminded, window_extended, window_paused, window_resumed, window_waiting, window_deadline_started and window_closed. A gated group's existing_members: verify now gives those already there the announced window, not 7 days.

2026-11-07

1.116.0

  • The member profile itself: POST /v1/orgs/{org}/brands/{brand}/member-profile/preview, the dashboard's live phone preview.
  • The audit log's user.identity_unlinked says by: member_profile for a way in removed there.

1.115.0

  • Synq Communities' member profile: GET and PATCH /v1/orgs/{org}/brands/{brand}/member-profile (its addresses, the sections it shows and its copy, and which servers and groups it lists).
  • PATCH …/discord-servers/{server}'s invite_url and listed, and PATCH …/telegram-groups/{group}'s listed.
  • Each server's and group's listed and listed_by.
  • Connecting a server or a group no longer needs the brand to offer Discord or Telegram sign-in, only wallets.

1.114.0

  • Synq never lifts or shortens a ban an admin set in a gated Telegram group: the audit log's and webhooks' telegram_member.banned_by_admin, when Synq leaves someone an admin banned as they are.
  • A removal is a ban that lifts itself two minutes later.

1.113.0

  • Token gate conditions on activity: program_activity (at least min_count successful transactions in the last window_days days that ran a program, signed by the person unless role: any) and address_activity (as many with an address, by who signed them: direction sent, received or either), each verdict's count, until and capped, and a group verdict's until.

1.112.0

  • Members recognized with no link because their account is linked at the brand already: the audit log's and webhooks' discord_role.recognized and telegram_member.recognized, which GET /v1/orgs/{org}/integrations/activity counts as verified.

1.111.1

  • Telegram groups' guard_bot says what it means now that Synq's bot shows no Mini App: a guard bot's join requests are left to the group's admins at once and verified through a link, as every other group's are.

1.111.0

  • An org's own Discord app and Telegram bot (Scale and Enterprise): GET /v1/orgs/{org}/own-bots, PUT …/own-bots/discord and …/own-bots/telegram (checked with Discord or Telegram, sealed), DELETE …/own-bots/{platform}.
  • own_bot on Discord's install and Telegram's connect.
  • The plan feature integration.own_bots.
  • The audit log's and webhooks' own_bot.set and own_bot.removed.

1.110.0

  • Those already holding a gated Discord role or in a gated Telegram group: a gate's discord_roles and telegram_groups each gain adoption (its state, deadline, how many were counted, how many still have to verify, how Synq finds them, and what stops it, with the fix).
  • GET …/discord-servers/{server}/roles' holders and holders_more.
  • The audit log's and webhooks' discord_role.adoption_started, discord_role.adoption_reminded, discord_role.adoption_failed, telegram_group.adoption_started and telegram_group.adoption_reminded.

1.109.0

  • Connecting Telegram groups through Synq's bot: POST /v1/orgs/{org}/telegram-groups/connect (a one-time code, the add-to-group link and the /connect command) and POST …/telegram-groups/{group}/check, and the audit log's and webhooks' telegram_group.connected, telegram_group.updated, telegram_group.bot_removed, telegram_member.approved, telegram_member.declined, telegram_member.removal_scheduled, telegram_member.muted, telegram_member.unmuted, telegram_member.removed and telegram_member.action_failed.

1.108.0

  • Synq's Discord bot: POST /v1/orgs/{org}/discord-servers/install, Discord's install screen for the bot.
  • GET …/discord-servers/{server}/roles and …/channels, read from Discord now.
  • PATCH …/discord-servers/{server}'s verify_channel, where the bot keeps its Verify message.
  • The audit log's and webhooks' discord_server.connected, discord_server.updated, discord_role.granted, discord_role.removal_scheduled, discord_role.removed, discord_role.grant_failed and discord_role.removal_failed.

1.107.0

  • Discord roles and Telegram groups as token-gate targets: a gate's discord_roles and telegram_groups, each with its grace period, re-check interval and what happens to those already there, and a Telegram group's on_lost (mute or remove).
  • GET and DELETE /v1/orgs/{org}/discord-servers and …/telegram-groups, GET …/integrations/activity, the permissions org.integrations.view and org.integrations.edit, the problems discord_unavailable and telegram_unavailable, and the audit log's and webhooks' discord_server.disconnected and telegram_group.disconnected.

2026-11-06

1.106.0

  • Brand themes: "Powered by Synq" is a choice of three: powered_by takes true to keep it, false to hide it (branding.remove_powered_by) and null for the plan's default, which hides it on a plan with branding.remove_powered_by (Scale and Enterprise) and shows it on every other.
  • A theme's powered_by_choice and powered_by_default.

2026-11-02

1.105.0

  • The audit log's and webhooks' brand.email_allowance_reached: a brand's sign-in email refused by its plan's allowance, at most once an hour.

2026-11-01

1.104.0

  • Pictures people choose and defaults each app draws: a user's picture_source, avatar_seed and default_picture.
  • A brand's own default avatars, the default_avatar upload purpose, its theme's default_avatars, default_avatar_style and DELETE …/theme/default-avatars/{file}.
  • Files' user_picture_upload purpose.
  • The problems picture_unavailable and storage_unavailable.

1.103.0

  • Brands: link_reauth_window, how recent a sign-in lets someone add a way to sign in without signing in again.
  • The audit log's and webhooks' user.identity_linked carry the provider's user id and the scopes granted.

1.102.0

  • Apps' sign_in_claims: an app's ID tokens say how each sign-in went, sign_in_method, sign_in_wallet and new_user.
  • For the brand's own (first_party) apps only.

1.101.0

  • Extra scopes at the sign-in providers, per org and per brand: GET /v1/provider-scopes, the public catalog of what each provider's reviewed list allows.
  • PUT and DELETE …/sign-in-providers/{provider}/scopes for the org and a brand.
  • Sign-in providers' scopes, the org's list's scopes, provider apps' app_type for GitHub.
  • scope_not_allowed, scope_unavailable and scope_needs_own_app.
  • A user's identities' scopes and unconfirmed_scopes, and Telegram's details.

1.100.0

  • No exception is left for launched callers: a value list an answer carries is x-extensible-enum, an enum only where it is a constant (apps' app_type and source, approval requests' kind and status, billing's status, interval, applies and action, themes' layout, button_style and card_shadow, slug reasons, link_conflicts, signs_in_through, audit actors' type, deliveries' status, sessions' via, files' visibility, plan features' status, token gate groups' type and schedules' outside).
  • The change-request routes (POST /v1/orgs/{org}/change-requests, its GET, approve and decline) are gone, approval requests making every change they made.
  • Every list pages, 50 by default: a brand's and the org's sign-in providers, an app's API access, a user's passkeys, consents and API keys, and the open upgrade requests too.

1.99.0

  • The standard's form is the only form: apps, users, sign-in providers, webhooks and token gates turn on and off only with POST …/enable and …/disable, never an enabled or disabled field.
  • Members, invites, roles, webhooks, token gates and plans answer a page, 50 by default, and invoices take only cursor, with no after or has_more.
  • A path id that isn't one of its kind is 400 validation_failed, not 404.
  • Validation errors are { pointer, code, detail }, with no path or message.

1.98.0

  • Money is an integer string in the unit its name says: plans' monthly_cents and annual_cents, invoices' total_cents and amount_due_cents, and plan previews' amount_due_today_cents and price_cents.
  • A plan's overage per user is mau_overage_micros, millionths of the currency, in place of the decimal mau_overage_cents.

2026-10-31

1.97.0

  • Brand creation: hash-bound dashboard approvals for permanent issuer namespace effects.
  • Approval decisions commit effects, results and audit atomically.
  • Durable email recovery.

1.96.0

  • Approval configuration: atomic whole app sign-in method lists and null inheritance.

1.95.0

  • Change requests: hashed previews, fresh dashboard approval, access-change kinds and approval provenance in audit rows.
  • Shared app quickstarts and configuration approvals.
  • Additive approval-requests preserve launched change-requests.

2026-10-30

1.94.0

  • Brand link-conflict policy and existing-account prompt.

1.93.0

  • Orgs: GET /v1/org-allowance, whether the caller may make another org, and when a slot frees up at the cap.

1.92.0

  • Webhooks: POST …/webhooks/{webhook}/deliveries/{delivery}/resend sends a finished delivery again, now and once.

1.91.0

  • Additive user/app/provider/token-gate actions and cursor queries on formerly unpaged lists.

1.90.0

  • Public quota headers, method_not_allowed and management authentication discovery.

2026-10-26

1.89.0

  • Webhooks: additive enable and disable POST actions.
  • PATCH remains supported.

1.88.0

  • Claimable development orgs, one-time ownership claims and bounded unclaimed sign-in and email budgets.

2026-10-25

1.87.0

  • Billing state, no-card trials, plan previews, portal card updates and member upgrade requests.
  • Plan trial_days and trial_unavailable.

1.86.0

  • Optional validation code, detail and JSON-body pointer.

1.85.1

  • Files and uploads declare existing timestamp fields as date-time.

1.85.0

  • Public root metadata for proactive management resource discovery.

1.84.0

  • Website logo and sign-in color suggestions for verified work domains.

1.83.0

  • Protected service org/issuer slugs require staff-verified organization ownership.

1.82.0

  • Org creation rechecks disposable email addresses, refusing with org_creation_closed and guidance to use a permanent address.

1.81.0

  • Problem documents include origin request_id, optional numeric retry_after and safe internal-error guidance.

1.80.0

  • The audit log and webhooks record outside app registration through DCR and CIMD as app.registered.

2026-10-23

1.79.0

  • Apps: test_sign_ins, made-up GitHub and Google accounts for a tenant's tests, everywhere but production.
  • A user's identities: details' test mark.

1.78.0

  • APIs: identity_claims (email, email_verified, linked_accounts), who the person is in their access tokens and API key checks.
  • A user's identities: Google's details, email_verified and workspace_domain.

1.77.0

  • Brands: built_in_methods, each built-in way to sign in on or off.
  • Apps: sign_in_methods, the ways an app takes.

1.76.0

  • Sign-in providers and connections: github.
  • A user's identities: github, its handle, and details with details_read_at, what GitHub said of the account at their last sign-in with it.

2026-10-21

1.75.0

  • Brands: POST sign-in-preview, a link to try the brand's sign-in as Synq's preview app.

1.74.0

  • Sign-in providers: Matrica at a tenant's brand through the tenant's own app, the provider's synq_app, and the problem own_app_required.

2026-10-20

1.73.0

  • Token gates: a dry run wants the plan's token gating, 403 plan_feature_unavailable.

1.72.0

  • A user's identities: handle, their username at X, Discord, Telegram or Matrica.

1.71.0

  • Apps: the warning passkey_origin_beyond_related_origins_limit.

1.70.0

  • Apps: own_ui_sign_in, signing people in on the app's own screens.

1.69.0

  • A user's sessions say where each was signed in (via: the hosted page, or an app's own screens).

1.68.0

  • APIs: allow_user_api_keys.
  • Users: their API keys, listed and revoked.
  • The audit log's and webhooks' user.api_key_created and user.api_key_revoked.
  • The problems api_keys_not_allowed and api_key_limit_reached.

2026-10-19

1.67.0

  • The audit log's and webhooks' brand.app_registrations_full: a brand's issuer refuses apps that register themselves once it holds 1,000 of them.

2026-10-09

1.66.2

  • Descriptions: link_by_email names the providers that vouch for an address: Google for Gmail and a Workspace account's own domain, Apple, and Microsoft with xms_edov.

2026-10-07

1.66.1

  • Descriptions: a person's access token comes from Synq's own issuer, the synq brand on the accounts host, not a console brand.

1.66.0

  • Custom domains: only a domain whose DNS proved its hostname holds it, so hostname_taken means another brand proved it first or served on it in the last 30 days.
  • The problem code hostname_taken, when a domain's record points at it but another brand holds the name.
  • A failed domain no longer holds its hostname.

1.65.0

  • Brands: a custom domain, GET, POST and DELETE /v1/orgs/{org}/brands/{brand}/custom-domain and POST …/custom-domain/verify, on plans with branding.custom_domain, now available.
  • Problems custom_domain_exists, hostname_taken, invalid_hostname, apex_not_supported, reserved_hostname, hostname_denied and hostname_not_allowed_here.
  • A brand's custom_domain_issuer.

1.64.0

  • Plans: the feature branding.custom_domain, coming.
  • The audit log's and webhooks' brand.custom_domain_added, _verified, _activated, _failed, _suspended, _restored and _removed.

1.63.0

  • Files: a brand's logo and background are uploaded straight to Synq's storage through POST …/brands/{brand}/files and …/files/{file}/finalize, and read at GET …/files/{file}.
  • PUT …/logo and PUT …/theme/background, which took the bytes, are gone.
  • The audit log's and webhooks' file.uploaded, file.rejected and file.downloaded.

1.59.0

  • Token gates: an answer's rule (TokenGateShownRule) carries its lists that grow (chain, wallets, collection_kind) as x-extensible-enum.
  • A dry run of a draft reads it from the chain as saving it would (400 at its path, 503).
  • PATCH asks the plan only for what changes.

1.58.1

  • Token gates: writing one reads what its rule names from the org's own reads (token_gate.org_reads), 429 once they're spent, and only once nothing else in the request is wrong.

1.58.0

  • Token gates: a collection condition may name a Token-2022 group, whose members are the mints its member extension names.
  • Each collection condition says what it is (collection_kind).

1.57.0

  • Token gates: POST /v1/orgs/{org}/token-gates/check, a dry run of a gate or a draft rule against wallets or a user's wallets in a brand, with the verdict tree, reads and the refusal page's words.
  • The audit log's and webhooks' user.token_gate_dry_run.

1.56.0

  • Token gates: a rule in place of one mint and a minimum (rule: all and any groups of token, collection, NFT and allowlist conditions, each on its chain, with display), an optional window (schedule), the tenant's refusal_message and a one-line summary.
  • 409 conflict past 40 chain conditions on an app. The rule's conditions take the place of a gate's mint, min_amount and chain.

1.55.0

  • Token gates: making one takes chain, in place of cluster.

1.54.1

  • A reply-to on a sending domain the org verified is confirmed at once, as it was already, and is a plain ASCII address: the descriptions say so.

1.54.0

  • Sending domains verify and are watched: "check now" verifies one whose records are there.
  • The audit log's and webhooks' email_domain.verified and email_domain.failed.

1.53.0

  • Brands: a brand's email from one of the org's sending domains once verified (sender on GET and PATCH …/email: the domain, the part before the @ and the name), <brand> via Synq otherwise.
  • POST …/email/test.
  • A sending domain's used_by, and 409 email_domain_in_use while a brand sends from it.

1.52.0

  • Sending domains, on plans with branding.custom_email_domain: /v1/orgs/{org}/email-domains (list, add, read, check, delete).
  • Permissions org.emailDomains.view and .edit.
  • Problems email_domain_unavailable, email_domain_invalid (with reason) and email_domain_limit_reached.
  • The audit log's and webhooks' email_domain.created and email_domain.deleted.

1.51.0

  • Brands: GET and PATCH /v1/orgs/{org}/brands/{brand}/email, a reply-to address on every plan, confirmed by whoever reads it, and what the next email carries.
  • POST …/email/reply-to/confirmation.
  • The audit log's and webhooks' brand.reply_to_confirmed.

2026-10-06

1.50.0

  • Brand themes: glow_color, and the font source-sans that Synq serves from the brand's own issuer host.
  • A theme's font in an answer is x-extensible-enum, since the list grows.

1.49.0

  • Token gates: each names its chain (chain, solana:mainnet), optional on create (the chain this API reads), changeable.
  • The gate list's chains, the chains this API reads.

1.48.0

  • Apps: initiate_login_uri, where the brand's signed-out page sends someone to sign in again, beside client_uri, its "Back to" link.

2026-10-05

1.47.1

  • Brands: the contract says primary_color, background_color and the theme's surface_color take null to unset them, as the API always did.

1.47.0

  • Change requests: an app's redirect URIs, asked for from an MCP host and approved in the dashboard.

1.46.0

  • Billing through Stripe: POST /v1/orgs/{org}/billing/checkout, …/billing/plan (an upgrade now, a downgrade at the period's end), …/billing/portal and GET …/billing/invoices.
  • Problems plan_not_sold, subscription_exists, no_billing_account, no_subscription and payment_failed.
  • The plans' price examples are Stripe's.

1.45.0

  • The audit log's and webhooks' user.looked_up, when Synq's staff looked a brand's users up, with their reason.

1.44.0

  • Orgs: disabled_at and disabled_reason, when Synq's staff disabled one, which can then only be read (403 forbidden otherwise, and for its API keys).
  • The audit log's and webhooks' org.disabled and org.enabled.

2026-10-04

1.43.0

  • A native app's redirect and post-logout URIs may use a scheme of its own, a reverse domain name such as com.example.app:/callback (RFC 8252).

1.42.0

  • Sign-in providers: matrica.

1.41.0

  • Sign-in providers: telegram.

1.39.0

  • Orgs: GET /v1/orgs/{org}/permissions, the caller's own permissions in an org, for a dashboard to offer only what they may do.

1.38.0

  • Sign-in providers: an app a tenant brings registers each brand's own callback, on its issuer's host: a brand's app its redirect_uri, an org's app redirect_uris, one per live brand, in place of its single redirect_uri.
  • A brand's sign-in providers name its redirect_uri.
  • Making a brand warns org_provider_apps_need_redirect_uri (ticket to follow).

2026-10-03

1.37.0

  • Brands: the hosted pages' theme, GET and PATCH /v1/orgs/{org}/brands/{brand}/theme, its preview and its background image.
  • The advanced settings need branding.advanced_theme and hiding "Powered by Synq" branding.remove_powered_by, which plans now give.

1.36.0

  • Sign-in providers: facebook and x.

1.35.0

  • Sign-in providers: apple.
  • An Apple app is its Services ID with team_id, key_id and private_key, from which Synq signs its client secrets.
  • A provider's name in an answer is x-extensible-enum, since the list grows.

1.34.1

  • Brands: one deleted in the last 30 days still counts against the plan's brands, in making one and in the usage.

1.34.0

  • Token gates: an org's gates on its brands and apps, Pro and up, checked at every sign-in and refresh, 409 token_gates_unavailable where the API reads no chain.
  • The audit log's and webhooks' token_gate.created, token_gate.updated, token_gate.deleted and user.token_gate_checked.

1.33.0

  • Apps: refresh_token_reuse_window_seconds, a web app's reuse window for rotated refresh tokens.
  • The audit log's and webhooks' app.refresh_token_replayed.

1.32.0

  • Apps: a web app or SPA may register https redirect URIs on a loopback address, and warnings, such as loopback_redirect_uris deployed.
  • A host ending in a dot is refused.

1.31.0

  • Webhooks: a subscription receives only events recorded after it exists and while it is on and wants them.

1.30.0

  • Billing: GET /v1/orgs/{org}/billing/usage, monthly active users against the plan's allowance, and apps and brands against its limits.

1.29.0

  • Plans: GET /v1/plans, public.
  • Orgs: plan.
  • Apps, brands and webhooks follow the org's plan, 403 plan_quota_exceeded and plan_feature_unavailable naming the plan that allows it.
  • The audit log's and webhooks' org.plan_changed.

1.28.0

  • Brands: show_last_used, the sign-in page's "Last used" mark.

1.27.0

  • Users: their consents, listed and withdrawn.
  • The audit log's and webhooks' user.consent_granted and user.consent_revoked.

1.26.0

  • Users: disabling one, ending their sessions or scheduling their deletion tells each app of their sessions over the back channel.

1.25.0

  • Orgs and brands: their own apps at each sign-in provider, checked with the provider, 422 connection_rejected.
  • A brand's sign-in providers show the app each signs in through and whether it is offered.

1.24.0

  • Users: their passkeys, listed and removed.

1.23.0

  • Users: each identity's id, a wallet's label and primary.
  • The audit log's and webhooks' user.identity_unlinked.

1.22.0

  • Brands: sign-in providers' microsoft_tenant.

1.21.0

  • Brands: sign-in providers, each off until turned on.
  • The audit log's and webhooks' user.identity_linked.

1.20.0

  • Webhooks: user.passkey_added and user.passkey_removed.

1.19.0

  • Orgs: making one wants a verified email, 403 email_unverified.

1.18.0

  • The audit log's and webhooks' user.password_reset.

1.17.0

  • The audit log's and webhooks' user.email_verified.

1.16.0

  • Apps: backchannel_logout_uri and backchannel_logout_session_required.

1.15.0

  • A change to what only Synq itself uses, outside the public contract.

1.14.0

  • Orgs: making one follows Synq's sign-up policy and a cap per person, 403 org_creation_closed and org_quota_exceeded.
  • Handing one over follows the cap, 403 recipient_org_quota_exceeded.

2026-09-30

1.13.0

  • Invites: 422 email_undeliverable.
  • An invite whose email can't go is revoked.

1.12.0

  • Brands: breached_password_check.

1.11.0

  • Apps: agents.

1.10.0

  • Webhooks, and the event catalog.

1.9.0

  • Brands: sign_in_cancels_deletion.

1.8.0

  • Members, roles and invites.

1.7.0

  • Users.

1.6.1

  • The audit log's actions name the account API's.

1.6.0

  • API keys.

1.5.1

  • A change to what only Synq itself uses, outside the public contract.

1.5.0

  • APIs, and apps' access to them.

1.4.0

  • Apps.

2026-09-28

1.3.0

  • Brands: logos.

1.2.0

  • Orgs: make, change the slug, delete.
  • Brands.
  • Slug checks.

1.1.0

  • Orgs: change.
  • The audit log.

1.0.0

  • Orgs: list and read.

Account API

The account API's versions before 1.9.0 were not logged one by one.

2026-11-17

1.36.1

  • finish: app only for a native app of the brand's own, never where the brand's link_reauth_window is 0.
  • POST /v1/link-results is rate limited per person (account.link_results), and its other refusals carry fixed words (the security review of).

1.36.0

  • Links an app redeems itself: a link request's finish (app from a sign-in within the brand's link window), whose browser does only the method being added, signs nobody in and comes back to the app with synq_link_result.
  • POST /v1/link-results joins it, with the authorization request's PKCE code_verifier, for the app and person that started it, once (link_result_invalid otherwise).

1.35.1

  • A link request's authorization_params carry synq_method, the way the person signed in, whenever it is known, not only where confirmation.needed: a native app's sign-in never reaches the browser the hosted page opens in, so the page confirms it's them there with that way at once rather than listing every way.

1.35.0

  • A wallet's chain, solana today, the shape a token's and userinfo's wallets claim carry too.

2026-11-15

1.34.0

  • A body that isn't JSON is 400 invalid_json, saying where it broke and what JSON needs there, and one sent without Content-Type: application/json is 415 unsupported_media_type, naming the type sent: both were 500 internal_error, and nothing ran.
  • A validation_failed field left out says it's required, with the values it takes.

2026-11-14

1.33.3

  • A validation_failed problem names each field a body doesn't take at its own pointer, with the field it likely meant.
  • A value of the wrong type gets its invalid_type alone.
  • A field's code is always one the docs list, a check of the API's own invalid_value.

1.33.2

  • A session's id has an example, as every other id does.

2026-11-13

1.33.1

  • The contract's descriptions name no tickets.

2026-11-11

1.33.0

  • A consent's scope_descriptions, everything allowed in the consent page's words.

2026-11-10

1.32.1

  • default_picture is absent where the brand's plan doesn't include its own default avatars.

2026-11-09

1.32.0

  • Moving a wallet on its own proof: a wallet another account has, which keeps another way in, moves here on the signature just made where the brand moves on it (move_proved_identities, on by default): POST /v1/wallets's wallet_in_use carries its move_ticket then, and POST /v1/wallet-moves moves it, recorded with on_own_proof: true.

1.31.0

  • Each way GET /v1/link-methods lists carries its confirmation, what adding it asks of the person first, and every confirmation names its way as people say it, with_name.

1.30.0

  • Adding a way in without signing in again: a sign-in on the device within the brand's link_reauth_window (2 hours unless the tenant chose otherwise) stands in, whichever way it signed in.
  • A link request answers confirmation, whether the person confirms it's them first and with which way, and its authorization_params carry synq_method for that way.
  • POST /v1/wallets takes a sign-in within that window instead of the last 5 minutes, and its fresh_sign_in_required carries confirm_with.

1.29.0

  • Accounts the tenant's app verifies: POST /v1/link-codes, GET /v1/pending-identities, POST /v1/identities/{identity}/confirm and …/reject, an identity's added_by, the problem identity_in_use, and a sign-in link's session never deleting the account.

1.28.0

  • A brand's own sign-in providers: GET /v1/link-methods lists each by its id (custom-…) and name, and POST /v1/link-requests adds one as { method: 'custom', provider }.

1.27.0

  • GET /v1/username-suggestions, usernames from the on-chain names of the wallets a person signs in with, a Seeker ID's.

1.26.0

  • A new API key ends with a checksum, the CRC32 of its secret in base62, so a made-up one is refused with no call.
  • One without a checksum no longer works.

2026-11-08

1.25.0

  • POST /v1/wallets answers merged_from, the empty account merged in to add the wallet where the brand merges empty accounts.

2026-11-01

1.24.0

  • Pictures people choose and defaults each app draws: a profile's picture_source, avatar_seed, default_picture and picture_choices, an identity's has_picture, uploading a picture (POST /v1/profile/picture/uploads, PUT /v1/profile/picture), using a linked account's, removing it, and the problems picture_unavailable and storage_unavailable.

1.23.0

  • Adding a wallet with one signature, POST /v1/wallets and POST /v1/wallet-moves, the problems wallet_in_use and wallet_signature_rejected, and a wallet's wallet_app.

1.22.0

  • A username that is taken comes with suggestions.
  • An identity at a provider carries provider_user_id and the scopes granted.
  • A link request skips signing in again within the brand's link_reauth_window.

1.21.0

  • Every list pages, limit and cursor answered with { data, next_cursor }, 50 by default: sessions, consents, APIs, API keys, sign-ins (all Synq keeps, not the last 50), identities, wallets, link methods and passkeys.
  • A session's via and a username's reason are x-extensible-enum.

1.20.0

  • A path id that isn't one of its kind is 400 validation_failed, not 404.
  • Validation errors are { pointer, code, detail }, with no path or message.

2026-10-31

1.19.1

  • last_sign_in_method counts only the ways the brand still offers.

1.19.0

  • A brand that turned passkeys off makes and keeps none, 409 sign_in_method_unavailable.

2026-10-30

1.18.0

  • Passkey availability in the add-method list.

1.17.0

  • Available link methods and adding every provider.

1.16.0

  • API quota headers and method_not_allowed problems.

2026-10-25

1.15.1

  • Stable operation IDs for every account route.

1.15.0

  • Optional validation code, detail and JSON-body pointer.

1.14.0

  • Problem request_id, optional retry_after and safe internal-error guidance.

2026-10-23

1.13.0

  • GitHub, as an identity's provider and a way to sign in to add.

2026-10-20

1.12.0

  • An identity's handle, the person's username at X, Discord, Telegram or Matrica.

1.11.0

  • A session's via: the hosted page, or an app's own screens.

1.10.0

  • API keys for the brand's APIs, /v1/apis and /v1/api-keys, and the problems api_keys_not_allowed and api_key_limit_reached.

2026-10-07

1.9.0

  • A problem may carry reason, why, for code to read.

MCP tools

What changed in the tools tools/list answers at https://api.synq.build/mcp, the one catalog every connected host has (MCP tools): a tool's name, description, input or hints, and changes to how a tool behaves.

2026-11-17

  • Changed: get_connection and request_configuration_change.

2026-11-16

  • Changed: get_reference, request_configuration_change and update_configuration.
  • get_reference's permissions says what each permission allows, then who holds it, with two more facts: in_brands (whether a brand role can hold it, or it is the org's alone) and comes_with (the permission that reads what a change changes, which it brings). Its org.read says that no role needs it to open the org: every member sees their orgs and their own permissions with none. create_role and update_role say to give only what the person asked for.

2026-11-15

  • Changed: get_configuration, get_reference, list_audit_log and request_configuration_change.

2026-11-14

  • Added: preview_sign_in.
  • Changed: get_app_quickstart, get_approval_request, list_audit_log, request_api_key, request_app, request_brand, request_configuration_change, request_invite, request_redirect_uris_change and request_sign_in_provider_change.

2026-11-13

  • Changed: get_approval_request, get_connection, request_api_key, request_app, request_brand, request_configuration_change, request_invite, request_redirect_uris_change, request_sign_in_provider_change and update_configuration.

2026-11-11

  • Added: get_approval_request and request_brand.
  • Changed: add_custom_domain, check_custom_domain, check_user_sign_in, create_brand, get_app, get_app_quickstart, get_change_request, get_configuration, get_connection, get_custom_domain, get_reference, get_sign_in_providers, list_apps, list_audit_log, list_users, list_webhook_deliveries, list_webhooks, request_api_key, request_app, request_configuration_change, request_invite, request_redirect_uris_change, request_sign_in_provider_change, send_webhook_delivery and update_configuration.
  • Removed: add_custom_domain, create_brand and get_change_request.

2026-11-10

  • Changed: get_configuration, get_reference, request_configuration_change and update_configuration.

2026-11-09

  • Changed: get_app, get_configuration, get_reference, request_api_key, request_configuration_change, request_sign_in_provider_change and update_configuration.

2026-11-08

  • Added: update_configuration.
  • Changed: create_brand, get_configuration, get_connection, get_reference, request_api_key, request_app, request_configuration_change and request_invite.
  • Removed: set_brand_colors.

2026-11-07

  • Changed: request_api_key.

2026-11-01

  • Added: check_custom_domain, check_user_sign_in, create_brand, get_app_quickstart, get_change_request, get_configuration, get_connection, get_reference, request_api_key, request_app, request_configuration_change, request_invite, request_sign_in_provider_change, send_webhook_delivery and set_brand_colors.
  • Changed: add_custom_domain, get_app, get_custom_domain, get_sign_in_providers, list_apps, list_audit_log, list_users, list_webhook_deliveries, list_webhooks and request_redirect_uris_change.
  • Removed: get_brand, list_brands, list_orgs, send_test_webhook, set_app_sign_in_methods, set_app_test_sign_ins, set_brand_colours, set_sign_in_method, set_sign_in_provider and verify_custom_domain.
  • /mcp serves one catalog, the tools MCP tools lists, in place of the 20 launched tools: list_orgs, set_brand_colours, verify_custom_domain and the others are gone, as are their argument names (org, brand, app, webhook, now org_id, brand_id, app_id, webhook_id) and the ?catalog=2026-10 selector. A host that learned the old tools lists them again and sees the new ones; get_connection is where to start.

2026-10-31

  • Changed: set_app_sign_in_methods, set_app_test_sign_ins, set_sign_in_method and set_sign_in_provider.
  • set_sign_in_provider, set_sign_in_method, set_app_sign_in_methods and set_app_test_sign_ins now ask for a person's approval in the Synq dashboard instead of making the change. Each answers that nothing changed yet, with an approve_url to share; the change is made only once the same person approves it there. Their names and inputs stay the same. Calling one again can make another pending request, so wait for the person instead of retrying.

2026-10-23

  • Added: set_app_sign_in_methods, set_app_test_sign_ins and set_sign_in_method.
  • Changed: get_app, get_brand, get_sign_in_providers and set_sign_in_provider.

2026-10-07

  • Added: add_custom_domain, get_custom_domain and verify_custom_domain.

2026-10-05

  • Added: request_redirect_uris_change.

2026-10-04

  • Changed: get_sign_in_providers and set_sign_in_provider.

2026-10-03

  • The first tools: get_app, get_brand, get_sign_in_providers, list_apps, list_audit_log, list_brands, list_orgs, list_users, list_webhook_deliveries, list_webhooks, send_test_webhook, set_brand_colours and set_sign_in_provider.

On this page