Connections
Connect a provider
Bring a key for a provider (yours, or your customer’s).
The key is checked live where the provider has a probe (a rejected key is never stored), then stored encrypted. The next call of a connection-tier agent runs on it. Nothing secret comes back.
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
google, azure for Microsoft 365, github, slack, stripe, …). The connect pointer in a 424 names it.Body
application/jsonMaximum string length: 4096
Maximum string length: 4096
Pattern: ^(?!.*\.\.)[A-Za-z0-9_.-]{1,128}$
Available options: json, yaml, markdown, text
Response
Connected Response format negotiates via the format field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
application/jsontext/yamltext/markdowntext/plain
Available options: connected
credential_rejected — the provider refused the key; missing_api_key — api_key is required; invalid_json / invalid_yaml / invalid_body — unreadable body; invalid_format — format must be one of json, yaml, markdown, text; invalid_on_behalf_of — on_behalf_of must be 1-128 characters of A-Z a-z 0-9 _ . - (no "..")
application/json
unauthorized — missing, invalid or revoked ozk_ key
application/json
unknown_provider — no connector with that provider id; connection_not_found — nothing to disconnect; not_found — no route for this method on this path: every other method answers it
application/json
connections_unavailable — connections are not available on this deployment
application/json