Update Preflight Check Result

Version: 3.0.0

Method

PUT

Url

https://platform.globaltravelrule.com/api/verify/v2/manual/preflight

Authentication

No authentication

Path Parameters

No path parameters

Query Parameters

No query parameters

Request Body (Optional)

Schema

	Property	Type	Required	Description
	requestId	String	Yes	requestId is the unique id for all transaction, the same travelrule-request invoke process flow should be using same requestId, the recommend format is: "[YOUR_VASP_NAME]-[UUIDv4]"
	result	Object	Yes	PreflightCheckStatusEnum
Property Type Description preflightCheckMessage String preflight check message is to let you know whether the counter-party vasp will accept your request or not *This is only suitable in before-on-chain scenario. *And also not mandatory for check the result of pre-flight preflightCheckStatus String PreflightCheckStatusEnum requestId String

Example

{
  "result": "PreflightCheckStatusEnum",
  "requestId": "testexchange-189e9948-64c7-4a6c-bb4f-859c173321c5"
}

Responses

Status 200

OK

JSON Content

Schema

	Property	Type	Description
	verifyMessage	String
	verifyStatus	Integer

Example

{
  "verifyStatus": 0,
  "verifyMessage": "string"
}

Status HTTP Status: 200, VerifyStatus: 100000

Success

JSON Content

Schema

	Property	Type	Description
	data	Object
Property Type Description No properties
	verifyMessage	String
	verifyStatus	Integer

Example

{
  "data": {},
  "verifyStatus": 0,
  "verifyMessage": "string"
}

Request Example 1: Manual Update - Preflight Check Accept

{
  "requestId": "[requestId]",
  "result": {
    "preflightCheckStatus": "ACCEPTED",
    "preflightCheckMessage": "accepted"
  }
}

Request Example 2: Manual Update - Preflight Check Reject

{
  "requestId": "[requestId]",
  "result": {
    "preflightCheckStatus": "REJECTED",
    "preflightCheckMessage": "rejected"
  }
}

Response Example: Success

HTTP Status: 200, VerifyStatus: 100000

{
  "verifyStatus": 100000,
  "verifyMessage": "Verify Success"
}