Sales Intelligence · Beta
Cognism
API integration
Ship Sales Intelligence features without building the integration. Full Cognism API access via Proxy and 20+ 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 usUse Cases
Why integrate with Cognism
Common scenarios for SaaS companies building Cognism integrations for their customers.
Embed B2B prospecting inside your sales tool
Let users search Cognism's contact and account database without leaving your app, then import verified records directly into sequences, campaigns, or workspaces. Removes context-switching and makes your product the daily surface for pipeline generation.
Enrich inbound leads and CRM records on the fly
Turn a bare email or domain into a full firmographic and contact profile using Cognism's enrichment endpoints. Ideal for RevOps, lead routing, and form-shortening use cases where accurate company size, industry, and job data drives downstream automation.
Enforce GDPR and DNC compliance at dial/send time
Contact center, dialer, and email platforms can check Cognism's global opt-out list before initiating outreach. Protects end-user companies from regulatory fines and keeps compliance native to your product.
Power ABM and buying-committee discovery
Marketing and ABM platforms can query Cognism by seniority, job function, industry, or technology to auto-build buying committees for target accounts. Converts account-level intent signals into contact-level activation.
Give users transparent control over Cognism credits
Because PII unlocks consume credits, expose a clear preview → redeem flow in your UI so users see what they're spending before they spend it. Builds trust and reduces support tickets around credit usage.
What You Can Build
Ship these features with Truto + Cognism
Concrete product features your team can ship faster by leveraging Truto’s Cognism integration instead of building from scratch.
Just-in-time phone and email unlocking
Show a preview with hasPhone/hasEmail flags from search, then call the redeem endpoint on click to spend a credit and reveal the verified mobile or email.
Domain-to-account enrichment for inbound forms
Accept an email address, resolve the company via account enrichment and redeem, and auto-populate revenue, employee count, industry, and location for routing rules.
Advanced prospecting search with native filters
Build a filter UI backed by Cognism's technologies, seniority, job functions, industries, regions, countries, company sizes, and NAICS/SIC/ISIC code lookups to let users compose precise ICP queries.
Compliance guard for dialers and sending engines
Batch-check contacts against Cognism's opt-out registry before outreach and automatically suppress any hit, with per-record audit logs for GDPR defensibility.
Match-score-gated CRM enrichment jobs
Run scheduled enrichment on CRM records using LinkedIn URL or name + domain, and only write back data when Cognism's matchScore exceeds your quality threshold (27 for contacts, 35 for accounts).
Credit and entitlement dashboards
Surface each user's remaining Cognism contact and account subscription entitlements inside your app so admins can monitor consumption without leaving your product.
SuperAI
Cognism 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_cognism_industry_codes
List industry codes in Cognism's dictionaries — SIC, NAICS, and ISIC codes mapped to industries. Returns the paginated code records with classification, code, label, and industry. classification is optional; when provided it must be one of sic, naics, isic.
list_all_cognism_technologies
List technologies from the Cognism technology dictionary. Filter with name (case-insensitive substring match). Returns the paginated envelope: data (array of technology records) and page (limit, nextCursor, hasMore in cursor mode; offset, total in offset mode). Max 100 per page, default 50; cursor and offset are mutually exclusive.
list_all_cognism_search_companies
Search Cognism companies by attribute, location, event (funding, acquisition, hiring, IPO), and intent filters. Returns one page of company records, each identified by its Cognism company UUID (uuid) plus the record's upstream attributes. Filter via the company and options body; options.sortFields (headcount or revenue) applies only with offset pagination. Max 100 per page. Costs one search token per row returned, regardless of view; an empty result page costs no tokens. Company searches never consume credits. Through Truto's proxy list API, pass the filter as query params (Truto moves them into the request body), e.g. company[name][include][]=Acme. Caveat (unverified live): Truto also moves `view` into the body, where Cognism may ignore it, so requested view segments might not be returned.
cognism_search_companies_count
Count the Cognism companies matching a company filter without retrieving records. Returns: total. Accepts the same company and options filter body as the companies search. Costs one search token per call, regardless of the total returned.
list_all_cognism_search_persons
Search Cognism persons by posting a structured person, company, and/or options filter. Returns one page of person records — redeemUuid/personUuid plus the segments selected via view (demographics, contacts, education, pastCompanies, skills, events). Max 100 per page; view=contacts reveals email addresses and phone numbers and costs one credit per record returned. Costs one search token per row returned, regardless of view; an empty result page costs no tokens. Through Truto's proxy list API, pass the filter as query params (Truto moves them into the request body), e.g. company[name][include][]=Acme. Caveat (unverified live): Truto also moves `view` into the body, where Cognism may ignore it, so requested view segments might not be returned.
cognism_search_persons_count
Count the Cognism persons matching a person and/or company filter without retrieving the records. Returns: total. Uses the same filter body as the person search. Costs one search token per call, regardless of the total returned.
list_all_cognism_countries
List countries from the Cognism dictionaries. Returns an unpaginated list of country records: id, name, isoAlpha2, regionId, and regionName. Optional filters: name (case-insensitive substring match) and regionId.
list_all_cognism_departments
List departments in Cognism. Returns department records ({id, name}) accepted by person and hiring-event filters, in a single unpaginated GET that costs no search tokens or credits.
list_all_cognism_industries
List industries from the Cognism dictionary. Returns industry taxonomy records with id, name, level, and parentId (links a child to its parent across the three-level taxonomy). No parameters are required.
list_all_cognism_regions
List the geographic regions available in Cognism's dictionary, used to resolve region filters (Africa, Americas, Asia, Europe, Oceania). Returns each region's id and name. Takes no parameters.
list_all_cognism_seniorities
List the seniority levels recognized by the Cognism dictionary API for use in person and hiring-event filters. Returns seniority records ({id, name}) for levels such as C-Suite, Vice President, Director, Manager, and Individual Contributor.
list_all_cognism_intent_topics
List the Bombora intent topic dictionary catalogue in Cognism. Supports filtering by name (case-insensitive substring match) and by id. Returns topic records with topicId and topicName; the catalogue returns an empty list in v1, with parameters accepted for forward compatibility.
list_all_cognism_account_intent_topics
List the intent topic IDs selected for your account in Cognism and the maximum number of topics the account may configure. Returns: topicIds, limit. No parameters required.
list_all_cognism_billing
Get the calling account's Cognism billing settings. Returns searchTokens (remaining, allotment, resetSeconds) and credits (allotment, resetSeconds). May fail with 503 when token usage cannot be read (enforcement disabled or store unavailable).
list_all_cognism_compliance_settings
Get the calling account's DNC-masking and geo-restriction compliance settings in Cognism. Returns dncRestrictedCountries (ISO alpha-2 codes where phone numbers are masked) and geoRestrictedCountries (countries excluded from search results).
list_all_cognism_personalization_settings
Get the calling account's personalization settings in Cognism. Returns intentTopics (selected intent topic ids) and technologies (watched technology names). No request parameters.
list_all_cognism_health
Check Cognism API service health with a lightweight probe. Returns an opaque health-probe payload whose fields are not documented upstream, so treat it as a liveness check rather than a data source. No required parameters; the endpoint is never rate limited.
create_a_cognism_tracked_company
Add companies to the Cognism tracked companies list so company webhooks deliver their events. Returns the full list as companyUuids. Required: companyUuids. A request that would push the list past 1,000 companies is rejected in full with 409.
delete_a_cognism_tracked_company_by_id
Remove one company from the Cognism tracked companies list by id (company UUID). Returns an empty 204 response on success. Required: id. Idempotent; removing a company stops future webhook deliveries only.
list_all_cognism_tracked_companies
List the tracked company UUIDs on the Cognism account — the companies whose events company webhooks deliver. Returns: companyUuids. The list is shared by every company webhook on the account and holds up to 1,000 companies.
Why Truto
Why use Truto’s MCP server for Cognism
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 850+ integrations.
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.
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.
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.
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.
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.
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.
For your product
Ship Cognism tools in your product
Give the AI in your product access to each customer’s own Cognism account, with one MCP server per connected account.
Rather talk it through? Book a demo
For your own team
Use Cognism in ChatGPT or Claude yourself
Connect your company’s Cognism once, then ask in the AI you already use, with exactly your own access.
From the team behind Truto · 14-day free trial
How It Works
From zero to integrated
Go live with Cognism in under an hour. No boilerplate, no maintenance burden.
Link your customer’s Cognism account
Use Truto’s frontend SDK to connect your customer’s Cognism account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
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.
Call our API, we call Cognism
Truto’s Proxy API is a 1-to-1 mapping of the Cognism API. You call us, we call Cognism, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Cognism’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Cognism on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication work when my users connect their Cognism account?
Truto handles the Cognism auth handshake and securely stores per-user credentials. Your app makes API calls through Truto using a connection ID — you never touch or persist the underlying keys.
Why do search endpoints not return emails or phone numbers directly?
Cognism gates PII behind a credit-based redeem step. Search and enrich return previews with boolean flags (hasPhone, hasEmail, hasLinkedinUrl) and identifiers; you must call cognism_contacts_redeem or cognism_accounts_redeem with those IDs to spend a credit and retrieve the actual data.
How do I know if an enrichment result is trustworthy?
Enrichment responses include a matchScore. Cognism recommends treating scores below 27 for contacts and 35 for accounts as low confidence — you can programmatically discard those before writing anything back to your users' systems.
Can I check whether a contact has opted out before sending or dialing?
Yes. Use cognism_compliance_get_opt_out_by_email or cognism_compliance_get_opt_out_by_id. A 200 response means the contact is on the opt-out list and should be suppressed; a 404 means they are safe to contact.
Can users see how many Cognism credits they have left?
Yes. cognism_entitlements_get_contact_subscription and cognism_entitlements_get_account_subscription return subscription and credit entitlement details, which you can render inside your product's admin UI.
Which filters are available for building a prospecting search UI?
Truto exposes Cognism's filter reference endpoints for technologies, management levels, company sizes, industries, job functions, regions, countries, states, SIC/ISIC/NAICS codes, skills, company types, and seniority — so you can populate dropdowns dynamically instead of hardcoding values.
From the Blog
Cognism integration guides
Deep dives, architecture guides, and practical tutorials for building Cognism integrations.
Cognism
Get Cognism integrated into your app
Our team understands what it takes to make a Cognism integration successful. A short, crisp 30 minute call with folks who understand the problem.