Skip to main content
Inputs: product (free text) · location (a country). Returns: a deduped shortlist of suppliers. A bare POST /v2/search with only a free-text describe field mixes in repair shops, rental firms, and parts makers, and the order drifts between runs. The quality comes from disciplined parameters that this template bakes in.

The recipe

Set ISTARI_API_KEY, then swap in your product and country. The request maps to POST /v2/search.

What each lever does

Validated example

product="industrial valves", country="Spain" → a clean mix of manufacturers and distributors: The same template was validated across different use cases like MacBooks (UAE, distributor-heavy), hydraulic pumps (Germany, maker-heavy), solar panels (India, mixed), electronic components (Singapore, trading hub), and surgical gloves (India — Asma, Kanam Latex, Saachi), one parameter set, product-appropriate skew in every geography.

Notes

Don’t set min_score. Keywords trigger hybrid retrieval, where a min_score of ~0.45 can collapse a clean 12-result query down to 1. Let NACE + keywords do the precision work.
  • Country is activity-based. GOI resolves location by where an organization is active, not solely legal HQ: a firm operating in your market can appear even if incorporated abroad. If strict incorporation matters, post-validate.
  • City filters are coarse. municipality=["Dubai"] can return zero (geocoding granularity). Prefer country, or region/state via resolve_location.
  • Ignore the Total field in keyword mode: it reports 0 while returning a full page. Count the returned rows.
  • For strict product matching, add "must_all": ["<core noun>"] inside keywords (fewer results, higher precision).