improved
API 2.0 BETA Release
October 4th, 2024 by Jake Wauchope
Overview
API 2.0 is officially out of ALPHA and into BETA (thank you to all our Alpha testers) which means we're opening up our sandbox environment to anyone who wants access. With this rollout comes a few additional tweaks to the spec and a whole host of backend bug fixes.
Version Impacted: V2.0
Date Effective: 4th of October 2024
Want Access to the Sandbox?
If you are interested in trying out the Send Payments API please reach out to us at [email protected] with the subject line "API Integration" and our sales team will get in touch with you!
BETA Improvements
The following tweaks are updates we've made from our most recent Alpha version into our fresh Beta version.
- Updated the auth pattern for webhooks, see our guide here. Please note that webhooks are not available in the sandbox, we aim to release them on the 10th of October
- Removed the requirement in API docs to add a
bearerToken
when using the /auth endpoint. This prevented users from testing the API from the dev site but was not enforced for postman testing. - Updated the sandbox URL. The new BETA URL is: partner-api-demo.uat.sendpayments.dev...
- Removed some fields from post request payloads that were redundant or could be inferred from other fields (ie removing the need to supply both a
fromWalletId
and atradingAccountId
when creating a trade) - Added some additional query parameters to GET endpoints to help with filtering
- Updated post/accounts/corporate to explicitly call out the mandatory fields (ie
authorisedRepresentative
,countryOfRegistration
etc) - Added in magic values, allowing transactions with certain values to be auto-failed/passed
- Added
externalReference
to more endpoints
Bug Fixes
- Fixed issues where optional fields on post/recipients were being forced despite the country guideline not mandating it for the recipients country.
- Fixed some issues with the payments/reason-codes endpoint
- Fixed an issue which caused some valid trades to fail being created
Got Questions?
Got questions or concerns about this change? Head over to our Discussion Board and leave us a note.