Skip to main content
All Business entity management happens through six public endpoints under /v3/businesses/. This page gives you the conceptual walkthrough — see the API reference for full request / response schemas.

List businesses

GET /v3/businesses/ Paginated list of businesses for your application with filters on status, search, country, and date range.

Get a business

GET /v3/businesses/{vendor_data}/ Retrieve a single business by vendor_data.

Create a business

POST /v3/businesses/create/ Pre-create a Business before any Business Verification (KYB) session runs:
Returns a conflict error if a business with that vendor_data already exists. Use PATCH to update an existing business.

Update a business

PATCH /v3/businesses/{vendor_data}/ Update mutable profile fields. Fields derived from registry lookups (legal_name, registration_number, country_code) are read-only after verification but can be overridden — overrides are flagged in the audit log. Mutable fields: display_name, metadata, tags. Read-only after verification: all registry-derived fields, aggregate counters, features map.
Emits business.data.updated.

Change status

PATCH /v3/businesses/{vendor_data}/update-status/ Move a business between ACTIVE, FLAGGED, and BLOCKED.
Emits business.status.updated.

Delete businesses (batch)

POST /v3/businesses/delete/ Delete one or more businesses. History is retained for the configured data retention period, then hard-deleted.
Idempotent — deleting an already-deleted business is a no-op.

Permission model

All /v3/businesses/* endpoints are scoped by the businesses permission resource: See Roles & permissions.

Webhooks fired by these operations

Next steps

Data model

Full field reference.

List API

GET /v3/businesses/ schema.

Create API

POST /v3/businesses/create/ schema.