Applies to: HReasily Pro API (OAuth 2.0 Authorization Code flow)
Updated: 16 November 2026
Summary
On 16 November 2026 we improved how the HReasily Pro API protects OAuth client secrets. If your OAuth application was created before 16 November 2026, generate a new client secret and update it in your integration.
This article also covers a PKCE authorisation issue fixed on the same day, and changes to our API documentation.
Action required: generate a new client secret
Client secrets are now stored in a secure, hashed form and are shown only once, when they are generated. Secrets issued before this change must be replaced.
- Go to Applications on the HReasily Pro developer portal and sign in.
- Open your OAuth application.
- Click Regenerate secret.
- Copy the new secret right away. It won't be shown again.
- Replace the old secret in your integration's configuration, then test that it can authorise and get a token.
Your Client id and Redirect Uris stay the same. Only the secret changes.
If you have more than one OAuth application, repeat these steps for each one.
Lost your secret later? The Client secret field shows "Hidden for security". Click Regenerate secret to create a new one. The previous secret stops working.
Other changes in this update
PKCE is optional again for confidential clients (fixed)
From 3 to 16 November 2026, the authorisation endpoint required PKCE (Proof Key for Code Exchange) for every OAuth client, although our documentation says it's optional. Integrations that don't send a code_challenge may have failed to authorise during that period.
Since 16 November 2026:
- Confidential clients (server-side applications that keep a client secret): PKCE is optional. All integrations registered today are confidential clients.
- Public clients (for example, mobile or single-page apps): PKCE is required.
We still recommend adding PKCE to your flow as good security practice.
New API documentation and renamed operation IDs
The API documentation now offers Swagger, ReDoc and Scalar viewers.
- API routes, requests and responses have not changed.
- Some operation IDs in the OpenAPI schema were renamed. If you generate client code from our schema, review the list of renamed operations before you regenerate.
Who needs to do what
| If you… | Do this |
|---|---|
| Have an OAuth application created before 16 November 2026 | Generate a new client secret (required). |
| Had authorisation errors between 3 and 16 November 2026 | Generate a new client secret. The PKCE issue itself is fixed. |
| Generate API client code from our OpenAPI schema | Review the renamed operation IDs before you regenerate. |
| Create a new OAuth application from 16 November 2026 | Copy the secret when it's shown. No other action needed. |
Need help?
Contact our support team at connect@hreasilygroup.com. Include your OAuth application name (never your secret) and the error message you see.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article