Delete a verified domain
The org no longer holds the name, and another org may prove it at once. Its people are no longer sent to the org's identity provider by their address. On any plan, so an org that moved down can clean up. Needs `org.sso.edit` across the org. Recorded as `org_domain.deleted`.
/v1/orgs/{org}/domains/{domain}The org no longer holds the name, and another org may prove it at once. Its people are no longer sent to the org's identity provider by their address. On any plan, so an org that moved down can clean up. Needs org.sso.edit across the org. Recorded as org_domain.deleted.
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 domain's id
^odm_[0-9a-hjkmnp-tv-z]{26}$Response Body
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X DELETE "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/domains/odm_01h455vb4pex5vsknk084sn02q" \ -H "Authorization: Bearer $SYNQ_API_KEY"Start adding Synq’s bot to a Discord server POST
A link to Discord's own install screen for Synq's bot, good for 15 minutes and once: Discord asks the person which server, and shows what the bot may do there (Manage Roles, View Channels, Send Messages, Embed Links and Pin Messages; adding a bot takes Manage Server there). Discord then sends them to the API, which connects the server to the org for `brand` (fixed from then on: its members verify on its hosted pages and become its users) and sends them back to the dashboard at `return_path` with `discord` set to `connected` (and `server`), `cancelled`, `taken` (another org has it), `full` (the org has 25), `expired` (the link sat past its 15 minutes), `used` (it was used already) or `failed`. Members verify on the brand's hosted pages: they sign in the way they already do, link Discord on their member profile and show what they hold with Solana wallets, so the brand must offer wallets (400 at `brand` with the fix); it needn't offer Discord sign-in. Needs `org.integrations.edit` and a plan with token gating (403 `plan_feature_unavailable`). Recorded as `discord_server.connected` when it comes back.
Read a verified domain GET
Its status, its TXT record and what Synq saw at the last check. Needs `org.sso.view` across the org, on any plan.