/v1/me/documentsIdentity and company documents the caller has uploaded.
Api-Key headermember token
Signed-in member. Send the token from POST /v1/sessions. Always send Api-Key as well.
Responses
| Status | Meaning | Body |
|---|---|---|
200 | OK | — |
Home / Documentation / API / Identity documents
API reference · 18.08.2026
Upload, list and remove the signed-in bidder's identity and company documents.
/v1/me/documentsApi-Key headermember token
Signed-in member. Send the token from POST /v1/sessions. Always send Api-Key as well.
| Status | Meaning | Body |
|---|---|---|
200 | OK | — |
/v1/me/documentsApi-Key headermember token
Auction houses often require proof of identity, or company registration for business buyers, before a bidder registration is approved. This is where that document goes.
The document is always filed against the signed-in member — any address in the body isignored, so a member can only ever upload for themselves.
List what has been uploaded with GET /v1/me/documents and remove one withDELETE /v1/me/documents/{id}. Uploading does not approve anything; approval is aback-office decision and is reported through the auction registration status.
application/json · AddMemberFileRequest| Property | Type | Required |
|---|---|---|
Email | string | no |
MemberUploadFiles | array of MemberUploadFiles | no |
MemberUploadFiles
| Property | Type | Required |
|---|---|---|
Name | string | no |
ContentType | string | no |
Data | string (byte) | no |
| Status | Meaning | Body |
|---|---|---|
200 | OK | HttpResponseMessage |
/v1/me/documents/{id}Api-Key headermember token
Signed-in member. Send the token from POST /v1/sessions. Always send Api-Key as well.
| Name | In | Type | Required |
|---|---|---|---|
id | path | string (uuid) | yes |
| Status | Meaning | Body |
|---|---|---|
200 | OK | — |