Configuration

Set a credential provider config

Changed on

Set (create or update) a credential provider config at runtime.

The payload is validated by provider name (e.g. pipedream). Secret fields are encrypted at rest. A successful write rebuilds the in-process provider registry so the change takes effect without a restart. The response redacts secret fields.

put/admin/config/providers/{name}

Request

  • Base URL: / (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /admin/config/providers/{name}
  • Auth: one of:
    • HTTP bearer
    • OAuth 2 (authorization code, authorization URL /authorize, token URL /oauth/token)

Path parameters

namestring required

Provider name, e.g. pipedream.

Example:pipedream

Request body

configobject required

Provider-specific configuration fields, validated by provider name.

Example request

{
  "config": {
    "client_id": "client_abc123",
    "client_secret": "<redacted>",
    "environment": "production",
    "project_id": "proj_abc123"
  }
}

Response

Successful Response

configobject required

Stored config with secret fields redacted.

created_atstring date-time required

When the provider config was created (RFC 3339).

namestring required

Provider name (e.g. 'pipedream').

updated_atstring date-time nullable

When the provider config was last updated (RFC 3339); null if never updated.

Example response

{
  "config": {
    "client_id": "client_abc123",
    "client_secret": "***",
    "environment": "production",
    "kind": "pipedream",
    "project_id": "proj_abc123"
  },
  "created_at": "2026-06-29T12:00:00Z",
  "name": "pipedream",
  "updated_at": "2026-06-29T12:00:00Z"
}

Changes