Step 4: first API call

First PSB API call: GET /api/v1/me to verify your token, party context and environment.

Validate credentials and environment with a read-only smoke test before you send documents.

Request
GET /api/v1/me HTTP/1.1
Host: accp-psb.econnect.eu
Accept: application/json
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...
curl
TOKEN=$(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" | jq -r '.access_token')

curl -s \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TOKEN" \
  https://accp-psb.econnect.eu/api/v1/me | jq .
What you check
  • Response is 200 with JSON (no HTML login or gateway error)
  • You recognise tenant/party information that belongs to your sandbox
  • You are talking to accp hosts (not production by accident)
If it fails
SymptomDirection401Token missing, expired, or from another environment403Scope/rights do not match — check scope=ap and account setupTimeout / DNSNetwork from the app server to accp-*.econnect.eu
Explore further