Before you can integrate, you must register your organisation with Class. Registration is what causes your firm to appear in the Actuarial Certificate Provider options in Class, and links your callback credentials to your provider record.
Contact Class to arrange registration.
You must provide separate staging (PIE) and production information for each of the following:
| Field | Description |
|---|---|
| System name | The name you would like your firm to be listed as in the Actuarial Certificate Provider options in Class. |
| Initial-request endpoint | The URL on your system that Class will POST the fund data to when a user requests a certificate. Must be HTTPS. |
| Payload format | Whether Class should send the initial request as XML or JSON. XML is the default. Your acknowledgement must use the same format. |
| Authentication required? | Whether Class must authenticate when calling your initial-request endpoint. |
| Grant type | If authentication is required, the OAuth grant type your endpoint expects. |
| Your OAuth token URL | If authentication is required, the token endpoint Class should call to obtain a token from your system. |
| Your OAuth client ID | The client ID Class should use when authenticating to your endpoint. |
The authentication requirements for the Class → Provider direction (the initial request) are agreed per provider during onboarding. This is separate from the Provider → Class direction, which always uses the OAuth flow described in the Authentication guide.
After registration, Class will provide you with:
| Item | Description |
|---|---|
| OAuth Client ID | Used to obtain a bearer token for the callback endpoints. Separate values per environment. |
| OAuth Client Secret | Used to obtain a bearer token for the callback endpoints. Separate values per environment. |
| Provider ID | The unique identifier for your organisation. Used in every callback URL as {providerId}. |
| Provider login (user account) | A Class user account set up for your integration, used for the OAuth password grant. This account is granted a special role by Class. |
You do not need to supply any credentials for the Provider → Class direction — Class issues all four of the above.
- Requests from Class to your endpoint are always made over HTTPS.
- Your callbacks to Class are always made over HTTPS with a valid OAuth bearer token.
- Class provisions your integration user with the role required to call the certificate endpoints. You do not need to configure this yourself.
Once you have your Client ID, Client Secret, Provider ID, and provider login credentials, you're ready to start testing in the Partner Integration (PIE) environment. See the Authentication guide to obtain your first token.
Your integration is promoted to production once you have successfully demonstrated it to Class and a partnership agreement has been signed.