As was predicted in the previous post, there was a major upgrade to Opaali platform on 2017-06-20 (to version R4 a.k.a. Rel4). The most notable change is the new Telia branding, seen in the visuals but also in the new host names for the portal https://developer.opaali.telia.fi and the API https://api.opaali.telia.fi. (The old addresses developer.sonera.fi and api.sonera.fi still work – I’ll update the new addresses to my sample source code later.)
If you are a registered Opaali user you should have received the e-mail containing a Release note listing the changes, so I won’t repeat those here.
One thing R4 introduced is something called API Console, which you can use to make Opaali API requests without having to write an application first. I have only briefly tried out the API Console, the documentation for it seems quite minimal (and the UI may not be the most intuitive) but if you already know how to use the API you can use this to check the request and response details while writing your own application. To make it easy to use, it prefetches some of the needed parameters, such as your application credentials. The downside of this is that the requests don’t look exactly like the ones you need to make in your own code. I’ll continue using curl for my examples, but the API Console is a handy tool for checking the exact format of things like response bodies.
Api Console
JPLa is a member of the Content Gateway (CGW) to Opaali migration team, specialising in programming related issues and API usage.