Re-activate a previously deactivated business customer.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Re-activate a business customer that was previously deactivated (soft-deleted). This flips is_active back to true so the business reappears in the default GET /kyb/businesses listing. It does not change kyb_status, verification_mode, or any verification state — only the active flag. The endpoint is idempotent: re-activating an already-active business is a no-op and still returns 200. Returns the updated business customer record.
Authentication & access
- Requires a client API token:
Authorization: Bearer <token>. - The caller must hold the
kyb.businesses.writepermission and have the OWNER role. Any other role is rejected with403.
Path parameters
| Parameter | In | Description |
|---|---|---|
business_id | path | The ID of the business customer to re-activate. Must belong to your client. |
What activation does
- If the business is currently inactive (
is_active = false), it is set back tois_active = trueand the change is recorded in the audit log. - If the business is already active, nothing changes and the current record is returned unchanged.
- Verification status (
kyb_status,external_verification_status, and the verification record) is left untouched.
Response
200 — Returns the BusinessCustomerResponse object for the business, including id, company_name, registration_number, country, kyb_status, verification_mode, verification_source, is_active, and created_at. After a successful activation is_active is true.
Error responses
| Status | When |
|---|---|
404 | No business customer with this business_id exists under your client |
Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.