Important API-changes
Summary
For some time, we have been transitioning away from our old technical platform. We have completed step 1 of our transition (Q3 2024), and we are now preparing for the next phase. Now, even more API endpoints will change URLs and require our new authentication (OAuth 2.0).
End of Life is set to be: 31.01.2025
Affected APIs
Digital Distribution System (current URLs:
api.dds.boknett.no/*
,idp.dds.boknett.no/*
)Old endpoints will be turned off 01.02.2025
Order API (current URL:
api.order.boknett.no
)Old endpoints will be turned off 01.02.2025
What do I need to do?
General
Change the authentication to Authentication Service
Each service has it’s own
audience
needed when fetching token
Change the URL for each API
No need for the previously required
Date
-header
Response-headers are considered to be case-insensitive
I.e. don’t only look for
Location
, the header might be calledlocation
If you are getting
413
errors try to reducepagesize
in the call, we will have a period with reduced payload-capabilities (both request and response)
Audiences
The APIs are divided into several audiences (groups). Each API needs an access-token for the corresponding audience. So be sure to use the appropriate audience when fetching the token or you will get 403
.
| Audience-value to use with Auth, see Use of Audience |
---|---|
dds |
|
bokskya |
|
orders |
|
reporting |
|
Production -vs- Test/stage
Login/auth →
auth.bokbasen.io
-vs-auth.stage.bokbasen.io
Audience →
api.bokbasen.io
-vs-api.stage.bokbasen.io
API-endpoints →
api.bokbasen.io
-vs-api.stage.bokbasen.io
New Endpoints
Each API has gotten a new URL. Here you can see a overview of the new URLs as well as the corresponding audience to use.
Auth | API | Method | New endpoint URL |
---|---|---|---|
dds |
|
| |
|
| ||
|
| ||
|
| ||
bokskya |
|
| |
|
| ||
orders | Send Order New required header |
|
|
|
| ||
|
| ||
|
| ||
reporting |
|
|
How can I test?
When you have gotten credentials (clientId + clientSecret) from Bokbasen.