The Fetch Business Autocomplete endpoint provides real-time suggestions for business-related fields, helping users quickly find relevant categories, locations, and industries based on partial text input. This is useful for creating dynamic search fields and enhancing user experience in filtering interfaces.
Coverage
Attribute
Coverage Details
Supported Fields
Country, Region, Google Category, NAICS Category, LinkedIn Category, etc.
Geographic Scope
Supports 150+ countries
Response Time
Optimized for real-time autocomplete functionality
How It Works
Input: Specify a field type (country, region_country, etc.) and provide a partial query string.
Processing: The system searches through indexed datasets to return the most relevant suggestions.
Output: A structured response containing suggested values for the given input.
Query Parameters
Parameter
Type
Description
field
String
The field for which autocomplete is requested (e.g., country, industry).
query
String
Partial text input to generate suggestions.
semantic_search
Boolean
Optional. When true, enables semantic autocomplete to return a broader, topic-aware set of suggestions. This parameter is intended for use with the business_intent_topics field.
Example Request (cURL)
Example with contry field.
Bash
curl -X GET \ "https://api.explorium.ai/v1/businesses/autocomplete?field=country&query=unit" \ -H "API_KEY: your_api_key_here"
Example with business_intent_topics field.
Bash
curl -X GET \ 'https://api.explorium.ai/v1/businesses/autocomplete?query=cloude&semantic_search=true&field=business_intent_topics' \ -H "API_KEY: your_api_key_here"
The businesses and prospects autocomplete endpoints support the same set of fields.
Filter
Description
Example Input
country
Autocomplete for country names
"Uni" → United States, United Kingdom
country_code
Autocomplete for country codes (ISO 2-letter)
"US" → United States
region_country_code
Autocomplete for region-based country codes
"EU" → European Union countries
google_category
Google’s business category classification
"E-com" → E-commerce
naics_category
Industry classification based on NAICS codes
"541512" → Computer Systems Design Services
linkedin_category
Industry classification from LinkedIn data
"Retail" → Retail Industry
company_tech_stack_tech
Technologies used by a company
"Cloud" → Cloud Computing, Cloud Security
company_tech_stack_categories
Technology categories used by the company
"Marketing" → CRM, AdTech
job_title
Autocomplete for job titles
"Soft" → Software Engineer, Software Developer
company_size
Autocomplete for company sizes (by number of employees)
"500" → Companies with ~500 employees
company_revenue
Revenue-based classification (K, M, B, T for thousands, millions, billions, trillions)
"100M" → $100 Million+
number_of_locations
Number of physical company locations
"1" → Companies with a single location
company_age
Company age in years
"10" → Companies older than 10 years
job_department
Autocomplete for job departments
"Eng" → Engineering, Product Engineering
job_level
Job seniority levels
"Senior" → Senior Manager, Senior Engineer
skills
Skills listed on a prospect’s profile
"Pyth" → Python, Python Scripting
interests
Professional interests listed on a prospect’s profile
"Sustain" → Sustainability, Sustainable Energy
city_region_country
Combined location filter by city, region, and country
"New York, NY, US" → Companies in New York
company_name
Filter by company name
"Meta" → Meta Platforms Inc.
business_intent_topics
Business intent topics — It is recommended to use semantic_search=true to receive a broader and smarter autocomplete result that identifies wider semantic connections to the searched term.
"cloud" → technology: cloudflare, cloud: cloud server
Best Practices
Use precise queries to get the most relevant autocomplete results.
Enable semantic_search=true when working with business intent topics to receive broader, smarter, and semantically-aware suggestions.
Optimize search fields by implementing real-time feedback mechanisms.
Restrict field selection to avoid unnecessary queries and improve API efficiency.
Combine with filtering APIs to refine user selections dynamically.
For detailed endpoint explanations, request examples, and integration tips, explore the documentation sections above.