Enable a provider your app verifies
Turns it on: people link accounts at it, your server adds them and, where `sign_in_tickets` is on, makes sign-in links. Needs `org.brands.edit`. Recorded as `brand.updated`, naming `custom_sign_in_provider.enabled`.
/v1/orgs/{org}/brands/{brand}/app-verified-providers/{provider}/enableTurns it on: people link accounts at it, your server adds them and, where sign_in_tickets is on, makes sign-in links. Needs org.brands.edit. Recorded as brand.updated, naming custom_sign_in_provider.enabled.
Authorization
bearer An org API key (sk_live_…, sk_test_…), or an access token from the Synq issuer (the synq brand, on the accounts host) for this API.
In: header
Path Parameters
The org's id
^org_[0-9a-hjkmnp-tv-z]{26}$The brand's id
^brd_[0-9a-hjkmnp-tv-z]{26}$The provider’s id
^custom-[a-z0-9]([a-z0-9-]{0,23}[a-z0-9])?$Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/brands/brd_01h455vb4pex5vsknk084sn02q/app-verified-providers/custom-acme-telegram/enable" \ -H "Authorization: Bearer $SYNQ_API_KEY" \ -H "Content-Type: application/json" \ -d '{}'{ "id": "custom-acme-telegram", "name": "Acme", "icon": "string", "sign_in_tickets": true, "enabled": true, "created_at": "2026-10-21T12:00:00.000Z", "updated_at": "2026-10-21T12:00:00.000Z"}Disable a provider your app verifies POST
Turns it off: no link code is made or redeemed, nothing pending is confirmed, your server adds no identity there, and every sign-in link is refused at once, those made already included. The accounts linked there stay. Needs `org.brands.edit`. Recorded as `brand.updated`, naming `custom_sign_in_provider.enabled`.
Add a provider your app verifies POST
A provider whose people your own service proves, such as your Telegram bot or your game's server: a name and an icon, with no address or app at Synq, since your server says who someone is there. People link an account at it from your app with a link code (`POST /me/v1/link-codes`), which your server redeems (`POST …/link-codes/redeem`) and they confirm in the app; your server can add one for someone it knows (`POST …/users/{user}/identities`); and where `sign_in_tickets` is on, it makes sign-in links for them (`POST …/sign-in-tickets`). It is never a way to sign in on the brand's pages, and never counts as one. It is off until `POST …/enable`. At most 20 of the brand's own providers of every kind (409 `conflict`); an id the brand has is 409 `sign_in_provider_exists`. Needs `org.connections.edit`, and a person's sign-in from the last 5 minutes for `sign_in_tickets` (403 `fresh_sign_in_required`). Recorded as `brand.updated` with `provider` and each setting under `custom_sign_in_provider.`.