An API request may return no result when the submitted input cannot be matched, validated, or processed with enough confidence by the DQE service being called.
Common reasons
- the input is incomplete or ambiguous;
- required parameters are missing;
- the service called does not support the requested use case;
- the country, postal code, locality, email domain, or phone format is inconsistent;
- the request is sent to the wrong endpoint or environment;
- the licence or configuration does not allow access to the expected service.
What to check first
- Verify that all required parameters are included.
- Check whether the input format matches the API documentation.
- Confirm that the correct endpoint and environment are used.
- Test with a simple known input to confirm the integration works.
- Compare the API response with the expected response format.
When the input is valid but no result is returned
Some services can validate the request format but still return no usable result if the submitted data cannot be matched against the available reference data or if the service cannot determine a reliable answer.
When to contact DQE Support
If the API consistently returns no result for data you expect to be valid, provide the endpoint, request timestamp, environment, input sent, response body, expected result, and any recent configuration changes.
Related articles
- Why is my API request rejected?
- How to troubleshoot API authentication issues
- What information should I provide for an API investigation?