We're improving our API infrastructure and updating our APIs to provide better performance and make it easier to use for our customers and partners to integrate with us.
Our new API endpoints are backwards compatible with our current API infrastructure. This means you can use existing bearer tokens on current and new API endpoints.
Once all our endpoints are available on the environment, we'll let you know more details so that you can migrate completely to the new environment. The process will required you to update the way you connect with our APIs and obtain an API tokens. More information to follow:
In order to access any new API endpoints, you need to change the base URL to point to our new server. The new server will accept valid Class OAuth tokens obtained for our current API auth/token endpoints.
If you want to access current API endpoints and new API endpoints, the only difference in the call for new endpoints, is the base URL. See Using the API for details of the new Base URL and how to use it. All existing endpoints will remain working the same as before.
Current BASE URL: api.class.com.au > New BASE URL: apigateway.class.com.au
We're also in the process of creating a new developer portal (to eventually replace API Reference), where you can find details of all new endpoints available via the new API infrastructure. This portal will be available soon, in the meantime the API support team will assist you with documentation to help you use these new endpoints when they become available. All our current endpoints are still available via the existing API Reference.
New endpoint documentation temporarily available here: