Deactivate Business Customer

Soft-delete a business customer (sets is_active=False).

Does not touch kyb_status or the verification provider applicant. Deactivated
businesses are hidden from the default GET /businesses response
unless the caller passes include_inactive=true. Idempotent.

require_client_permissions enforces allowed_roles only for
client_user actors; the explicit role guard below also rejects
client_api callers whose credential role is not Owner.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Soft-deletes a business customer by setting is_active to false. This does not change the company's kyb_status or affect any verification already on file; it only hides the record from the default business listing. Returns the updated business customer.

The operation is idempotent — deactivating an already-inactive business is a no-op that returns the current record unchanged, and no new audit entry is written.

Deactivated businesses are excluded from GET /api/v1/kyb/businesses by default. To include them in that listing, pass include_inactive=true. A deactivated business can be brought back with POST /api/v1/kyb/businesses/{business_id}/activate.

Authentication & access

  • Requires a client API token: Authorization: Bearer <token>.
  • The caller must hold the kyb.businesses.write permission.
  • Only the OWNER role may deactivate a business. No other role is permitted, including for API-token callers.

Path parameters

NameInRequiredDescription
business_idpathyesThe ID of the business customer to deactivate. Must belong to your client.

Request body

FieldTypeConstraintsDescription
reasonstringrequired, 10–500 charactersOperational reason recorded in the audit log. The minimum length ensures the audit trail captures meaningful context.

Response

200 OK returns the BusinessCustomerResponse for the business with is_active set to false. All other fields (kyb_status, verification_mode, verification details, etc.) are unchanged.

Error responses

StatusWhen
404No business customer with this business_id exists under your client
422Request body failed validation (reason missing, shorter than 10 characters, or longer than 500)

Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.

Path Params
string
required
Body Params
string
required
length between 10 and 500

Operational reason recorded in audit log. Must be at least 10 characters so the audit trail captures meaningful context.

Responses

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json