# Overview

OpenVasp specification v.3.2.1

Originator/Beneficiary entry points

Metadata:
  - types: ["Vasp"]
  - status: alpha

## Servers

Production
```
https://trp.travel-rule.com
```

Dev area
```
https://trp-stg.travel-rule.com
```

## Security

### BearerAuth

Type: http
Scheme: bearer
Bearer Format: JWT

## Download OpenAPI description

[Overview](https://docs.travel-rule.com/_bundle/api/vasp.yaml)

## Auth

### Generate JWT access token

 - [POST /auth/token](https://docs.travel-rule.com/api/vasp/auth/paths/~1auth~1token/post.md): Generates a signed, short-lived JWT access token using your API Key. This token is required to authenticate all subsequent TRP API requests. The endpoint ensures secure client identification and protects access to sensitive Travel Rule operations.

## Identity

### VASP public info

 - [GET /identity](https://docs.travel-rule.com/api/vasp/identity/identity.md): Retrieves verified information about a VASP based on its Travel Address or system identifier. This endpoint is used by VASPs to validate the counterparty before executing a Travel Rule transfer.

## Travel Address

### Generate beneficiary travel address

 - [POST /travel-address/generate](https://docs.travel-rule.com/api/vasp/travel-address/paths/~1travel-address~1generate/post.md): Creates a unique, encrypted Travel Address for a beneficiary using firstName, lastName, walletAddress and optional externalId. The generated Travel Address is used by the originator VASP to initiate a compliant Travel Rule transfer.

### Decode travel address

 - [POST /travel-address/decode](https://docs.travel-rule.com/api/vasp/travel-address/decodetraveladdress.md): Decodes a previously generated Travel Address and extracts beneficiary metadata (firstName, lastName, walletAddress, externalId). This endpoint allows the receiving VASP to retrieve the identity information included in the Travel Address before processing a transfer.

## Transfer

### Initiate

 - [POST /transfers/initiate](https://docs.travel-rule.com/api/vasp/transfer/initiate.md): Initiates a Travel Rule transfer by submitting the full IVMS101 originator and beneficiary profiles along with the transaction details. This endpoint returns a TRP transferId and triggers status callbacks to the originator VASP. Required to begin compliant cross-VASPs transfers.