On this page
Help
Find the guide that matches your problem.
| Symptom | Go to |
|---|---|
No articles, a rejected API key or HTTP 429 | Troubleshoot a request — check a request step by step |
| A term in the docs means nothing to you | Glossary |
| A general "how does X work" question | Technical FAQ |
The request returns 200 but the results look wrong | Debugging API requests |
| The request returns an error code | HTTP response codes |
429, or requests being throttled | Rate limits and quotas |
402, or points running out faster than expected | Balance and usage |
| Everything fails at once | API Status |
Filters that do not apply
An unrecognised parameter does not cause an error: the API returns 200 ok and ignores that filter. Check parameter names and values when results are broader than expected. Wildcards are not supported.
Check user_input in the response to see which parameters the API accepted. Follow Debugging API requests for a step-by-step check.
More material
- Cookbook — worked solutions to concrete tasks.
- Usage examples — requests grouped by filter and result options.
- Recipes — end-to-end guides for a specific task.
- Migrations — coming from another news API, including the behaviour differences that surprise people.
Still stuck
Use the chat widget on any documentation page or contact support at apitube.io. Include the response's request_id so support can find your request.