Release Note: v3.3 (2024.05.02)
What's Changed
Enhancement to bridge/action/history
Endpoint
bridge/action/history
EndpointIn response to user feedback, the bridge/action/history
endpoint has undergone significant improvement. It has been divided into three distinct endpoints: bridge/action/history/user/{address}
, bridge/action/history/count/{count}
, and bridge/action/history/tx/{txHash}
, based on their respective call methods. This restructuring aims to simplify usage by providing clearer functionality for each endpoint, alleviating potential confusion caused by the previous combined endpoint.
Note to Users
Note that the bridge/action/history
endpoint has been deprecated in this release and is slated for removal in the upcoming version.
Moreover as previously announced, all subsequent API enhancements and updates are available exclusively on v3. Thus, users interested in utilizing these improvements must migrate to v3, which involves obtaining an API token. For detailed instructions, please refer to the description on the Authorization page.
We appreciate your continued support and encourage you to explore the enhanced functionality provided in v3. If you have any questions or require assistance, our support team is here to help.