POST
/
api
/
v1
/
customers
/
{customerId}
/
kyc
/
Submit KYC Information
curl --request POST \
  --url https://skala-sandbox.ripio.com/api/v1/customers/{customerId}/kyc/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "legalFirstName": "John",
  "lastName": "Doe",
  "dateOfBirth": "1980-01-01",
  "idNumber": "12345678"
}'
{
  "submissionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "createdAt": "2023-11-07T05:31:56Z",
  "providerUrl": "<string>"
}

Authorizations

​
Authorization
string
header
required

Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>.

Path Parameters

​
customerId
string<uuid>
required

Unique identifier for the customer.

Body

application/json · object

KYC data for the customer. Structure should align with fields from /kycRequirements/.

Encapsulates the KYC data for the customer. The structure of this object should comply with the kycRequiredFields information retrieved from the KYC Requirements endpoint. For example: {"legalFirstName": "John", "lastName": "Doe", ...}

Response

KYC submission received successfully. Includes providerUrl for document upload and liveness check.

​
submissionId
string<uuid>
required

Unique identifier for the submitted KYC data.

​
createdAt
string<date-time>
required

Date and time the KYC submission was created (UTC format).

​
providerUrl
string<url>
required

Points to a third-party KYC provider's widget to handle file uploads and liveness checks.