Revoke tenant authorizations

Revoke every authorization your application currently holds for a tenant, across all scopes. Use this when your application should disconnect from a user's agrirouter account, for example when the user closes their account with you or unlinks agrirouter in your application. It is the API counterpart of the user clicking Revoke in the agrirouter UI (see Managing Authorizations).

The application is taken from the access token. Like the endpoint operations, the tenant is passed in the x-agrirouter-tenant-id header.

Today an authorization exists only for the endpoints:manage scope, so this removes that single authorization. If additional scopes are introduced later, this operation revokes all of them at once.

Delete your endpoints first

The call is rejected with 409 Conflict while your application still has at least one endpoint in the tenant, and nothing is revoked. Endpoints of other applications in the tenant do not count.

This protects integrations that connect more than one instance of the same platform to one agrirouter account. Without the check, revoking from one instance would also disconnect the other instances. Disconnect in this order:

After a 204 response, you receive an AUTHORIZATION_REVOKED event for each revoked authorization on GET /events.

A 404 means your application holds no authorization for the tenant, for example because it was already revoked. Treat it as "already disconnected".

curl -X DELETE "https://api.agrirouter.com/authorizations" \  -H "x-agrirouter-tenant-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08"

{
  "message": "string"
}

{
  "message": "string"
}

{
  "message": "string"
}

{
  "message": "string"
}

{
  "message": "string"
}