Revoke Connection
Disconnect an app.
Spends every refresh token under the grant at once, so the app cannot rotate its way back in and has to go through consent again. Access tokens already issued are not hunted down - they expire on their own within minutes, which is the price of not keeping a revocation list and the reason that lifetime is short.
No step-up, like every other revoke here: revocation is the fail-safe direction, and a password prompt is a cost paid at exactly the wrong moment. Session-only, because ending the credentials an incident response depends on must not itself be doable with a credential.
Authentifizierung
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
Pfad-Parameter
uuiduuidResponse-Body
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/organizations/497f6eca-6276-4993-bfeb-53cbbbba6f08/connections/497f6eca-6276-4993-bfeb-53cbbbba6f08"