Import pre-verified KYB (Know Your Business) data from a partner platform

⚠️

NOT AVAILABLE YET

This endpoint is not available yet. Please contact the Kulipa partnership team to request access.

Initiates a new KYB process from an existing business using pre-verified identity data from a trusted partner platform.
This endpoint enables Shared KYB functionality, allowing businesses who have already been verified
by a partner to onboard instantly without re-submitting documents.

If required, individuals associated with the business will need to be imported separately using the /kybs/{id}/individuals endpoint.

Partnership Required: This endpoint is only available to approved partner platforms.

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

Pre-verified KYB information from partner platform

string
required

Name of the business

string

Registration number of the business

date

Registration date of the business in YYYY-MM-DD format

string

Tax identification number of the business

string
enum

Status of the business

Allowed:
address
object
required
documents
array of objects

List of documents

documents
affiliatedCompanies
array of objects

List of companies affiliated with the business

affiliatedCompanies
Responses

400

The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

401

Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.

403

The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.

429

The user has sent too many requests in a given amount of time ("rate limiting").

500

The server has encountered a situation it does not know how to handle.

502

This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.

503

The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.

504

This error response is given when the server is acting as a gateway and cannot get a response in time.

Language
Credentials
Header
LoadingLoading…
Response
Choose an example:
application/json