Skip to content

Sales Intelligence · Beta

Bombora
API integration

Ship Sales Intelligence features without building the integration. Full Bombora API access via Proxy and 50+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us
Bombora

Use Cases

Why integrate with Bombora

Common scenarios for SaaS companies building Bombora integrations for their customers.

01

Embed intent-driven account prioritization in your ABM platform

Let your users push their target account lists into Bombora and pull back Company Surge® scores to power predictive account ranking, dynamic personalization, and ad targeting inside your product.

02

Trigger sales workflows on real-time surge events

Subscribe to Bombora webhooks so your sales engagement or CRM product can automatically drop contacts into outbound sequences the moment their account spikes in intent for a relevant topic.

03

Monitor customer accounts for churn risk signals

Give CS platforms the ability to define custom signals around competitor domains and keywords, then continuously score existing customers so account managers get alerted before renewal conversations go sideways.

04

Power a native B2B audience builder for AdTech and CDPs

Use Bombora's taxonomy and Digital Audience APIs to let marketers build, estimate, and activate custom intent-based segments for programmatic and CTV campaigns without leaving your platform.

05

Enrich lead scoring models with third-party intent

Batch-pull Bombora intent data on a nightly cadence to feed RevOps teams' predictive lead scoring, routing rules, and CRM analytics inside your platform.

What You Can Build

Ship these features with Truto + Bombora

Concrete product features your team can ship faster by leveraging Truto’s Bombora integration instead of building from scratch.

01

Target Account List sync

Two-way sync between your users' account lists and Bombora Account Lists, including adding, updating, searching, and bulk-deleting monitored domains.

02

Custom intent signal builder

A native UI for users to create, update, and delete Bombora signal definitions using product keywords, competitor URLs, and domains — with metadata and product definitions managed via bulk update endpoints.

03

Company Surge® enrichment pipeline

Scheduled jobs that submit intent retrieval requests and paginate through Bombora data to enrich native account records with domain-level scores and score labels.

04

Webhook-driven surge automations

Let users register Bombora destinations, subscribe to event types, and trigger downstream workflows in your app when accounts cross intent thresholds.

05

Native B2B taxonomy pickers

Populate audience-builder dropdowns from Bombora's topics, B2B/B2C interests, firmographics (company size, industry, revenue), demographics (seniority, functional area, persona), and geographic reference data.

06

Digital audience activation console

Preview reach with the audience estimate endpoint, create digital audiences from selected criteria, and activate or deactivate them for downstream DSPs — all from within your product.

SuperAI

Bombora AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

list_all_bombora_signal_definitions

List all Bombora signal definitions. Returns: signalDefinitionId, status, topicCount, createdDate, modifiedDate, metadata.

get_single_bombora_signal_definition_by_id

Get a single Bombora signal definition by id. Returns the full signal definition including signalDefinitionId, status, topicCount, createdDate, modifiedDate, metadata, and topics. Required: id.

create_a_bombora_signal_definition

Create a new Bombora signal definition from product data points such as domain, keywords, and urls. Returns: signalDefinitionId. Required: metadata.

update_a_bombora_signal_definition_by_id

Replace a Bombora signal definition by id with new topics and metadata. Returns: metadata, topics. Required: id.

delete_a_bombora_signal_definition_by_id

Delete a Bombora signal definition by id. Returns an empty 200 response on success. Required: id.

list_all_bombora_account_lists

List all Bombora account lists. Returns each list's id, type, name, description, accountsLastModified, accountTotal, pendingUpdate, createdDate, and modifiedDate.

create_a_bombora_account_list

Create a new Bombora account list from an AccountListDefinition body specifying the list type, metadata, and type-specific specification. Returns: id. Required: type, metadata, specification.

get_single_bombora_account_list_by_id

Get a single Bombora account list definition by id. Returns: type, metadata, specification. Required: id.

update_a_bombora_account_list_by_id

Update a Bombora account list definition by id. parentId and type are not modifiable. Returns the updated definition including type, metadata (name, description), and specification. Required: id, type, metadata, specification.

delete_a_bombora_account_list_by_id

Delete a Bombora account list by id. A 409 Conflict error is returned if the account list is used as a parent of a derived account list. Returns an empty 200 response on success. Required: id.

list_all_bombora_destinations

List Bombora webhook destinations. Returns: destinationId, name, description.

create_a_bombora_destination

Create a Bombora webhook destination for use with event type subscriptions. Returns: destinationId.

get_single_bombora_destination_by_id

Get a single Bombora webhook destination by id, excluding the auth object. Returns: name, description, address, headers. Required: id.

update_a_bombora_destination_by_id

Replace a Bombora webhook destination by id, excluding the auth object — use the separate auth endpoint to update auth. Returns an empty 200 response on success. Required: id.

delete_a_bombora_destination_by_id

Delete a Bombora webhook destination by id. All related subscriptions are also deleted, but all events must be disabled first or the request fails with a 409. Returns an empty 200 response on success. Required: id.

list_all_bombora_data

