> ## Documentation Index > Fetch the complete documentation index at: https://docs.mnai.com/llms.txt > Use this file to discover all available pages before exploring further. # Create or update Information Request requirement entry data > Writes structured data for one or more requirement entries. ## OpenAPI ````yaml /products/meridian-accounts/api-reference/meridian-accounts.json post /v1/information-requests/{informationRequestId}/data openapi: 3.1.1 info: title: Meridian API version: '1.0' description: API documentation for Meridian services contact: name: Meridian url: https://mnai.com email: support@mnai.com license: name: Proprietary url: https://mnai.com servers: - url: https://sandbox-api.va.meridianpay.com description: Sandbox - url: https://api.va.mnai.com description: Production security: [] paths: /v1/information-requests/{informationRequestId}/data: post: tags: - Information Requests summary: Create or update Information Request requirement entry data description: Writes structured data for one or more requirement entries. operationId: writeInformationRequestData parameters: - name: Authorization in: header description: >- Bearer authentication header of the form `Bearer {token}`. Required for client-server (JWT) authentication. See [Authentication](/products/meridian-accounts/guides/authentication-overview). schema: type: string - name: X-Meridian-Program-Id in: header description: >- Identifies the program context for the request. Required for server-to-server (HMAC) authentication. See [Authentication](/products/meridian-accounts/guides/authentication-overview). schema: type: string - name: X-Meridian-User-Id in: header description: >- 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](/products/meridian-accounts/guides/authentication-overview). schema: type: string - name: X-Meridian-Api-Key in: header description: >- Partner API key issued by Meridian during provisioning. Required for server-to-server (HMAC) authentication. See [Authentication](/products/meridian-accounts/guides/authentication-overview). schema: type: string - name: X-Meridian-Timestamp in: header description: >- 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](/products/meridian-accounts/guides/authentication-overview). schema: type: string - name: X-Meridian-Signature in: header description: >- HMAC SHA-256 signature of the canonical request string, computed per request. Required for server-to-server (HMAC) authentication. See [Authentication](/products/meridian-accounts/guides/authentication-overview) for how to construct it. schema: type: string - name: informationRequestId in: path required: true schema: type: string requestBody: description: Requirement entry data write payload content: application/json: schema: $ref: '#/components/schemas/Write Information Request Data Request' examples: usd_account_to_stablecoin_autosweep: $ref: '#/components/examples/WriteDataUsdAccountToStablecoinAutosweep' usd_account_to_php_bank_account: $ref: '#/components/examples/WriteDataUsdAccountToPhpBankAccount' required: true responses: '200': description: The updated Information Request details content: application/json: schema: $ref: '#/components/schemas/Information Request Detail Response' '400': description: Invalid or malformed request body content: application/json: schema: $ref: '#/components/schemas/MeridianError' '401': description: Missing or invalid authentication content: application/json: schema: $ref: '#/components/schemas/MeridianError' '403': description: >- The authenticated caller is not permitted: JWT scope missing, or the partner API key lacks entitlement, user ownership, or user-type match content: application/json: schema: $ref: '#/components/schemas/MeridianError' '404': description: The requested Information Request was not found content: application/json: schema: $ref: '#/components/schemas/MeridianError' '422': description: The payload failed requirement validation content: application/json: schema: $ref: '#/components/schemas/MeridianError' security: - meridian-account-jwt: [] - partner-api-key: [] components: schemas: Write Information Request Data Request: type: object title: Write Information Request Data Request description: Structured data write request for requirement entries required: - entries properties: entries: type: array items: $ref: '#/components/schemas/MeridianWriteInformationRequestEntryData' Information Request Detail Response: type: object title: Information Request Detail Response description: >- Detailed Information Request payload for the authenticated Meridian account required: - id - status - subjectType - subjectId - requirements - validationStatus - createdAt - updatedAt properties: id: type: string description: Unique identifier of the Information Request example: ir_01HZX1A2B3C4D5E6F7G8H9J0K status: type: string description: Current status of the Information Request example: DRAFT enum: - DRAFT - PROCESSING_SUBMISSION - PENDING_REVIEW - COMPLETED - CANCELED subjectType: type: string description: Type of entity the Information Request is associated with example: ENROLLMENT enum: - ENROLLMENT subjectId: type: string description: Identifier of the entity the Information Request is associated with example: enrollment_123 requirements: type: array description: >- Requirement contracts and submitted entries for this Information Request items: $ref: '#/components/schemas/Information Request Requirement' validationStatus: type: string description: Validation status of the Information Request data example: MISSING enum: - MISSING - VALID - INVALID decision: type: - string - 'null' description: >- Current manual review decision status for the Information Request, if it has been reviewed example: PENDING enum: - PENDING - APPROVED - REJECTED title: type: - string - 'null' description: Display title for the Information Request example: Business Verification createdAt: type: string description: Timestamp when the Information Request was created example: '2026-04-01T12:00:00Z' format: date-time updatedAt: type: string description: Timestamp when the Information Request was last updated example: '2026-04-01T12:05:00Z' format: date-time MeridianError: type: object title: com.meridianpay.core.common.api.MeridianError description: >- Represents an error response from the Meridian API, including validation errors and an optional error code. required: - message properties: validationErrors: type: array description: >- An array of validation errors that occurred during the processing of the request. This field is optional and may be empty if there are no validation errors. items: $ref: '#/components/schemas/ValidationError' errorCode: type: - string - 'null' description: >- An optional error code that provides additional information about the error. This field is optional and may be null. message: type: string description: >- A human-readable message describing the error. This field is required and should provide a clear explanation of the error that occurred. MeridianWriteInformationRequestEntryData: type: object title: >- com.meridianpay.remittances.api.dto.meridian.MeridianWriteInformationRequestEntryData description: Structured data for one requirement entry required: - requirementKey - data properties: requirementKey: type: string entryId: type: - string - 'null' clientReferenceId: type: - string - 'null' data: type: object Information Request Requirement: type: object title: Information Request Requirement description: Requirement contract and submitted entries required: - requirementKey - cardinality - documents - validationStatus - entries properties: requirementKey: type: string description: Stable requirement key example: business_information title: type: - string - 'null' description: Display title for the requirement description: type: - string - 'null' description: Display description for the requirement cardinality: $ref: '#/components/schemas/Information Request Requirement Cardinality' dataSchema: type: - object - 'null' description: JSON Schema describing the expected structured data shape documents: type: array description: Document slots that may be attached to each entry items: $ref: '#/components/schemas/MeridianInformationRequestDocumentDefinition' validationStatus: type: string description: Validation status of this requirement enum: - MISSING - VALID - INVALID entries: type: array description: Submitted entries for this requirement items: $ref: '#/components/schemas/MeridianInformationRequestEntry' ValidationError: type: object title: com.meridianpay.core.common.api.ValidationError description: >- Represents a validation error that occurred during the processing of a request to the Meridian API. One of the following types of validation errors may be present: InvalidFormat, InvalidValue, MissingValue, UnprocessableValue, UnexpectedVerificationError, MissingRequestBody, MissingPathParameter, MissingQueryParameter, or NotFound. Each validation error includes a reference to the field that caused the error and a message describing the error. oneOf: - $ref: '#/components/schemas/InvalidFormat' - $ref: '#/components/schemas/InvalidValue' - $ref: '#/components/schemas/MissingPathParameter' - $ref: '#/components/schemas/MissingQueryParameter' - $ref: '#/components/schemas/MissingRequestBody' - $ref: '#/components/schemas/MissingValue' - $ref: '#/components/schemas/NotFound' - $ref: '#/components/schemas/UnexpectedVerificationError' - $ref: '#/components/schemas/UnprocessableValue' discriminator: propertyName: type mapping: com.meridianpay.core.common.api.ValidationError.InvalidFormat: $ref: '#/components/schemas/InvalidFormat' com.meridianpay.core.common.api.ValidationError.InvalidValue: $ref: '#/components/schemas/InvalidValue' com.meridianpay.core.common.api.ValidationError.MissingPathParameter: $ref: '#/components/schemas/MissingPathParameter' com.meridianpay.core.common.api.ValidationError.MissingQueryParameter: $ref: '#/components/schemas/MissingQueryParameter' com.meridianpay.core.common.api.ValidationError.MissingRequestBody: $ref: '#/components/schemas/MissingRequestBody' com.meridianpay.core.common.api.ValidationError.MissingValue: $ref: '#/components/schemas/MissingValue' com.meridianpay.core.common.api.ValidationError.NotFound: $ref: '#/components/schemas/NotFound' com.meridianpay.core.common.api.ValidationError.UnexpectedVerificationError: $ref: '#/components/schemas/UnexpectedVerificationError' com.meridianpay.core.common.api.ValidationError.UnprocessableValue: $ref: '#/components/schemas/UnprocessableValue' Information Request Requirement Cardinality: type: object title: Information Request Requirement Cardinality description: Requirement cardinality required: - mode - min properties: mode: type: string description: >- Cardinality mode for the requirement. SINGLE means exactly one entry is expected; MULTIPLE means the requirement may accept more than one entry. example: SINGLE min: type: integer description: Minimum number of entries required for this requirement example: 1 max: type: - integer - 'null' description: >- Maximum number of entries allowed for this requirement. Null means there is no fixed upper limit. example: 1 MeridianInformationRequestDocumentDefinition: type: object title: >- com.meridianpay.remittances.api.dto.meridian.MeridianInformationRequestDocumentDefinition description: Requirement document slot required: - documentKey - minFiles - maxFiles - supportedMimeTypes - maxFileSizeBytes properties: documentKey: type: string description: Stable document key example: identityDocumentFront minFiles: type: integer maxFiles: type: integer supportedMimeTypes: type: array items: type: string maxFileSizeBytes: type: integer MeridianInformationRequestEntry: type: object title: >- com.meridianpay.remittances.api.dto.meridian.MeridianInformationRequestEntry description: Submitted requirement entry required: - entryId - validationStatus - documents properties: entryId: type: string clientReferenceId: type: - string - 'null' validationStatus: type: string enum: - MISSING - VALID - INVALID data: type: - object - 'null' documents: type: array items: $ref: '#/components/schemas/MeridianInformationRequestEntryDocument' InvalidFormat: type: object title: com.meridianpay.core.common.api.ValidationError.InvalidFormat description: The provided value exists, but its format is invalid for the field. required: - fieldRef properties: fieldRef: type: string description: The field or parameter that triggered the validation error. message: type: string description: A human-readable explanation of the validation failure. InvalidValue: type: object title: com.meridianpay.core.common.api.ValidationError.InvalidValue description: >- The provided value is syntactically valid, but not accepted for the field. required: - fieldRef properties: fieldRef: type: string description: The field or parameter that triggered the validation error. message: type: string description: A human-readable explanation of the validation failure. MissingPathParameter: type: object title: com.meridianpay.core.common.api.ValidationError.MissingPathParameter description: A required path parameter was not supplied. required: - fieldRef properties: fieldRef: type: string description: The field or parameter that triggered the validation error. message: type: string description: A human-readable explanation of the validation failure. MissingQueryParameter: type: object title: com.meridianpay.core.common.api.ValidationError.MissingQueryParameter description: A required query parameter was not supplied. required: - fieldRef properties: fieldRef: type: string description: The field or parameter that triggered the validation error. message: type: string description: A human-readable explanation of the validation failure. MissingRequestBody: type: object title: com.meridianpay.core.common.api.ValidationError.MissingRequestBody description: >- The request body is missing or does not contain the required non-null fields. properties: message: type: string description: A human-readable explanation of the validation failure. fieldRef: type: string MissingValue: type: object title: com.meridianpay.core.common.api.ValidationError.MissingValue description: A required value for the field was not provided. required: - fieldRef properties: fieldRef: type: string description: The field or parameter that triggered the validation error. message: type: string description: A human-readable explanation of the validation failure. NotFound: type: object title: com.meridianpay.core.common.api.ValidationError.NotFound description: The referenced principal object was not found. required: - fieldRef properties: fieldRef: type: string description: The field or parameter that triggered the validation error. message: type: string description: A human-readable explanation of the validation failure. UnexpectedVerificationError: type: object title: >- com.meridianpay.core.common.api.ValidationError.UnexpectedVerificationError description: A downstream verification step failed while checking the value. required: - fieldRef properties: fieldRef: type: string description: The field or parameter that triggered the validation error. message: type: string description: A human-readable explanation of the validation failure. UnprocessableValue: type: object title: com.meridianpay.core.common.api.ValidationError.UnprocessableValue description: The provided value cannot be processed into a valid result. required: - fieldRef properties: fieldRef: type: string description: The field or parameter that triggered the validation error. message: type: string description: A human-readable explanation of the validation failure. MeridianInformationRequestEntryDocument: type: object title: >- com.meridianpay.remittances.api.dto.meridian.MeridianInformationRequestEntryDocument description: Files attached to one requirement document slot required: - documentKey - files properties: documentKey: type: string files: type: array items: $ref: '#/components/schemas/Information Request Uploaded File' Information Request Uploaded File: type: object title: Information Request Uploaded File description: An uploaded file associated with an Information Request document required: - fileName - mimeType - sizeBytes - storageKey properties: fileName: type: string description: Original file name of the uploaded file example: business_license.pdf mimeType: type: string description: MIME type of the uploaded file example: application/pdf sizeBytes: type: integer description: File size in bytes example: 204800 storageKey: type: string description: Storage key used to retrieve the uploaded file example: >- uploads/ir_01HZX1A2B3C4D5E6F7G8H9J0K/businessLicense/business_license.pdf examples: WriteDataUsdAccountToStablecoinAutosweep: value: entries: - requirementKey: us_business_information entryId: us_business_information:0 data: legalName: Acme Industries LLC displayName: Acme Industries registrationNumber: C1234567 incorporationDate: '2020-03-15' industry: Software taxNumber: 98-7654321 businessType: LIMITED_LIABILITY_COMPANY websiteUrl: https://www.acme.example - requirementKey: us_registered_address entryId: us_registered_address:0 data: addressLine1: 123 Market St addressLine2: Suite 400 city: San Francisco stateProvince: CA postalCode: '94105' countryCode: US - requirementKey: associated_persons entryId: associated_persons:0 clientReferenceId: representative-1 data: roles: - BENEFICIAL_OWNER - CONTROL_PERSON - SIGNER title: CEO ownershipPercentage: 60 person: firstName: John lastName: Smith dateOfBirth: '1986-06-01' citizenship: US email: john.smith@acme.example phoneNumber: '+12813308004' taxNumber: 078-05-1120 physicalAddress: addressLine1: 100 Legends Way addressLine2: Apt 5 city: Boston stateProvince: MA postalCode: '02114' countryCode: US - requirementKey: associated_persons entryId: associated_persons:1 clientReferenceId: representative-2 data: roles: - DIRECTOR title: Director ownershipPercentage: 40 person: firstName: Jane lastName: Doe dateOfBirth: '1990-11-23' citizenship: US email: jane.doe@acme.example phoneNumber: '+14155550199' taxNumber: 087-65-4321 physicalAddress: addressLine1: 742 Evergreen Terrace city: San Francisco stateProvince: CA postalCode: '94110' countryCode: US - requirementKey: credit_wallet_address entryId: credit_wallet_address:0 data: creditWalletAddress: '0x52908400098527886E0F7030069857D2E4169EE7' WriteDataUsdAccountToPhpBankAccount: value: entries: - requirementKey: us_business_information entryId: us_business_information:0 data: legalName: Acme Remittances LLC displayName: Acme Remittances registrationNumber: RC-2026-0099 incorporationDate: '2021-03-15' industry: Money services / remittances taxNumber: 84-1234567 businessType: LIMITED_LIABILITY_COMPANY websiteUrl: https://www.acme.example - requirementKey: us_registered_address entryId: us_registered_address:0 data: addressLine1: 500 Market Street addressLine2: Suite 400 city: San Francisco stateProvince: CA postalCode: '94105' countryCode: US - requirementKey: associated_persons entryId: associated_persons:0 clientReferenceId: representative-1 data: roles: - SIGNER - BENEFICIAL_OWNER - CONTROL_PERSON title: CEO ownershipPercentage: 60 person: firstName: Maria lastName: Santos dateOfBirth: '1985-07-22' citizenship: US email: maria.santos@acme.example phoneNumber: '+14155550123' taxNumber: 123-45-6789 physicalAddress: addressLine1: 12 Hill Street city: San Francisco stateProvince: CA postalCode: '94110' countryCode: US - requirementKey: associated_persons entryId: associated_persons:1 clientReferenceId: representative-2 data: roles: - BENEFICIAL_OWNER title: CFO ownershipPercentage: 40 person: firstName: John lastName: Cruz dateOfBirth: '1979-11-02' citizenship: US email: john.cruz@acme.example phoneNumber: '+14155550199' taxNumber: 987-65-4321 physicalAddress: addressLine1: 88 Ocean Avenue city: San Francisco stateProvince: CA postalCode: '94112' countryCode: US - requirementKey: php_bank_account entryId: php_bank_account:0 data: accountHolderName: Acme Remittances LLC accountNumber: '001234567890' bankCode: '010040018' bankName: BPI - Bank of the Philippine Islands ````