API authentication issues usually occur when credentials, licence information, tokens, environments, or request headers do not match the expected configuration for the DQE service being called.
Common symptoms
- the API request is rejected;
- the service returns an authentication or authorization error;
- a token cannot be generated or is rejected;
- the same request works in one environment but not another;
- the integration suddenly stops working after a configuration change.
What to check first
- Verify that you are using the correct environment and base URL.
- Check that the licence, credentials, or token are valid for the service called.
- Confirm that required headers and parameters are included in the request.
- Make sure credentials have not expired or been replaced.
- Check whether the request comes from an authorized network or IP address if access restrictions apply.
Where to find credentials and licence information
Credentials and licence information are available through the DQE customer intranet at new.mydqe.com. For security reasons, DQE Support may request additional verification before updating or sharing access information.
When to contact DQE Support
If the issue persists, provide the service called, environment, request timestamp, endpoint, headers used, error message, and any recent configuration changes. Do not share sensitive credentials directly in the ticket body.