Retrieve paginated Bombora intent data using a page token obtained from the corresponding POST request. Returns: domain, score, scoreLabel. Required: pageToken. Response body size will not exceed 10MB; if the result set exceeds this limit, fewer results are returned than the requested limit.

create_a_bombora_datum

Submit a Bombora intent data retrieval request that describes the attributes and filters for data fetched via the corresponding GET endpoint. Returns: pageToken. The body must contain either signalDefinitionId or topics, but not both; when attributes is empty or unspecified, domain, score, and scoreLabel are returned by default.

create_a_bombora_oauth_token

Generate an OAuth 2.0 bearer token from Bombora by providing valid client credentials. Returns: access_token, token_type, expires_in. The returned token is used in the Authorization header for authenticated Bombora API calls.

list_all_bombora_signal_definition_metadata

Get the metadata of a Bombora signal definition. Returns: description. Required: signal_definition_id.

bombora_signal_definition_metadata_bulk_update

Update the metadata of a Bombora signal definition by replacing its name, description, and clientId. Returns: name, description, clientId. Required: signal_definition_id.

list_all_bombora_signal_definition_product_definitions

Get the product definition for a Bombora signal definition. Returns: domain, keywords, urls. Required: signal_definition_id.

bombora_signal_definition_product_definitions_bulk_update

Replace the product definition inputs for a Bombora signal definition. The signal definition enters the 'Processing' state and its topics collection is overwritten before returning to 'Available'. Returns: domain, keywords, urls. Required: signal_definition_id.

list_all_bombora_events

Get the configuration and delivery stats for a specific Bombora webhook event subscription. Returns: enabled, headers, stats. Required: destination_id, event_type.

bombora_events_bulk_update

Replace the event subscription document for a Bombora webhook destination to enable or disable an event type and set custom headers. Returns an empty 200 response on success. Required: destination_id, event_type.

bombora_events_bulk_delete

Delete a Bombora webhook event subscription from the specified destination's subscription list. Returns an empty 200 response on success. Required: destination_id, event_type.

bombora_auths_bulk_update

Replace the auth object for a Bombora webhook destination. Returns the updated auth object including its secret. Required: destination_id.

list_all_bombora_accounts_domains

List all distinct domains in a Bombora account list. Returns an array of domain name strings (e.g., bombora.com, starbucks.com). Required: account_list_id.

update_a_bombora_account_list_account_by_id

Submit accounts to a Bombora account list by posting to the list's accounts collection. Required: account_list_id. The request body shape is not described in Bombora's publicly reachable API reference, which requires a developer-portal login; consult the linked documentation before calling.

bombora_account_list_accounts_search

Search the accounts in a Bombora account list. Returns the matching accounts from the response's accounts array. Required: account_list_id. Any additional search or filter parameters are not described in Bombora's publicly reachable API reference, which requires a developer-portal login.

create_a_bombora_account_list_account

Search the accounts in a Bombora account list by posting a JSON request body, the POST counterpart of this resource's search method on /accounts/search. Despite the create name this method does not create an account. Required: account_list_id. The request body shape is not described in Bombora's publicly reachable API reference, which requires a developer-portal login; consult the linked documentation before calling.

bombora_account_list_accounts_bulk_delete

Delete accounts from a Bombora account list in bulk, sending the identifiers in a JSON request body on the DELETE call. Required: account_list_id. Compare with the account_list_delete_accounts create method, which deletes accounts through POST /delete-accounts with an ids array and is documented as valid only for the Manual account list type. The request body shape is not described in Bombora's publicly reachable API reference, which requires a developer-portal login; consult the linked documentation before calling.

create_a_bombora_account_list_delete_account

Delete specified accounts from a Bombora account list. Returns an empty response on success. Required: account_list_id, ids. Only valid for Manual Account List Type.

list_all_bombora_topics

List Bombora intent topics with optional filtering by id, name, theme, category, or description. Returns: id, name, theme, category, description. Filters accept comma-separated case-insensitive values applied with OR logic. The 's' parameter returns similar topics (up to 50 by default, adjustable via maxTopics).

list_all_bombora_b_2_c_interests

List supported B2C interest attributes from Bombora. B2C interest represents the B2C topics a given device has shown interest in. Returns: name. The response is a collection of topic-name objects (e.g. Acura, Audi, Baseball, Wine, Yoga).

list_all_bombora_b_2_b_interest_groups

List B2B interest group attributes from Bombora's Reference API. Each item represents a B2B topic category (from Bombora's Topic Taxonomy) that a given device may have shown interest in. Returns: name.

list_all_bombora_install_data_products

List Bombora Install Data Products — technologies installed by members of an audience. Returns the products array, where each product includes its name.

list_all_bombora_firmographic_company_sizes

List Bombora firmographic company size attributes. Returns a collection of company size records, each containing a name description such as "Large (1,000 - 4,999 Employees)" or "Micro (1 - 9 Employees)". Returns: name.

list_all_bombora_firmographic_industries

List Bombora firmographic industry attributes — a collection of industry names, some hierarchical (e.g. Agriculture > Animals & Livestock). Returns: name.

list_all_bombora_firmographic_revenues

