Skip to main content

VASP Server API Specifications

Authentication

  • Before completing authentication, you should complete
  • GTR server authenticates incoming requests by verifying the bearer token in the Authorization header. To generate the bearer token, follow the below steps.
  • Use generated AK, signed SK and VaspCode with login API and obtain the issuance jwt token from the response.

For example:

  • Access_key: ABCD1234
  • Secret_Key(must be signed with SHA512): a1bacae12ac9614a2d04e794a5f1e2b705cb48573c6c9b29fee46378e8933acb3c6ddcad3357a80286a3e1593834867ca299efbe6cec5f2f9322d47a39e17712
  • VaspCode: rveJ2DyP9mOCu9V9ntYj4.

Authentication token:

eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiIsInppcCI6IkRFRiJ9.eNp0jTsPgjAUhf9LZwZpeV03CkI0JAJFHmOFDpoIBFqiMf53K3FwcTv35H7feSLetoPqJZNcqhlt0QYZaFZnnYDmqW-XjePiyALHzYCywirqKsliyuJTENKchUUWQFFWHgWoosaPmzBKMKvT3UmLvvJ9p3Wm45m6aifBpdDF5zaJSzCxiWeghc9jMHRCf06LOODwkcLtGCgooZfN1dKouI8rRlwMGjOQmsW0uv8RFy5_h15vAAAA__8.xh_AieoRWjVnSXBoktcUeAzABj1vK6BoftWKgYm-3Iw

All API requests sent to the GTR server must contain the following headers:

Header NameRequiredDescription
AuthorizationYesBearer Token generated in the Authentication section
Copyright (C) 2024 Global Travel Rule. All Rights Reserved
General
Developer