SnozeDevelopers
API referenceIntegrations

Start an OAuth install for a provider

Begins a provider install and returns the provider authorization URL, the opaque `state` token to echo back, and the expiry after which the attempt is void; the browser completes the flow at the provider and Snoze exchanges the code on the separate callback route, so no secret ever passes through this endpoint. Requires the `integrations:write` workspace permission. Fails when the provider is unknown, when the provider feature is disabled for the workspace, when the provider is manual-setup only, or when the deployment is missing the configuration that provider requires. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.

POST
/v1/workspaces/{workspaceId}/integrations/providers/{provider}/install

Authorization

apiKey
headerAuthorizationBearer <snoze_sk_…>

Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.

Path Parameters

workspaceId*string
provider*string

Request Body

application/json
  1. body
discordLinkChallenge?string|null
label?string|null
key?string|null
manifest?|null
redirectTo?string|null

Response Body

Success

application/json
  1. response
data*
Example Request
curl -X POST 'https://api.snoze.dev/v1/workspaces/string/integrations/providers/string/install' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{  "data": {    "provider": "string",    "installKind": "github_app",    "url": "string",    "state": "string",    "expiresAt": "string"  }}

List connector capabilities for every provider

Returns the connector catalog — the object types each provider can mirror and the migrations it offers — so a client can present what a connection would bring in before one exists. Authorized through the same `integrations:read` check as the provider-operations read path.

List the integration connections in a workspace

Returns the workspace's provider connections with their label, provider, enabled state, and sync status. Requires the `integrations:read` workspace permission; stored credentials are not included.