List company revenue attributes from Bombora firmographic reference data. Returns each revenue band's name (e.g., "Large ($100MM-$200MM)", "Micro (<$1MM)").

list_all_bombora_demographic_functional_areas

List Bombora employee functional area attributes. Returns: name. No required parameters.

list_all_bombora_demographic_seniorities

List employee seniority attributes in Bombora. Returns a collection of seniority levels, each identified by its name (e.g., Board and Ownership, Csuite, Management, Non-management). Returns: name. No required parameters.

list_all_bombora_demographic_professional_groups

List employee professional group attributes in Bombora. Returns: professionalGroup.

list_all_bombora_demographic_b_2_b_personas

List Bombora B2B personas, which are demographic attributes used to identify employees showing positive intent. Returns: name.

list_all_bombora_geographic_countries

List geographic country attributes in Bombora. Returns: name, isoCode. No required parameters.

list_all_bombora_geographic_states

List Bombora geographic state attributes (returned for US and CA only). Returns: name, stateCode, countryIsoCode.

list_all_bombora_geographic_metro_areas

List metropolitan area attributes in Bombora, used for geographic targeting in account lists. Returns: name. Each record contains only the metropolitan area name.

list_all_bombora_destination_events

List subscribable event types for a Bombora webhook destination, along with each event's current enabled or disabled status. Returns: eventType, enabled. Required: destination_id.

create_a_bombora_digital_audience

Create a new Bombora DAB custom audience for a specified data exchange. Returns a 201 Created response on success. Required: dataexchange, name, endDate. At least one of topics, domains, filters, surgeId, or granularInstallData must also be provided; additional required fields like externalId, partnerId, and cpmPrice vary by data exchange.

get_single_bombora_digital_audience_by_id

Get an existing Bombora digital audience by data exchange, external id, and partner id. Returns: externalId, partnerId, cpmPrice, name, endDate, topics, domains, filters, surgeId, granularInstallData, filterOr, entityParty, status. Required: dataexchange, external_id, id.

update_a_bombora_digital_audience_by_id

Update an existing Bombora digital audience with a full overwrite of all audience settings. Returns an empty 204 response on success. Required: dataexchange, external_id, id, name, endDate. At least one of topics, domains, filters, surgeId, or granularInstallData must also be provided.

delete_a_bombora_digital_audience_by_id

Delete an existing Bombora digital audience by data exchange, external id, and partner id. Returns an empty 204 response on success. Required: dataexchange, external_id, id.

bombora_digital_audiences_activate

Activate an existing suspended Bombora digital audience. Returns an empty 204 response on success. Required: dataexchange, external_id, partner_id.

bombora_digital_audiences_deactivate

Suspend an existing Bombora Digital Audience. The Last Modified By column for the audience will be set as DAB API. Returns an empty 204 response on success. Required: dataexchange, external_id, partner_id.

create_a_bombora_digital_audience_estimate

Estimate the size of a Bombora digital audience before creation. Returns: count. Required: dataexchange and a request body containing at least one of domains, topics, or filters.

Why Truto

Why use Truto’s MCP server for Bombora

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 800+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Go live with Bombora in under an hour. No boilerplate, no maintenance burden.

01

Link your customer’s Bombora account

Use Truto’s frontend SDK to connect your customer’s Bombora account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call Bombora

Truto’s Proxy API is a 1-to-1 mapping of the Bombora API. You call us, we call Bombora, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate Bombora’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Bombora on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How does authentication work for Bombora?

Truto handles Bombora's OAuth token flow for your end users via the create_a_bombora_oauth_token endpoint and bombora_auths_bulk_update, so you don't need to manage credential storage, refresh, or rotation yourself.

Can we pull Company Surge® intent scores through the integration?

Yes. You submit an intent retrieval request with create_a_bombora_datum and then paginate results via list_all_bombora_data to fetch domain, score, and score label data for the accounts and signals you're monitoring.

Does the integration support real-time surge events or only polling?

Both. You can poll list_all_bombora_events on a schedule, or register webhook destinations with create_a_bombora_destination and manage event subscriptions via bombora_events_bulk_update to receive push notifications when intent spikes occur.

Can our users bring their own target account lists into Bombora?

Yes. You can programmatically create account lists, add or update accounts, search list contents, and bulk-delete accounts using the account list and account list account endpoints — so users can sync their CRM accounts into Bombora without manual uploads.

Is Bombora's reference taxonomy available for building our own UI?

Yes. Truto exposes list endpoints for topics, B2B interest groups, B2C interests, install data products, firmographics (company size, industry, revenue), demographics (seniority, functional area, professional group, B2B persona), and geographic data (countries, states, metro areas) so you can render native pickers.

Can we build and activate digital audiences programmatically?

Yes. You can estimate audience size before provisioning with create_a_bombora_digital_audience_estimate, then create, update, activate, deactivate, or delete audiences using the digital audience endpoints for downstream programmatic activation.

Bombora

Get Bombora integrated into your app

Our team understands what it takes to make a Bombora integration successful. A short, crisp 30 minute call with folks who understand the problem.