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.
Authorization
apiKey Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/workspaces/string/integrations/providers"{ "data": [ { "provider": "string", "label": "string", "category": "string", "authKinds": [ "api_key" ], "capabilities": [ "string" ], "installKind": "github_app", "enabled": true, "configured": true, "installFields": [ { "key": "string", "label": "string", "required": true, "placeholder": "string" } ], "docsUrl": "string", "experience": "deep" } ]}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}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.