---
title: "Revoke access to authorisation"
method: DELETE
path: "/authorisations/{id}"
tags: ["Authorisations"]
---

# Revoke access to authorisation

`DELETE /authorisations/{id}`

A user's accounts are connected to Akahu via an authorisation with their financial institution. Multiple accounts can be connected using a single authorisation.

This endpoint will revoke your application's access to one of the user's consented authorisations. After calling this endpoint, your application will no longer have access to the accounts connected via that authorisation (including their associated data and transactions).

You can find an authorisation for an account by looking at the `_authorisation` field on each account.

> ℹ️
>
> Users can also update their authorisations via the [📚 authorisation flow](/docs/authorizing-with-oauth2). The authorisation flow is the only way that users can add or remove access for individual accounts rather than a whole authorisation.

For more details see:
  - [📚 Accessing account data guide](/docs/accessing-account-data)
  - [📖 Account model](/docs/the-account-model)

## Headers

- `X-Akahu-Id` string, required

## Response `200`

Successful response.

- object
  - `success` boolean

## Other responses

- `400` — Your request was malformed or otherwise unacceptable. More details are provided under the `message` key in the response.
- `401` — You are not authorised to access this content.
- `403` — You are not allowed to access this content.
- `404` — The item you are trying to access doesn't exist.
- `500` — An internal error has prevented us from processing the request. More detail may be supplied in the `message` key.

---

[API](https://skmtc.dev/akahu/apis/akahu-enduring-api.md) · [All operations](https://skmtc.dev/akahu/apis/akahu-enduring-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/akahu/akahu-enduring-api/revisions/b2de9915920d/schema)