Customers
Identify who holds a destination wallet
Records who holds a wallet the customer sent crypto to: the customer's own self-hosted wallet (with the ownership attestation), or the customer's account at an exchange. OZAV asks for it with a requirement.due webhook (reason: destination_unidentified) and a documents_due item with purpose: travel_rule; answering closes that item. You can also send it before being asked. The identification applies to every send of the customer to the same wallet. It does not allow or block any send.
post/customers/{customer_id}/destination-identifications
Request
- Base URLhttps://developers.ozav.io/v2
- Auth
- API key in header X-API-Key
- or HTTP bearer
Path parameters
customer_idstring required
Request body
Example request
{
"chain": "tron",
"address": "TGssfnTouNs2H9AYPRkeZo9zuRxTPB5KCq"
}Response
The identification, as recorded.
Changes
No recorded changes to this operation across all 1 revision of this API.