---
title: "Reverse clearing of authorisation hold"
method: POST
path: "/v3/authorization-holds/clearings/{clearingTransactionId}/reverse"
tags: ["Authorization Holds"]
---

# Reverse clearing of authorisation hold

`POST /v3/authorization-holds/clearings/{clearingTransactionId}/reverse`

Reverses (cancels) a previously created authorization hold clearing

## Path parameters

- `clearingTransactionId` string, biginteger, required

## Query parameters

- `auditUser` string, required

## Response `200`

Authorization hold clearing reversed successfully

- ReverseAuthorizationHoldClearingResponse
  - `clearingReversalTransactionId` string, biginteger — Transaction Id of generated authorization hold clearing reversal

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Authorization hold not found
- `500` — Internal server error

---

[API](https://skmtc.net/enfuce/apis/transfer-api.md) · [All operations](https://skmtc.net/enfuce/apis/transfer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/enfuce/transfer-api/revisions/dc4a41118f80/schema)