post https://sg-api.upbit.com/v1/travel_rule/deposit/uuid
Retrieves travel rule verification using the deposit UUID.
Check the proper endpoint based on your region.
The examples on this page use Singapore fiat code (SGD). Please note that this feature is only supported in Singapore.
- Singapore (sg): https://sg-api.upbit.com
- Singapore (sg): https://sg-api.upbit.com
Deposit will be reflected after account owner verification is completed.
If the account owner verification is not completed, please check whether the name and date of birth information entered during Upbit's identity verification process matches the information entered at the counterparty exchange.Once verification is completed, the deposit will be reflected immediately. However, if the deposit itself is still processing due to blockchain network delays even after verification, the deposit will be reflected after the deposit is completed.
Form-based POST requests are no longer supported from March 1, 2022.
Due to the end of Form support, POST requests sent using URL-encoded Form data are no longer guaranteed to work properly. Please ensure that the request body is sent strictly in JSON format.
| Version | Date | Changes |
|---|---|---|
| v1.1.2 | 2024-04-24 |
Addition of Travel Rule API,(Upbit Singapore only) |
Rate Limit
Up to 30 calls per second allowed. Measured per account and shared among requests within the [Exchange Basic Group]. However, for the same deposit, up to 1 call per 10 minutes is allowed.
API Key Permission
API key with authentication is required, with [Deposit] permission enabled.
If you encounter a permission error (out_of_scope), please check the permission settings in the API Key Management page.
If you encounter a permission error (out_of_scope), please check the permission settings in the API Key Management page.