Edvisor API - Troubleshooting API OAuth Authentication Errors
This guide outlines some troubleshooting steps to help you resolve OAuth Authentication Errors
Troubleshooting API Authentication and 500 Internal Server Errors
1. Confirm Your API Endpoint
- Only use the current Edvisor API endpoint:
https://api-v2.edvisor.io/graphql - Previous endpoints, such as
https://api.edvisor.io/graphql, have been deprecated. If you use an outdated address, your requests may fail or be blocked.
2. Double Check Your Authorization Header
- The Authorization header must be formatted exactly as:
Authorization: Bearer <your_edvisor_api_key> - Errors often occur because of typos, missing the ‘Bearer’ prefix, or including extra spaces.
3. Review Your Token or API Key
- Confirm the API key being used (private), is identical to what has been provided, and correctly pasted into your integration
- If unsure, request to regenerate your key from our support team, and apply the update.
4. Use the Correct Content-Type
- Set your
Content-Typeheader to:application/json - This is required for Edvisor APIs to interpret your payloads correctly.
5. Deleted Users
- Check if you have deleted any users recently.
- API Keys are connected to the users in your account; deleting users will break the corresponding API key's authentication.
- Contact our team to generate a new API key for you.
7. Check for Typographical Errors
- Thoroughly check headers and configuration fields for typos or unintentional spaces. Even a small error can prevent successful authentication.
8. Contact Edvisor Support for Assistance
- If all steps above fail, connect with our dedicated support team. Use:
- In-app live chat
- Email: support@edvisor.io
- Attach any relevant error responses or logs for faster resolution.
Troubleshooting Tips: Clearly document the changes you make and any error codes you receive. This information helps both your team and the Edvisor support team resolve issues as efficiently as possible.
If you’re integrating specific Edvisor products—such as Edvisor Payments or Insurance—or need additional API help, please specify the product or endpoint involved for a more targeted resolution.