Skip to main content
POST
/
v1
/
information-requests
/
{informationRequestId}
/
documents
curl --request POST \
  --url https://sandbox-api.va.meridianpay.com/v1/information-requests/{informationRequestId}/documents \
  --header 'Content-Type: multipart/form-data' \
  --form requirementKey=associated_persons \
  --form documentKey=passport \
  --form entryId=associated_persons:0 \
  --form file='@example-file'
{
  "message": "<string>",
  "validationErrors": [
    {
      "fieldRef": "<string>",
      "message": "<string>"
    }
  ],
  "errorCode": "<string>"
}

Headers

​
Authorization
string

Bearer authentication header of the form Bearer {token}. Required for client-server (JWT) authentication. See Authentication.

​
X-Meridian-Program-Id
string

Identifies the program context for the request. Required for server-to-server (HMAC) authentication. See Authentication.

​
X-Meridian-User-Id
string

Identifies the Meridian user targeted by the request. Required for server-to-server (HMAC) authentication with MULTI_USER integrations; omit for SINGLE_USER. See Authentication.

​
X-Meridian-Api-Key
string

Partner API key issued by Meridian during provisioning. Required for server-to-server (HMAC) authentication. See Authentication.

​
X-Meridian-Timestamp
string

Current time in milliseconds since the Unix epoch. Must be within 60 seconds of the request. Required for server-to-server (HMAC) authentication. See Authentication.

​
X-Meridian-Signature
string

HMAC SHA-256 signature of the canonical request string, computed per request. Required for server-to-server (HMAC) authentication. See Authentication for how to construct it.

​
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

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