Update Org Key
Rename an org key, change what it may do, or both. The secret is untouched.
Open only to someone who holds what the key holds: an owner-grade key is not
editable by a member, not downwards and not even to rename it. Revoking it
stays open to them, which is the move that matters when a key is suspected.
The reasoning is in _require_authority_over.
Within that, step-up is asked only when the edit gives the key MORE than it had - a scope it did not carry, or a later expiry. Both are re-granting authority and are a mint in all but name. Narrowing and renaming pass without a factor. The ceiling for a widening is what the person editing holds today, never what the original minter held.
Authorization
bearerAuth API token generated from the fastmon dashboard (Account → API Token) or at organization level (fmo_…, one that outlives its creator). Send as Authorization: Bearer fm_... or paste the full token (including its prefix) into the Authorize dialog.
In: header
Path Parameters
uuiduuidRequest Body
application/json
Rename an org key, change its scopes, or both. Same contract as
ApiKeyUpdate, minus the reach question - an org key names one
organization by construction, so there was never a list to edit.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X PATCH "https://example.com/organizations/497f6eca-6276-4993-bfeb-53cbbbba6f08/api-keys/497f6eca-6276-4993-bfeb-53cbbbba6f08" \ -H "Content-Type: application/json" \ -d '{}'{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "kind": "personal", "name": "string", "prefix": "string", "last4": "string", "scopes": [], "expires_at": "2019-08-24T14:15:22Z", "last_used_at": "2019-08-24T14:15:22Z", "reach": { "scope": "string", "partner_org_id": "6d083317-c55a-4f41-82ae-8c86d8187f47", "organization_ids": [], "organization_count": 0 }, "created_at": "2019-08-24T14:15:22Z", "revoked_at": "2019-08-24T14:15:22Z", "editable": true}