We are making a change to the `GET /api/v1/user/walletHistory` endpoint that may impact API users’ integration.
Issue Identified:
We recently identified a bug in the `GET /api/v1/user/walletHistory` endpoint, where the `count` parameter was not falling back to the expected default value of 100 as documented. This resulted in some clients receiving more data than anticipated from their API requests.
Resolution:
To address this issue, we will be implementing a fix by adjusting the default value for the `count` parameter. Starting from the next release scheduled for Thursday, January 18 at 04:00 UTC, the default value for `count` will be set to 10,000.
Action Required:
If your integration relies on the `GET /api/v1/user/walletHistory` endpoint and you have explicitly set the `count` parameter, no action is required on your part. Your specified `count` value will continue to be honored.
However, if you have not explicitly set the `count` parameter, we recommend reviewing your implementation to ensure compatibility with the upcoming change. Adjustments may be necessary to accommodate the new default value of 10,000 if you rely on the default behavior.
Release Schedule:
The planned release date for this change is Thursday, January 18 at 04:00 UTC. Please make the necessary adjustments to your integration before this time to avoid any disruptions.
We appreciate your attention to this matter and apologize for any inconvenience caused. If you have any questions or concerns, please reach out to Support.
To be the first to know about new listings, product launches, promotions or other updates we invite you to join one of our communities and follow us on Twitter or check our blog regularly.