Skip to main content
POST

Authorizations

​
Authorization
string
header
required

Bearer token authentication, for client-server calls.

Send the access token issued by POST /v1/auth/token as Authorization: Bearer {token}. The token carries its own program and user context, so the X-Meridian-* headers are not required. See Authentication.

Headers

​
X-Meridian-Api-Key
string

Server-to-server (HMAC) requests only. Partner API key issued by Meridian during provisioning.

​
X-Meridian-Timestamp
string

Server-to-server (HMAC) requests only. Current time in milliseconds since the Unix epoch. Must be within 60 seconds of the request.

​
X-Meridian-Program-Id
string

Server-to-server (HMAC) requests only. Identifies the program context for the request.

​
X-Meridian-User-Id
string

Server-to-server (HMAC) requests only. Identifies the Meridian user targeted by the request. Required for MULTI_USER integrations; omit for SINGLE_USER.

​
Content-Digest
string

SHA-256 digest of the multipart body, formatted per RFC 9530 as sha-256=:<base64>:. Required when authenticating with a partner API key; the HMAC signature is computed over the Content-Digest value instead of the raw multipart bytes. Ignored for JWT auth.

Path Parameters

​
informationRequestId
string
required

ID of the Information Request the uploaded document is attached to.

Body

multipart/form-data

Multipart form data containing requirementKey, documentKey, optional entryId, and file

Multipart form data for uploading a file to an Information Request

​
file
file
required

File to upload

​
requirementKey
string | null

Requirement key to attach the document to

Example:

"associatedPersons"

​
documentKey
string | null

Document slot key to attach the file to

Example:

"identityDocumentFront"

​
entryId
string | null

Virtual requirement entry id, such as associatedPersons:0

Example:

"associatedPersons:0"

Response

Document upload accepted