Proxy a DELETE request to the Verification API

Forwards an authenticated DELETE request to the Flutterwave Verification API (https://api.verification.flutterwave.com) on behalf of the caller, so clients never need the internal Verification API secret key.

The downstreamPath wildcard segment is checked against an explicit allow-list before anything is sent upstream — only paths starting with v1/verifications or v1/banks are permitted. Any other path is rejected with a 400 and never reaches the Verification API. Any query string parameters supplied on this request are forwarded verbatim to the downstream path; DELETE requests never forward a request body.

A best-effort, PII-free audit record (caller identity, downstream path, outcome, duration) is persisted for every attempted call, including rejected and failed ones. Audit persistence failures never block the response.

Status code and body are passed through from the Verification API almost verbatim: the HTTP status code returned by this endpoint is exactly the status code the Verification API responded with (for example 200 or 204 for a successful delete, or the Verification API's own 4xx/5xx if it rejects the request), and the JSON body's data field is exactly the Verification API's response body — its shape depends entirely on the downstream path and cannot be enumerated here. Note that because no exception is thrown for a passed-through downstream error, the envelope's status field will still read "success" in that case; only requests rejected by our own allow-list check, authentication failures, or genuine network/timeout errors talking to the Verification API produce our own status: "error" envelope.

Request

Authorization

JWT Bearer

Add the parameter

Authorization

to Headers

Example:

Authorization: ********************

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Query Params

Responses

🟢200

application/json

The Verification API accepted the delete and responded with a 2xx status. The exact status code and data shape are whatever the Verification API returned for this downstream path — shown here is a representative example only.

Bodyapplication/json

🟠400

🟠401

🔴500