SnozeDevelopers
API referenceIntegrations

List the integration providers available to a workspace

Returns the provider catalog annotated for this workspace: whether the provider is enabled by feature flag and whether the Snoze deployment is configured with the credentials the provider needs. Requires the `integrations:read` workspace permission. No credential values are returned, only whether configuration is present.

GET
/v1/workspaces/{workspaceId}/integrations/providers

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

Response Body

Success

application/json
  1. response
data*array<>
Example Request
curl -X GET 'https://api.snoze.dev/v1/workspaces/string/integrations/providers'
Example Response
{  "data": [    {      "provider": "string",      "label": "string",      "category": "string",      "authKinds": [        "api_key"      ],      "capabilities": [        "string"      ],      "installKind": "github_app",      "credentialScope": "installation",      "enabled": true,      "configured": true,      "installFields": [        {          "key": "string",          "label": "string",          "required": true,          "placeholder": "string",          "secret": true        }      ],      "docsUrl": "string",      "experience": "deep"    }  ]}

Rotate an asset's access key

Issues a fresh access key for the file and returns it, which invalidates every capability URL previously handed out for that file. Requires a workspace member with the `files:write` permission; an unknown or malformed file id is reported as not found.

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.