Submit per-user-headers values

Consumes a pending submission flow row: verifies the caller’s values against the upstream MCP server, upserts the credential keyed by the flow row’s (mode, identity), then deletes the flow row and the bound temp token. Mirrors the OAuth callback’s “complete the flow” semantics.

Values for any key not in the live per_user_header_keys schema are dropped server-side so a stale UI can’t persist deprecated keys.

PUT /api/mcp/per-user-headers/flows/{id}

Error

A valid request URL is required to generate request examples

200

{
  "credential_id": "<string>",
  "updated_at": "2023-11-07T05:31:56Z"
}

Authorizations

Authorization · string · header · required

Management API authentication for /api/* endpoints. Use the Authorization header with Bearer <API key>. Virtual keys, dashboard/user/session tokens, and x-api-key headers are not supported on management APIs.

Path Parameters

id · string · required

Flow row ID

Body

application/json

Request body for PUT /api/mcp/per-user-headers/flows/{id}. The flow row identifies the (mode, identity, mcp_client) triple, so the caller carries only the values. Extra keys not in the live per_user_header_keys schema are dropped server-side.

headers · object · required

Show child attributes

Response

200

application/json

Credential persisted

status · enum<string> · required

Available options: success

credential_id · string · required

updated_at · string<date-time> · required