---
title: "Set a credential provider config"
method: PUT
path: "/admin/config/providers/{name}"
tags: ["Configuration"]
---

# Set a credential provider config

`PUT /admin/config/providers/{name}`

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.

## Path parameters

- `name` string, required

## Request body

- ProviderConfigSetRequest — Request body for setting a provider config. Fields are provider-specific and validated server-side by provider name. For ``pipedream`` the recognised fields are ``project_id``, ``client_id``, ``client_secret`` (write-only), and optional ``environment``, ``connect_base_url``, ``expiry_skew_seconds``.
  - `config` object, required — Provider-specific configuration fields, validated by provider name.

## Response `200`

Successful Response

- ProviderConfigResponse — A stored provider config with secret fields redacted.
  - `config` object, required — Stored config with secret fields redacted.
  - `created_at` string, date-time, required
  - `name` string, required — Provider name (e.g. 'pipedream').
  - `updated_at` string, date-time, nullable

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `422` — Unprocessable Entity
- `500` — Internal Server Error
- `503` — Service Unavailable

---

[API](https://skmtc.net/jentic/apis/jentic-control-plane-api.md) · [All operations](https://skmtc.net/jentic/apis/jentic-control-plane-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/jentic/jentic-control-plane-api/revisions/4ccade8cfa18/schema)