PASAR API
Enterprise-oriented pricing (custom quotes, no public self-serve free tier) — the value is one integration reaching Norwegian BankID and other Nordic eIDs, not a cheap hobby key. OAuth2 client-credentials flow with a shared signicat-api scope.
View docs ↗ More Auth & identity APIs# Signicat ~ Nordic digital identity, BankID & e-signature API needs OAuth credentials ~ get yours at: # https://developer.signicat.com/ curl 'https://api.signicat.com/' \ -H 'Authorization: Bearer YOUR_TOKEN'
I'm integrating a Norway API into my app. API: Signicat ~ Nordic digital identity, BankID & e-signature API Provider: Signicat Auth: requires OAuth credentials (sign up: https://developer.signicat.com/) Pricing: paid Base URL: https://api.signicat.com/ Important note: Enterprise-oriented pricing (custom quotes, no public self-serve free tier) — the value is one integration reaching Norwegian BankID and other Nordic eIDs, not a cheap hobby key. OAuth2 client-credentials flow with a shared signicat-api scope. Source: Signicat (https://developer.signicat.com/) Source type: Provider API or developer docs Endpoint type: Provider API base URL Integration difficulty: Needs OAuth Last checked: 2026-07-05 Production caveat: Keep credentials server-side and confirm current limits, pricing, and webhook/error behaviour in the provider docs. Help me set up the correct onboarding/authentication path and make the first valid request ~ explain exactly where credentials go and what must happen before production.