Every PSB call requires a Bearer token from the Identity Server. Tokens are valid for 3600 seconds by default.

POST /connect/token HTTP/1.1
Host: accp-identity.econnect.eu
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials
&client_id=your-client-id
&client_secret=your-client-secret
&scope=ap

curl -s -X POST https://accp-identity.econnect.eu/connect/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials" \
  -d "client_id=your-client-id" \
  -d "client_secret=your-client-secret" \
  -d "scope=ap"

{
  "access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...",
  "expires_in": 3600,
  "token_type": "Bearer",
  "scope": "ap"
}

Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...

Send this header with every request to accp-psb.econnect.eu. Invalid or expired → 401 Unauthorized.

There is no separate refresh-token flow for Client Credentials: request a new token (for example after ~3500 s) so calls do not fail mid-batch.

Do rights run through an end-user account? Use Resource Owner Password Credentials, fully explained in Authentication.

First API call (GET /me)