Skip to main content
POST
Fetch Businesses

Description

The Fetch Businesses endpoint allows users to retrieve business records based on filters such as country, industry, company size, and revenue. It returns a structured dataset optimized for further filtering, deduplication, or previewing records before enrichment. This enables precise data-driven decision-making and lead generation. It is designed to help users efficiently find relevant businesses based on their specific criteria.
  • 80M+ businesses across 150+ countries.
  • Advanced filtering options for precise data extraction.
  • Optimized for efficiency, returning only the minimal data needed for further processing.
  • Input: Define filter parameters such as country, industry, revenue range, and company size.
  • Processing: The system searches across multiple datasets to retrieve businesses that meet the criteria.
  • Output: A structured response containing business records for further analysis or enrichment.
JSON

Data Fetching: Pagination, Filtering & Modes

The API supports flexible data fetching through pagination, filtering, and optional modes to customize the amount and structure of the returned data.

Pagination

To efficiently retrieve large datasets, use the following parameters to paginate the results:

Behavior Notes

  • If size is smaller than page_size * page, the last page may contain fewer records or be empty.
  • If pagination parameters are omitted, the API may return a default page size (implementation-specific).

Filtering

Filters allow you to narrow down results based on specific field values. All filters must be included in the request body under the "filters" key, as a JSON object.Each filter field accepts:
  • values: for multiple possible matches (e.g. "values": ["11-50", "51-200"])

Example Request Body

JSON

Filter Matching Logic

  • Fields using values are matched using an OR condition.
  • Filters are combined using an AND across different fields.

Mode Parameter

The optional mode parameter defines the level of detail in the returned data.
preview mode is restricted. It’s blocked by default and available only to paying customers on a custom plan. Use mode: "full". To get preview access, see pricing and plans.What preview returns: each record keeps every field name, but only business_id, name, domain, website, logo, and country_name have values. All other fields are returned as null.

Best Practices

  • Always use page_size to control payload size for better performance.
  • Use size to set an upper limit and avoid unintentionally requesting large datasets.
  • Apply filters whenever possible to reduce response size and processing time.

Note on Filter Usage

  • Only one category filter can be used per request: choose from either Google category, LinkedIn industry, or NAICS code. Combining them is not supported.
Bash
Finding valid intent topics: You can discover supported intent topic values in two ways — use the Autocomplete endpoint with business_intent_topics (preferably with semantic_search=true) for interactive, relevance-ranked suggestions, or download the full topics list as a CSV, which is refreshed weekly with the complete Bombora taxonomy. Topics follow the category: topic format (e.g., technology: ios).
business_intent_topics is a premium filter — 2 credits per returned result instead of the standard 1 credit per result.Always fetch with mode: "full" when filtering by intent — only full mode returns the actual intent topics each business is researching.
  • increase_in_customer_service_department
  • hiring_in_finance_department
  • hiring_in_support_department
  • increase_in_engineering_department
  • decrease_in_customer_service_department
  • hiring_in_operations_department
  • hiring_in_creative_department
  • decrease_in_engineering_department
  • hiring_in_sales_department
  • increase_in_operations_department
  • hiring_in_trade_department
  • decrease_in_marketing_department
  • increase_in_marketing_department
  • hiring_in_marketing_department
  • hiring_in_health_department
  • hiring_in_education_department
  • increase_in_all_departments
  • decrease_in_all_departments
  • decrease_in_sales_department
  • decrease_in_operations_department
  • hiring_in_professional_service_department
  • hiring_in_human_resources_department
  • increase_in_sales_department
  • hiring_in_legal_department
  • hiring_in_unknown_department
  • hiring_in_engineering_department
  • company_award
  • new_product
  • employee_joined_company
  • merger_and_acquisitions
  • lawsuits_and_legal_issues
  • outages_and_security_breaches
  • closing_office
  • new_investment
  • new_office
  • new_partnership
  • cost_cutting
  • new_funding_round
  • award
  • ipo_announcement
Full definitions and examples for each event type are available under Business Events.
The response returns a data array of business records matching your filters, along with pagination metadata. Each business record contains the following signals:In addition to data, the response includes pagination metadata:
For detailed endpoint explanations, request examples, and integration tips, explore the documentation sections above.

Body Params - Try Me Example

Authorizations

api_key
string
header
required

Body

application/json
mode
enum<string>
required

Level of detail in the returned records. Use full.

preview is restricted: blocked by default and available only to paying customers on a custom plan. See pricing and plans.

Available options:
full,
preview
Example:

"full"

page_size
integer
required

The maximum number of businesses in a page. Max limit is 500

Required range: 1 <= x <= 500
Example:

3

request_context
Request Context · object | null
Example:

null

size
integer

The maximum number of businesses to return. Max size is 60000 (which is the default value)

Required range: 1 <= x <= 60000
Example:

3

page
integer | null

The page number to fetch.

Required range: x >= 1
Example:

1

exclude
string[] | null

List of business ids to exclude from the response.

Maximum array length: 1000
Pattern: ^[a-f0-9]{32}$
Example:

null

filters
Filters · object | null
next_cursor
string | null

The sort values from the last document returned by the previous page. If provided, cursor pagination is used instead of page-based pagination. send "null" to start with next_cursor pagination from the beginning.

Example:

null

Response

Successful Response

This is base response model for all responses in partner service.

response_context
ResponseContext · object
required
total_pages
integer
required

The total number of pages.

Required range: x >= 0
data
Business · object[]

List of businesses that match the filters.

total_results
integer

The total number of businesses that match the filters.

Required range: x >= 0
page
integer

The page number of the response.

Required range: x >= 0