his page contains the setup guide and reference information for the Elation Health connector.
Prerequisites
Before connecting your Elation Health account, ensure that:
-
You have an active Elation Health developer account.
-
You are aware of the API environment you are targeting: Sandbox (for testing) or Production (for live data).
Note: Always begin with the sandbox environment to test your workflows. Once verified, switch to the production environment with a new authentication in Keragon.
Setup Guide
Follow these steps to connect your Elation Health account to Keragon:
-
Obtain your Client ID and Client Secret from Elation Health by registering your application through their developer portal or via your account representative.
Reach out to Elation Health
You can reach out to your account representative in Elation to ask for API credentials. Feel free to use the below template.
Hi there, I want to integrate Elation with Keragon through the Elation API. Can you please send me the API credentials?
-
Go to app.keragon.com and open the Elation Health connector setup.
-
Click Create Authentication.
-
Choose the API environment (Sandbox or Production) based on your credentials.
-
Enter the Client ID and Client Secret.
-
Click Connect to complete the integration.
Ensure you match the environment in Keragon to the credentials provided. Sandbox credentials will not work with the production endpoint, and vice versa.
Troubleshooting and Common Errors
| Error Message | Cause | Suggested Fix |
|---|---|---|
401 Unauthorized |
Invalid or expired Client ID/Secret | Verify the credentials and ensure you're using the correct environment. |
403 Forbidden |
Insufficient permissions or unauthorized access scope | Confirm API access and scopes with Elation support or developer documentation. |
Endpoint not found |
Incorrect environment selection (sandbox vs production mismatch) | Switch to the correct environment in Keragon settings. |
Invalid client |
Client credentials not recognized | Confirm that your app is registered and active in Elation’s developer portal. |
Limitations and Notes
-
The Elation Health connector uses OAuth 2.0 Client Credentials for authentication.
-
Separate authentications are required for Sandbox and Production environments.
-
Start all workflow development and testing in the Sandbox environment before going live.
-
Elation Health APIs follow a robust and well-documented structure; refer to Elation API Docs for full endpoint and schema references.