Troubleshooting API OAuth authentication errors
Last updated: May 6, 2026
API auth troubleshooting: (1) endpoint = api-v2.edvisor.io/graphql (old deprecated). (2) Authorization: Bearer <key>. (3) verify key. (4) Content-Type: application/json. (5) check for deleted users (breaks key). (6) typo check. (7) support@edvisor.io with logs.
For 500 Internal Server Errors and authentication issues with the Edvisor API.
1. Confirm the API endpoint
Use only the current endpoint: https://api-v2.edvisor.io/graphql.
The previous endpoint https://api.edvisor.io/graphql is deprecated. Old endpoint requests may fail or be blocked.
2. Check the Authorization header
Must be formatted exactly: Authorization: Bearer <your_edvisor_api_key>.
Common errors:
- Typos in the header name.
- Missing the
Bearerprefix. - Extra spaces.
3. Verify the API key
- Confirm the key matches what was provided.
- Check for accidental modifications during paste.
- Request a regenerated key from support if unsure.
4. Set the correct Content-Type
Must be: application/json.
Required for Edvisor APIs to interpret payloads.
5. Check for deleted users
API keys are tied to users. Deleted users break the corresponding API key. Contact support to generate a new API key.
6. Look for typos
Thoroughly check all headers and configuration fields. A small typo prevents authentication.
7. Contact support
If all steps fail:
- In-app live chat.
- Email: support@edvisor.io.
Attach error responses or logs. Document changes made and error codes received — helps both teams resolve faster.
Specify the product or endpoint involved (Edvisor Payments, Insurance, etc) for targeted resolution.