Skip to main content
Paths are relative to /api/v1. All routes use a project-scoped API key - Authorization: Bearer <api_key> - that must belong to the project in the path. See Authentication for scopes. Provider-specific credential fields and fallback behavior are described in Integrations. Secret values are accepted on writes but are never returned by list responses. Connections use a priority-only fallback contract. On connect, the server derives priority: reconnecting preserves its place and new connections append to the fallback chain. PATCH a priority of 0 to promote and renumber the chain; other priority values reorder it. The generated OpenAPI JSON remains the machine-readable source of truth for request and response schemas.