Beginning January 1, 2016, Cloud Elements will be sunsetting our API Version 1 (API v1). We will continue to support API v1 calls for the next three months ending on December 31st, 2015. Applications developed using our v1 APIs will no longer function as expected.
If you are currently using our v1 APIs and would like support in moving to our v2 APIs, please contact us at email@example.com. We will be providing support through the end of 2015.
Q: What does sunsetting mean?
A: v1 of our APIs will no longer be supported nor function as expected.
Q: Why is Cloud Elements sunsetting v1 APIs?
A: As with all platforms, the underlying technology becomes more efficient and powerful over time. Cloud Elements is continuously improving its platform and sometimes these improvements are not backwards compatible. Our philosophy is to release improvements as soon as possible to Cloud Elements users’ while at the same time providing a grace period for existing applications to transition smoothly.
Q: How do I know the state of an API version?
A: The API version is documented in the URL of each API call made. For example:
In V2, we updated our core application to better support REST best practices. Conversion to RESTful architecture gives us more consistency across our API and is a well known pattern for API clients.
If you are currently using Version 1, don’t worry, we will be continuing to support Version 1, and you won’t have to change any of your current integrations. And our API console and dashboard will continue to work with both versions. We will continue to support V1 indefinitely, but all new functional changes will be on V2. Changes to V1 will be limited to security patches and operational updates.
See our full API documentation for V1.
Our Elements Manager will support both V1 and V2 APIs. The token generated for you in the Manager will work with both V1 and V2 API calls. You can login to the Manager as usual.
Need help getting started with our V1 APIs?
Our V1 and V2 APIs are available for the same price. Check our Pricing page for more information.
Please contact us with any questions regarding the change to V2.
New OAuth workflow that mimics the standard OAuth authorization grant workflow:
Hub now supports explicit operations by path and provider specific id: