PostNord APIs use OAuth client credentials

PostNord's Norway developer portal is automatable through its APIs for a PostNord business customer. The getting-started guide says authentication is the OAuth 2.0 client-credentials grant. The client exchanges a client ID and client secret for a bearer token, then sends that token on API calls. Credentials are issued after the business activates developer resources. An invoice agreement is required and is described as free of charge with no volume requirement. Sandbox and live environments have separate credentials. A Postman collection is offered. API descriptions can be read without logging in. The Booking API page says it returns product options, prices, pickup choices, and an estimated delivery time, and that it can order a shipment with a pickup agreement and a label, including named parcel, pallet, and groupage products. The Authentication API page says its token is the authorization for the APIs in the catalog. The interactive reference behind the documentation button was not copied field by field. No PostNord MCP server was established from the pages opened here. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 6 because booking and authentication are documented and a customer account is required.

Best path today: api · Overall automatability: 6/10