Save third party introduction diligence.

post

https://example.com/api/v3.0/{partnerCode}/users/{appUserId}/kyc/third-party-introduction-diligence

Description

This endpoint is only dedicated to the validation of identity diligence in case of third party introduction kyc.

Prerequisite

Prerequisites to call this endpoint are :

Partner has to be configured with expected diligence subtype THIRDPARTY_INTRODUCTION_IDENTITY as Identity diligence

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

partnerCode

string

required

Identifier of partner

appUserId

string

required

User identifier of partner

Format

Min 6 characters, max 30 characters

Accepted characters

0-9 a-z A-Z_-.!()

Example

ABCDEFGHI or
A1B2C3d4f5g678901234567890123

Body Params

Information needed to be provided

type

string | null

Type of the third party introduction.

Possible values:

Id	Code	Description
55	THIRDPARTY_INTRODUCTION_IDENTITY	Third party introduction Identity

Headers

CorrId

string

Defaults to 9f0ac3c7-f057-4c4a-9549-bf6440cafc58

Correlation Id

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

content-type

string

enum

Defaults to application/json-patch+json

Generated from available request content types

Allowed:

Responses

200

Description
The appUserId field is required.
The Type field is required.
Type does not exist in referential

Language

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

text/plain

application/json

text/json

400 Bad Request : DescriptionThe appUserId field is required.The Type field is required.Type does not exist in referential

404Not Found

405Operation not allowed

500Internal Server Error