Reference data
Most APITube filters take an ID, not free text: category.id=medtop:20001126, source.country.code=us, industry.id=…. This section is where those values come from — browsable lists for the fixed taxonomies, and endpoints for the ones large enough to need search.
Browsable lists
Fixed value sets you can read here and hard-code in a filter UI:
| List | Feeds the filter |
|---|---|
| List of Countries | source.country.code |
| List of Languages | language.code |
| List of Categories | category.id — IPTC Media Topics |
| List of Topics | topic.id — curated news beats |
| List of Industries | industry.id — business sectors |
APITube does not index every language in existence — check yours with a cheap count request before building on it.
Fetched at runtime
GET /v1/news/event-types returns every valid value for the event.type and event.category filters. Call it to populate a filter UI or to validate input, instead of copying codes by hand.
Autocomplete (Suggest)
Entities, categories, topics and industries are too numerous to list, so each has a typeahead endpoint that turns a name prefix into an ID you can filter on:
| Endpoint | Resolves to | Guide |
|---|---|---|
GET /v1/suggest/entities?prefix= | entity.id — people, companies, brands, places, products | Suggest entities |
GET /v1/suggest/categories?prefix= | category.id | Suggest categories |
GET /v1/suggest/topics?prefix= | topic.id | Suggest topics |
GET /v1/suggest/industries?prefix= | industry.id | Suggest industries |
curl "https://api.apitube.io/v1/suggest/entities?prefix=elon&api_key=YOUR_API_KEY"Entity results carry Wikipedia and Wikidata links alongside the ID, which makes them usable directly in a search UI.
Why IDs matter
An unknown parameter or an invalid value does not raise an error — the request returns 200 ok and the filter silently does not apply, so a typo looks like a successful query over the entire index. Resolving values through these lists and endpoints is the cheapest way to avoid that. See Debugging API requests for how to confirm what the API actually received.
Next steps
- Build a search-as-you-type UI: Build an autocomplete search box
- See every filter these values plug into: Parameters
- Look up a term: Glossary