Update Credential
Update the fields you send. Send api_key to rotate the key. The vendor
can’t change: delete the credential and create a new one to switch vendors.
Authentication
A management key (mgmt_...), sent as Authorization: Bearer <key>. Reading /v1/routing-policies also accepts the organization’s gateway API keys; writing there needs a management key.
Path parameters
The credential’s id.
Request
A custom base URL for the vendor’s API, such as your own proxy. null or "" keeps the current value: once set, it can’t be cleared. Delete and create the credential to remove it.
Only the config fields sent change; none can be cleared.
When a request with this key fails, retry it once on Merge-managed access for the same vendor, if the organization has it.
A name for the credential, shown in the dashboard. null or "" keeps the current value: once set, it can’t be cleared. Delete and create the credential to remove it.
Response
The non-secret vendor settings. Settings that aren’t set are null.
The last 4 characters of the stored API key, like a1b2, to tell keys apart. null when the credential has no API key, or the key is under 12 characters (4 would give away too much of it).
When a request with this key fails, retry it once on Merge-managed access for the same vendor, if the organization has it.
The vendor’s slug, like openai. Can’t change after creation: delete the credential and create a new one to switch vendors. An organization has at most one credential per vendor.