Summary of changes

TODO En kort tekst for ledelse CEO/CTO

Datoer

Forhandlere

Onix Export

• Onix Export (prod) ikke lenger mulig å nå med gamle URLer: 21.05.2024

TODO Frister

Stage-miljø tilgjengelig DATO

Vi sender ut påloggingsinformasjon DATO

Prod-miljø tilgjengelig med nye URLer DATO

Prod-miljø ikke lenger mulig å nå med gamle URLer DATO

Berørte APIer

Forhandlere

• Onix Export API (current URLs: api.boknett.no/metadata/export/onix/*)

• Object Export API (current URLs: api.boknett.no/metadata/export/object/*)

• Digital Distribution System (current URLs: api.dds.boknett.no/*, idp.dds.boknett.no/*)

• Order API (currently: api.order.boknett.no)

Utgivere og distributører

• Onix Import API (currently: api.boknett.no/metadata/import/onix/*)

• Object Import API (currently: api.boknett.no/metadata/import/object/*)

Technical Guide

What do I need to do?

General

• Change the authentication to Authentication Service (for selected services)

  • Each service has it’s own audience needed when fetching token

• Change the URL for each API

Retailers

...

Change ONIX

Publishers & Distributors

...

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).

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 called location

• If you are getting 413 errors try to reduce pagesize 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.

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.

How can I test?

When you have gotten credentials (clientId + clientSecret) from Bokbasen.