Class provides two environments: PIE (Partner Integration Environment) for building and testing, and Production for live customer data.
Each environment has its own credentials and its own endpoints. An integration configured for one will not work against the other.
Class uses two hosts per environment — app.* for authentication, api.* for the resource APIs. Your OAuth client talks to the app.* host to obtain a token; every data call afterwards goes to the api.* host.
| Purpose | Endpoint |
|---|---|
| Authorisation | https://app.class.com.au/connect/authorize |
| Token | https://app.class.com.au/connect/token |
| Resource APIs | https://api.class.com.au/api/1.0/{scope}/{area}/{action} |
| Purpose | Endpoint |
|---|---|
| Authorisation | https://app.class-pie.com.au/connect/authorize |
| Token | https://app.class-pie.com.au/connect/token |
| Resource APIs | https://api.class-pie.com.au/api/1.0/{scope}/{area}/{action} |
See Class API structure for how the resource API path is constructed.
Credentials are issued per environment and do not carry across.
- PIE credentials are issued when your access is approved, so you can begin building.
- Production credentials are issued separately, after your integration passes review.
Keep your PIE and production credentials clearly separated in your configuration. Pointing a production deployment at PIE credentials — or the reverse — is one of the most common integration failures, and the error it produces (invalid_client) does not make the cause obvious.
PIE holds sample data, not a copy of production. When your access is set up you are given one or more business codes with sample funds beneath them, so you can exercise the APIs against realistic structures without touching live data.
Business codes differ between PIE and production. Any business code hard-coded during development will need to change before you go live — including the target:b/{BusinessCode} value in your authorisation scope.
If your integration validates ID tokens, the iss claim is the app.* host for the environment you are in:
| Environment | Issuer |
|---|---|
| Production | https://app.class.com.au/ |
| PIE | https://app.class-pie.com.au/ |
Validate iss against the environment your integration is configured for. See Single Sign-On using Class API for the full set of ID token claims.
Promotion to production requires review and approval. See Production readiness for what is assessed.
When you switch, you need to change:
- Both hosts, from
*-pieto production. - Your client ID and client secret.
- Your registered redirect URL, if it differs between environments.
- Any business codes referenced in scopes or API paths.