Present PII data to counterparties

Used to present PII data to counterparties in a transfer.
This endpoint is used for sharing PII between entities and can
optionally skip validation with skipValidation=true parameter.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
^did:([a-z0-9]+):((?:(?:[a-zA-Z0-9._-]|(?:%[0-9a-fA-F]{2}))*:)*(?:[a-zA-Z0-9._-]|(?:%[0-9a-fA-F]{2}))+)((;[a-zA-Z0-9_.:%-]+=[a-zA-Z0-9_.:%-]*)*)(/[^#?]*)?([?][^#]*)?(#.*)?$

The DID of the entity

uuid
required

The transfer ID

string
required

The policy ID

Query Params
boolean
Defaults to false

Whether to skip validation

Body Params
ivms101
object
required

IVMS101 compliant data structure for originator and beneficiary information.
This structure is compliant with the official standard IVMS 101.2023.

Geographic Address Structure - Use ONE of these patterns:

Pattern 1 (with addressLine):

  • addressType (required)
  • addressLine (array of strings, required)
  • townName (required)
  • country (required - ISO-3166 Alpha-2 format, e.g., US, GB, XX)
  • postCode (optional)

Pattern 2 (with streetName/buildingNumber):

  • addressType (required)
  • streetName (required if not using addressLine)
  • buildingNumber (required if not using addressLine)
  • townName (required)
  • country (required - ISO-3166 Alpha-2 format, e.g., US, GB, XX)
  • postCode (optional)
Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json