- Centralized holds: New endpoints added to the API to be able to operate and manage holds via the API. Holds guarantee a future transfer and make the held tokens unavailable for the user in the meantime.
- Create hold: You can now create a hold via API on a wallet by indicating the target wallet that will receive the transfer in case of execution, the amount, the expiration date, and an optional concept. Check the full details of the request here.
- Execute hold: This endpoint will allow you to close the hold sending the indicated amount to the receiver. The difference amount that was held but not sent will be made available again in the origin account. It is also possible to leave the hold open after an execution using the executeHoldAndKeepOpen endpoint. Check the full details of the requests here.
- Release hold: This action will cancel the hold making the held amount available again to the origin account. Check the full details of the requests here.
- Renew hold: This endpoint will allow you to update the expiration date of a hold to a new value. You can also make a hold perpetual (it never expires). Check the full details of the requests here.
- Get hold: You can use Get endpoints to retrieve a specific hold or all the holds of a specific wallet. Check the full details of the requests here.
- Optional dlt Address in user and wallet creation: We have included the possibility of leaving empty the dlt address in the creation of wallets and users. When empty, the system automatically generates one and disposes its private key. Therefore, it will not be possible for the use case to operate with the wallet directly on the smart contract. These dlt addresses can be changed in the future by new dlt addresses in case the client want to start using smart contract interaction.
With these new features, ioCash platform is now compatible with non-Blockchain clients that want to use our solution to create complex payments and wallet management and take advantage of Blockchain technology but without needing to directly interact with it. They can access all its functionalities by just consuming its APIs.
- Hateoas links base path in API responses: The base-path informed in some of the APi responses links were not correct.
- Transfer-in movement not created in case of failed centralized transfers: In case of error in a transfer originated in the API, a transfer-in movement on the receiver wallet was being created. This has been fixed so that the movement in error is only shown on the sender’s wallet (transfer-out).
- Users with all their wallets in unsubscribed can now create new wallets: We fixed a bug that did not allow to create a new wallet for a user that had before unsubscribed all its wallets.
- Public API endpoints pagination: Now, all GET endpoint responses can be paginated. This improvement has been added for faster loading when retrieving a big list of elements(users, wallets, movements, holds...). By default, the size of the page is set to 20 elements, but this can be configured. You can see more details in all GET list endpoints in the documentation
- Postman API collection: We have uploaded a Postman collection to our Github with all ioCash endpoints so that you can quickly test them and use it as guide when you develop your solution. To check it, click here
- Documentation updates: The dev portal documentation was updated with all the new functionalities and improvements detailed in the above paragraphs.