Move a connection's key from the deployment to a stored value
The operator (installation.settings.manage, the workspace owner), signed in; an API key is 403 whatever its scopes. For a connection whose key comes from the operator's deployment (an env or Secrets Manager reference): the person types the key, it is sealed under the same id, and the row is stored from then on. The server does not read the referenced value. Ceilings made before keep running on the stored key and their pins do not change. A settings document that still names the old entry leaves the row as it is. A connection that already keeps its own value is 409 not_external, a disabled one 409 disabled, one that another connection is or was exactly 409 alias_taken, the secret store off 503. Writes a set_settings_credential receipt naming the last four characters and which reference it replaced.
Auth: cookie session only; no scope. Idempotency-Key: ignored.
cookieSession__Host-werft_session<token>For the web console: the browser session cookie set by POST /v1/auth/login. It holds the scopes of the user's workspace role (owner: all; admin and member: all but sessions:recover). Requests other than GET must also send X-Requested-With: werft-web.
id*stringThe model connection's id.
1 <= lengthX-Requested-With?"werft-web"Required with a cookie session: the literal werft-web.
"werft-web"application/json- body
value*string1 <= length <= 8192The entry's id and the change's receipt.
application/json- response
id*string1 <= lengthreceipt_id*string^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidcurl -X POST 'https://example.com/v1/installation/settings/connections/string/convert' \ -H 'Content-Type: application/json' \ -d '{ "value": "example-key"}'{ "id": "anthropic-main", "receipt_id": "019a0000-0000-7000-8000-0000000000f3"}