Release date
CERT: 4/26
PROD: 5/3
Please reach out to your respective account manager/Zero Hash contact for more details
Release type
Actionable – Updates required for platforms using withdrawals.
Summary
Currently Zero Hash withdrawal_request_ids are generated as an “integer” type. We will be implementing a change to improve performance related to withdrawal request generation that requires the withdrawal_request_ids to migrate to a UUID “string” type.
Action required
Platforms need to adjust to make sure they support ingesting the withdrawal_request_id or id (withdrawal endpoints) as a “string” instead of as an “integer”.
Note: The withdrawal_request_id or id (withdrawal endpoints) is only submitted to the API when using the GET /withdrawals/requests/:id endpoint. In that case, the id is submitted as a url parameter and interpreted as a string. Therefore, there will always be backwards compatibility with the old integer format. Upon the cutover, the id parameter in the response json will change to a string. Otherwise, any id submitted will be backwards compatible.
Impacted endpoints
Impacted endpoints
- GET /withdrawals/requests
- GET /withdrawals/requests/:id
- POST /withdrawals/requests
- GET /accounts/:account_id/movements
- DELETE /withdrawals/requests/:id
- GET /withdrawals/locked_network_fee
- POST /withdrawals/execute
Relevant documentation
Review updated OpenAPI Spec: https://api.cert.zerohash.com/api-docs/