Skip to main content

1. Endpoint

2. Authentication

Include the API key in the x-api-key header:
x-api-key

3. Request Parameters

The request parameters should be sent as URL query parameters. Below are the parameter descriptions:
string
Unique ID of a specific submission (single submission query)
string
Retrieve a list of submissions matching the user ID
string
Retrieve a list of submissions matching the email address
string
default:"50"
Number of results to return (default: 50)
string
ID for fetching the next page of results
string
Date for fetching the next page of results
string
Start date for filtering results (format: YYYY-MM-DD)
string
End date for filtering results (format: YYYY-MM-DD)
string
Use the request_type parameter to selectively retrieve specific types of data. Choose one of the following options:
  • kyc: Returns KYC-related data and submission_id.
  • aml: Returns AML-related data and submission_id.
  • data: Returns personal information data and submission_id.
  • others: Returns all data items excluding KYC, AML, and personal information.

4. Request Examples by Query Type

Retrieve detailed information for a specific submission.

Request Example

Response Example

For detailed response field definitions, refer to the Response Fields page.

5. Secure Data Transfer

Encrypt all request parameters, including submission_id, as a single JSON object, URL-encode the result, and pass it as the data query parameter. For details, see API Request Data Encryption (AES-256-ECB).
For POST and PATCH, send the ciphertext in the request body as a raw base64 string. For GET, URL-encode the ciphertext and pass it as the data query parameter.

Encrypted Request Example

When using Secure Data Transfer, the response will be encrypted data, and you should decrypt it to read the data.

Encrypting the Entire Request

For projects with Secure Data Transfer enabled, bundle all the request parameters you use into a single JSON object and encrypt it. The example below includes every parameter; include only the ones you need in an actual request:
encrypt-request-params.json
Encrypt the object above using AES-256-ECB, URL-encode the result, and pass it as the data query parameter.
Plaintext parameters placed outside data are ignored. Put every query condition inside the encrypted object.

Encrypted Response

The response includes an isEncrypted flag and encrypted data:
result.json

6. Response Field Definitions

For detailed definitions of all fields included in GET/Submission API responses, refer to the following page:

Response Field Definitions

Detailed definitions and descriptions of GET/Submission API response fields

7. Error Codes