Reference data
Use these lists and search endpoints to find valid filter values. For example, category.id=medtop:20001126 selects a category, source.country.code=us selects a country, and industry.id=… selects an industry.
Browsable lists
Browse the lists below to choose values for your filters or search interface:
| 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 — specific news subjects |
| List of Industries | industry.id — business sectors |
Language coverage varies. Use a count request to check coverage for the language you need.
Get the current list from the API
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)
To search for an entity, category, topic or industry, send the beginning of its name to a Suggest endpoint. Use the returned ID in your filter:
| 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 invalid value may be ignored while the API returns 200 ok. Use the values from these lists and endpoints to avoid typos. See Debugging API requests to check which filters the API accepted.
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