KintsugiKintsugi
API reference / Archive a customer

Archive a customer

DELETE/customers/{customer_id}

Delete a customer. It is removed from this API: afterwards it is absent from GET /customers and returns 404 from every read and write, exactly as a customer that never existed does. Creating a customer again with the same externalId and source restores this one instead of making a second, so its transactions and exemptions stay attached to it. Returns 404 if the customer does not exist, is already deleted, or belongs to an organization your credential cannot access.

Authorization

Api-KeystringRequired

Your secret API key. Include it with every request.

Headers

Api-Versiondate

Release date, as YYYY-MM-DD. Defaults to 2026-07-21.

Organization-Idstring

Target organization id (Organization-Id selector).

Connection-Idstring

Target connection id; resolves to its organization.

Entity-Idstring

Platform entity id; resolves to a connection's organization.

Entity-Sourcestring

Optional source to disambiguate an Entity-Id.

Path parameters

customer_idstringRequired

The unique identifier of the customer.

Response

204

Successful Response

400

The request was invalid.

401

Authentication failed or was missing.

403

The credential is not permitted for this request.

404

The requested resource was not found.

409

The request conflicts with existing state.

422

The request failed validation.

cURL
DELETE /customers/{customer_id}
-H "Api-Key: ***"
-H "Api-Version: 2026-07-21"
Example request
https://api.trykintsugi.com/customers/{customer_id}
Response
{
"code": "missing_target_selector",
"message": "Provide one of Organization-Id, Connection-Id, or Entity-Id.",
"requestId": "req_8f3k2mNpQr7Ls",
"errors": []
}
Archive a customer (2026-07-21) | Kintsugi API Reference