Help
Start with the symptom.
| Symptom | Go to |
|---|---|
| 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 |
The one that catches everyone
APITube returns 200 ok for parameters it does not recognise, and the filter simply does not apply. A misspelled parameter therefore looks like a successful query — over the entire index, unfiltered. The same goes for an invalid value, and for wildcards, which are not supported.
The fix is to read back what the API received: the user_input object in the response echoes your parameters, so you can see exactly which ones survived. Debugging API requests walks through it.
More material
- Cookbook — worked solutions to concrete tasks.
- Common workflows — the example library and end-to-end recipes.
- Migrations — coming from another news API, including the behaviour differences that surprise people.
Still stuck
Ask the chat widget on any documentation page, or contact support through apitube.io. Include the request_id from the response — every API response carries one, and it identifies the exact request in the logs.