Create a KYC Document Page
Upload a file to the KYC Document object
<Warning icon="fa-regular fa-triangle-exclamation">
**Caution – Legacy endpoints being superseded by the hosted KYC/KYB solution**
Mangopay's [hosted KYC/KYB solution](/guides/users/verification/hosted) is becoming mandatory for all platforms (relying on the [IDV Session](/api-reference/idv-sessions/idv-session-object) object). The legacy KYC Document endpoints remain available for the sole purposes of [sending additional documents](/guides/users/verification/hosted/integration#sending-additional-documents), but this use case will also be handled by the hosted solution in future.
</Warning>
The KYC Document Page is a file attached to the KYC Document for Mangopay's teams to review.
You can upload up to 5 files to each KYC Document, and each upload requires a call to this endpoint. Each file can contain as many real-life pages as required.
To be able to upload a file using this endpoint:
- The corresponding KYC Document `Status` must be `CREATED`
- The `File` must be Base64 encoded and abide by the [format and size constraints](/guides/users/verification/documents/submission#file-constraints)
[Read more about the KYC Document object →](/api-reference/kyc-documents/kyc-document-object)
Authentication
AuthorizationBearer
Bearer authentication of the form `Bearer <token>`, where token is your auth token.
If your platform is using a [proxy](/guides/sca/proxy-management) to take SCA-triggering action on behalf of users, you also need to integrate [mTLS authentication](/guides/sca/platform) and use the `api-mtls` base URL.
Path parameters
ClientId
Platform's API account identifier, associated with the API key.
UserId
The unique identifier of the user.
KycDocumentId
The unique identifier of the KYC Document.
Request
This endpoint expects an object.
File
Format: Base64 encoded file
The encoded file of the logo to upload.
Response
Success
Errors
400
Bad Request Error