me

Set Provider Key

Set or update a provider API key for this identity.

Upserts: if a row exists, updates the key and re-activates. Key is encrypted with Fernet before storage when FERNET_KEY is configured.

TOS-6394: an admin/owner has no way to tell, from this endpoint alone, whether a key they mean for the whole install actually needs the admin platform-key surface instead. A real incident on the Heartwood Guild install (2026-09-17) left a platform-intended ElevenLabs key sitting here, under one person's identity, for a month with nothing surfacing the mismatch. The response now carries a one-line hint when the saving identity is an admin/owner and the platform has no active key for this provider yet - advisory only, never blocks or redirects the save, because a personal key for a provider the platform also happens to lack is a completely ordinary case.

put/api/me/provider-keys/{provider}

Request

  • Base URL: https://app.thinqos.com (the document declares no server; this is the origin it was published from)
  • URL: https://app.thinqos.com/api/me/provider-keys/{provider}
  • Auth: none declared

Path parameters

providerstring required

Headers

x-impersonate-identity-idstring nullable

Request body

api_keystring required
provider_scopestring nullable

Response

Successful Response

okboolean
providerstring required
validboolean nullable
validation_errorstring nullable
provider_scopestring nullable
scope_outcomestring nullable
scope_candidatesstring[]
scope_detailstring nullable
batch_eligibleboolean
platform_key_hintstring nullable

Changes

No recorded changes to this operation across all 2 revisions of this API.