Skip to main content
POST
Submit and validate provider credentials

Authorizations

Authorization
string
header
required

Authorization: Bearer <token>. Token types resolve to the same scoped credential: a user-generated API key (casa_…, from Account settings — recommended for machines and MCP clients), a WorkOS AuthKit session JWT (the web app; org and role come from verified token claims), or a static token. API keys are group-scoped, optionally pinned to one property at creation. MCP OAuth connector tokens authenticate the MCP server only and are rejected on these REST routes.

Path Parameters

id
string<uuid>
required

Resource id (UUID).

Body

application/json

Provider-specific credential fields (e.g. access_token, client_token).

Response

Validated and stored.

status
string
Example:

"connected"