/ docs
ProductKnowledgeDevelopers
Platform Control
Step 2: configure acceptance endpoints

Acceptance versus production endpoints for PSB API, Identity Server, VPD and mailhooks. Avoid mixed-environment bugs.

Configure all hosts for acceptance before the first token request. Mixed environments (accp token with production call, or the reverse) cause cryptic 401/403 errors.

Host table
ComponentAcceptance (sandbox)ProductionPSB APIhttps://accp-psb.econnect.euhttps://psb.econnect.euIdentity Serverhttps://accp-identity.econnect.euhttps://identity.econnect.euVPD (GraphQL)https://accp-vpd.econnect.eu/graphql/v1https://vpd.econnect.eu/graphql/v1Mailhook email@accp.econnect.email@econnect.emailSwagger / OpenAPIhttps://accp-psb.econnect.euhttps://psb.econnect.eu
Configuration pattern

Keep the environment in one config object or env prefix, for example:

ECONNECT_ENV=accp
ECONNECT_IDENTITY_URL=https://accp-identity.econnect.eu
ECONNECT_PSB_URL=https://accp-psb.econnect.eu
ECONNECT_CLIENT_ID=...
ECONNECT_CLIENT_SECRET=...

Switch to production URLs and production credentials only when end-to-end tests (including webhook signatures) are green.

Network and TLS
  • Outbound HTTPS to Identity + PSB must be allowed from your app server
  • No TLS interception that breaks client certificates or SNI
  • Timeouts: allow for validation + routing on send calls (do not set them too aggressively low)
Next step

With hosts and credentials in place: Obtain an OAuth2 token.

Related

Step 1: sandbox
Step 3: OAuth2 token
API overview