Skip to main content
GET
Get an Information Request by ID

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.

Path Parameters

informationRequestId
string
required

ID of the Information Request to fetch — the id returned by GET /v1/information-requests.

Response

The Information Request details for the authenticated account

Detailed Information Request payload for the authenticated Meridian account

id
string
required

Unique identifier of the Information Request

Example:

"ir_01HZX1A2B3C4D5E6F7G8H9J0K"

status
enum<string>
required

Current status of the Information Request

Available options:
DRAFT,
PROCESSING_SUBMISSION,
PENDING_REVIEW,
COMPLETED,
CANCELED
Example:

"DRAFT"

subjectType
enum<string>
required

Type of entity the Information Request is associated with

Available options:
ENROLLMENT
Example:

"ENROLLMENT"

subjectId
string
required

Identifier of the entity the Information Request is associated with

Example:

"enrollment_123"

requirements
Information Request Requirement · object[]
required

Requirement contracts and submitted entries for this Information Request

validationStatus
enum<string>
required

Validation status of the Information Request data. VALID means every rule that can be checked from this Information Request alone passes — field schemas, cross-entry rules and required documents. It is not a promise that submission will succeed: checks against data outside this Information Request, such as whether a business name is already registered, only run on POST /submit and are reported there.

Available options:
MISSING,
VALID,
INVALID
Example:

"MISSING"

createdAt
string<date-time>
required

Timestamp when the Information Request was created

Example:

"2026-04-01T12:00:00Z"

updatedAt
string<date-time>
required

Timestamp when the Information Request was last updated

Example:

"2026-04-01T12:05:00Z"

decision
enum<string> | null

Current manual review decision status for the Information Request, if it has been reviewed

Available options:
PENDING,
APPROVED,
REJECTED,
null
Example:

"PENDING"

title
string | null

Display title for the Information Request

Example:

"Business Verification"