The query a developer asks earlier than committing to a CRM API shouldn’t be whether or not it exists, however whether or not it provides you adequate management over the info mannequin, the data, and the automation layer to justify constructing on it fairly than round it.
Attio’s API is a public REST floor exchanging JSON over HTTPS, with OAuth 2.0 authentication for multi-workspace apps and API keys for single-workspace use, revealed charge limits of 100 reads/sec and 25 writes/sec, a webhook system with at-least-once supply ensures, and an endpoint catalogue spanning {custom} objects, data, lists, notes, duties, recordsdata, conferences, and name recordings.
The developer docs are public, an OpenAPI spec is downloadable, and API entry ships on each plan, together with free.
That openness shouldn’t be common within the CRM class. However scope and depth are totally different questions.
Attio’s API covers the CRM layer: creating and querying data throughout {custom} objects, managing lists and pipeline entries, subscribing to webhooks on file modifications, and orchestrating workflows. The place its scope stops is B2B information intelligence.
The API doesn’t search exterior contact databases, enrich data with verified cellphone numbers or technographics, floor purchaser intent alerts, resolve org charts, or present AI-powered account analysis. Attio’s built-in enrichment populates fundamental firmographics routinely, however no API endpoint enables you to set off enrichment on demand or question an exterior dataset.
That is the place ZoomInfo enters the image.
ZoomInfo’s Enterprise API is a REST suite masking search, enrichment, AI intelligence, and viewers administration throughout 500M contacts and 100M corporations, with an MCP server for AI-agent workflows. The 2 APIs are layers of the identical pipeline: Attio manages the CRM data and workflows, ZoomInfo supplies the intelligence that decides what goes into these data.
This assessment covers the Attio API in technical depth first (authentication, endpoints, webhooks, SDKs, charge limits, and pricing), then evaluations ZoomInfo’s API as the info and intelligence layer that picks up the place CRM file administration stops.
Attio API at a Look
|
Attribute |
Element |
|---|---|
|
API sort |
REST over HTTPS, JSON request/response |
|
Authentication |
OAuth 2.0 (multi-workspace) or API key (single-workspace), each as Bearer tokens |
|
Base URL |
https://api.attio.com (endpoints versioned beneath /v2/) |
|
Charge limits |
|
|
SDKs |
No standalone REST shopper SDK; App SDK (TypeScript/React) for embedded apps |
|
Webhooks |
Sure, occasion system with at-least-once supply and HMAC signing |
|
MCP server |
Sure, hosted at https://mcp.attio.com/mcp |
|
Documentation |
docs.attio.com (Mintlify-hosted, interactive reference, OpenAPI spec) |
|
Pricing / entry |
Bundled on all plans together with Free ($0); no separate API tier or per-call prices |
Attio API: What Works Nicely & What to Plan Round
|
What works properly |
What to plan round |
|---|---|
|
API entry on each plan, together with Free ($0) |
CRM scope solely: no exterior contact search, no enrichment endpoints, no intent alerts |
|
OAuth 2.0 with scoped permissions for multi-workspace apps |
No official REST shopper SDK in any language; you construct and preserve the HTTP layer your self |
|
100 reads/sec and 25 writes/sec are beneficiant for a CRM API |
Write charge restrict (25/sec) is agency; bulk imports want cautious orchestration |
|
Webhook supply with HMAC signing and at-least-once ensures |
Rating-based charge limits on listing/file queries add complexity past easy req/sec ceilings |
|
OpenAPI spec accessible for code era and Postman imports |
Automated enrichment has no API set off; you can not enrich a file on demand through the API |
|
Versatile information mannequin: {custom} objects, 17 attribute varieties, file references |
SQL endpoint is plan-gated; not accessible on all tiers |
Attio API: Authentication & Getting Began
Getting API entry begins with any Attio account, together with the free tier.
There isn’t a separate developer signup, no approval gate, and no enterprise-only restriction. API and webhook entry is accessible on all plans.
Attio helps two entry token varieties:
-
OAuth 2.0: The usual authorization code circulation for apps serving a number of workspaces. You register your app and handle shopper credentials on the developer dashboard (construct.attio.com). Attio implements RFC 6749, with reference endpoints for authorize, token change, and token introspection. That is the trail for constructing integrations that hook up with many Attio workspaces.
Each token varieties authenticate the identical method: a Bearer token within the Authorization header. HTTP Primary Auth additionally works (token as username, clean password), although Bearer is really helpful.
Scopes management which sources a token can learn or write. The endpoint reference lists required scopes per operation, so you possibly can create tokens with the minimal privileges your integration wants.
A fundamental authenticated request:
curl -X GET “https://api.attio.com/v2/objects/individuals/data/question”
-H “Authorization: Bearer YOUR_ACCESS_TOKEN”
-H “Content material-Kind: software/json”
-d ‘{}’
One sensible benefit: as a result of API entry ships on each plan, you possibly can prototype an integration on the free tier (3 seats, 50,000 data, 3 objects) and improve solely if you want extra capability.
Attio API: Core Endpoints & Capabilities
The API is organized round Attio’s information mannequin: objects, data, lists, and supporting sources, all beneath the /v2/ base path. Knowledge format is JSON all through.
Folks, Firms & Offers (Commonplace Objects)
Attio ships three customary objects: Folks, Firms, and Offers. Every has devoted endpoints following the sample /v2/objects/{object}/data.
Operations: Create, listing (through POST question), get, replace, upsert, and delete. The upsert operation is helpful for sync integrations: it creates a file if no match exists or updates the present one, so that you keep away from duplicate-management logic in your aspect.
Folks data settle for e-mail addresses as identifiers; firm data use domains. You possibly can append to or overwrite multiselect fields, with separate endpoints for every conduct.
Customized Objects & Generic Information
Attio’s information mannequin extends to {custom} objects (subscriptions, invoices, tasks, partnerships, or the rest what you are promoting tracks). Customized objects use the identical file endpoints as customary objects: /v2/objects/:object/data.

Supply: Attio
Operations: Create, listing, get, replace (append or overwrite multiselect values), upsert, delete, and a search endpoint for full-text search throughout any object sort.
The variety of {custom} objects is plan-gated: 3 on Free (together with Folks and Firms), 5 on Plus, 12 on Professional, and limitless on Enterprise.
What you’ll construct with this: a product-led progress pipeline that syncs workspace utilization information from Phase into {custom} Attio objects through the API, then queries data to floor accounts hitting activation thresholds for gross sales follow-up.
Lists & Entries
Lists set up data into process-specific views (pipelines, territories, marketing campaign cohorts). Lists can carry their very own attributes past these on the father or mother object.
Operations: Create, get, listing, and replace lists (/v2/lists). Full CRUD plus upsert on listing entries (/v2/lists/:listing/entries), with separate endpoints for appending vs. overwriting multiselect values.
That is the place pipeline administration lives on the API degree: transferring a deal via levels, updating pipeline-specific fields, and querying entries by standing.
Attributes
Operations: Listing, get, create, and replace attributes on objects and lists. Handle choose choices and standing choices.
Attio helps 17 attribute varieties: textual content, quantity, choose, foreign money, date, location, e-mail tackle, cellphone quantity, area, checkbox, ranking, standing, timestamp, private identify, interplay, file reference, and actor reference. The file reference sort allows relationship modeling throughout objects, which is the place Attio’s graph-based information mannequin turns into accessible via the API.
Notes, Duties & Feedback
Notes (/v2/notes): Create, listing, get, and delete notes hooked up to data.
Duties (/v2/duties): Create, listing, get, replace, and delete duties.
Feedback and Threads: Create, get, and delete feedback; listing and get remark threads.
These endpoints make Attio a collaborative workspace on the API degree. A typical integration sample: routinely create a process when a deal reaches a particular stage, or append a observe summarizing a buyer interplay from an exterior system.
Information, Conferences & Name Recordings
Information: Add, listing, obtain, get, and delete recordsdata; create folders.
Conferences (/v2/conferences): Listing and get assembly data with cursor-based pagination.
Name Recordings and Transcripts: Listing and get name recordings; retrieve full name transcripts.
The decision recording endpoints expose Attio’s Name Intelligence information via the API. In case your integration wants to tug transcript information into an exterior analytics instrument or feed dialog context into an AI workflow, these endpoints present the uncooked materials.
Meta & Identification
/v2/self: Identifies the present authenticated token and workspace. Helpful for multi-workspace integrations that want to substantiate which workspace a token belongs to earlier than making information calls.
Workspace Members: Listing and get workspace member data.
SCIM 2.0: A separate SCIM endpoint handles enterprise consumer and group provisioning, enabling automated consumer lifecycle administration via id suppliers like Okta.
Filtering, Sorting & Pagination
Pagination works in two types relying on the endpoint: restrict/offset (move restrict and offset parameters; cease when outcomes returned are fewer than restrict) and cursor-based (move restrict and cursor; obtain pagination.next_cursor within the response physique for subsequent pages).
Each GET and POST endpoints help filtering and sorting, documented in a devoted information. The filtering system helps compound situations, so you possibly can construct focused queries with out pulling complete datasets.
SQL Endpoint
A read-only SQL endpoint (/v2/sql) permits analytical queries towards workspace information.
That is helpful for reporting integrations and information warehouse syncs that must ask questions the REST endpoints weren’t designed for. This endpoint is plan-gated and never accessible on each billing tier.
Attio API: Webhooks & Occasions
Attio has a webhook system documented at docs.attio.com/rest-api/guides/webhooks. You possibly can create webhooks via the REST API (/v2/webhooks) or via the developer settings UI.
The occasion varieties cowl the CRM lifecycle:
|
Class |
Occasions |
|---|---|
|
Information |
file.created, file.up to date, file.deleted, file.merged |
|
Lists |
listing.created, listing.up to date, listing.deleted |
|
Listing entries |
list-entry.created, list-entry.up to date, list-entry.deleted |
|
Attributes |
list-attribute.created, list-attribute.up to date, object-attribute.created, object-attribute.up to date |
|
Notes |
observe.created, observe.up to date, observe.deleted, note-content.up to date |
|
Duties |
process.created, process.up to date, process.deleted |
|
Feedback |
remark.created, remark.deleted, remark.resolved, remark.unresolved |
|
Name recordings |
call-recording.created |
|
Workspace members |
workspace-member.created |
Supply conduct: Goal URLs have to be HTTPS. Attio ensures at-least-once supply, so occasional duplicates can happen.
If the server doesn’t reply with HTTP 200-299 inside 5 seconds, Attio retries as much as 10 instances with exponential backoff, totaling about 3 days earlier than it marks the webhook as degraded and sends an alert e-mail. Supply is rate-limited to 25 requests per second per goal URL; contact help to regulate.
Safety: Each supply contains an Attio-Signature header containing a SHA256 HMAC of the request physique (hex-encoded, utilizing the webhook secret). An Idempotency-Key header is included for deduplication. Collectively, these offer you a stable basis for constructing dependable, tamper-resistant occasion customers.
Filtering: Webhook subscriptions help server-side filtering through $and/$or guidelines concentrating on payload fields with dot notation. Operators are equals and not_equals. This allows you to subscribe to modifications on a particular listing or object with out receiving occasions for your complete workspace.
What you’ll construct with this: a real-time sync pipeline that listens for file.up to date occasions in your Offers object, pushes stage modifications to Slack, updates your information warehouse, and triggers downstream workflows in an exterior automation instrument, all with out polling.
Attio API: SDKs, Docs & Charge Limits
SDKs & Libraries
Attio doesn’t publish a standalone REST API shopper library for any programming language. Builders name the REST API instantly over HTTP.
The Attio App SDK exists however serves a special goal: it’s a TypeScript/React framework for constructing apps that run contained in the Attio interface (file widgets, bulk actions, settings panels, {custom} workflow blocks). It’s not a REST API shopper. You submit apps constructed with the SDK via the developer dashboard and distribute them through the Attio App Retailer.
Attio additionally operates a hosted MCP server at https://mcp.attio.com/mcp, exposing about 30 structured instruments masking data, lists, notes, duties, feedback, emails, conferences, name recordings, workspace administration, reporting, and SQL.

Supply: Attio
Supported MCP shoppers embody Claude Desktop, Claude.ai, ChatGPT, Cursor, and any MCP-compatible AI instrument. Authentication is OAuth (no API keys required for MCP).
No standalone REST shopper means you personal the auth layer, request serialization, error dealing with, and rate-limit backoff logic. The OpenAPI spec helps: you possibly can generate typed shoppers in your language of alternative utilizing customary code-generation instruments.
Documentation & Developer Expertise
Attio’s developer documentation lives at docs.attio.com, constructed on Mintlify. It’s structured into 5 sections: Docs (overview and OAuth reference), App SDK, REST API, MCP, and SQL.
The REST API documentation contains:
-
Guides: Authentication, charge limiting, filtering/sorting, and pagination walkthroughs
-
Endpoint reference: Particular person pages per operation, organized by useful resource, with request/response examples
An OpenAPI spec is obtainable for Postman imports, API shopper imports, and code era. An interactive API explorer is accessible from the endpoint reference pages. An in-docs AI assistant (“Ask Assistant”) is embedded on each documentation web page.
The developer dashboard at construct.attio.com manages app creation, OAuth shopper configuration, webhook settings, API key era, and App Retailer submission.
A public changelog is maintained at attio.com/changelog, and an engineering weblog at attio.com/engineering/weblog covers technical deep dives. The API is on v2; v1 webhook endpoints are deprecated.
Developer help runs via the Attio Assist Middle and speak to kind. Precedence help is obtainable on Professional and Enterprise plans. No devoted developer Discord or neighborhood discussion board is linked from the developer docs.
The documentation is thorough, well-organized, and usable with out signing in. The OpenAPI spec and interactive explorer offer you two quick paths to confirming response shapes earlier than writing code. One hole: no downloadable Postman assortment ships instantly, although the OpenAPI spec will be imported into Postman.
Charge Limits & Constraints
The revealed charge limits are:
Charge-limited responses return HTTP 429 with a Retry-After header (a date/time indicating when the restrict resets, usually the following clock second) and a JSON physique containing “sort”: “rate_limit_error” and “code”: “rate_limit_exceeded”. Attio might also briefly decrease limits on particular endpoints throughout incident response.
Rating-based limits on listing and file queries: The Listing data and Listing entries endpoints carry further complexity-based charge limits. Every question will get a rating based mostly on its filters, types, and the full file/entry depend for the queried object/listing. Limits fireplace in two methods:
Each situations return HTTP 429 with a Retry-After header. This scoring system means easy queries towards small datasets are unlikely to hit limits, however complicated filtered queries towards massive objects can exhaust the finances quicker than the headline req/sec numbers recommend.
MCP server charge limits are enforced individually per workspace:
|
Tier |
Restrict |
|---|---|
|
Learn instruments |
100 req/sec |
|
Write instruments |
25 req/sec |
|
Search instruments |
300 req/min |
|
Semantic search instruments |
2 req/sec |
|
Reporting / SQL instruments |
2 req/sec |
Webhook supply is individually rate-limited to 25 deliveries per second per goal URL.
Attio API Pricing & Entry Prices
Attio bundles API and webhook entry on all plans, together with the free tier.
There isn’t a separate API pricing, no per-call metering for traditional REST API utilization, and no API-specific credit score system. The App SDK and MCP server are additionally accessible throughout all plans.
What every plan provides you on the API degree:
-
Free ($0): 3 seats, 50,000 data, 3 objects, API and webhook entry
-
Plus ($29/consumer/month annual, $36 month-to-month): No seat restrict, 250,000 data, 5 objects
-
Professional ($69/consumer/month annual, $86 month-to-month): 1,000,000 data, 12 objects, precedence help
-
Enterprise ({custom} pricing): Limitless objects, {custom} file limits, SSO, migration service
The SQL endpoint through MCP is an exception: it isn’t accessible on each billing plan.
Attio’s credit score system (workspace credit and seat credit) governs AI options like Ask Attio and workflow automation blocks, not REST API calls. Commonplace API calls, webhook deliveries, and MCP instrument calls are topic to charge limits however to not credit score deduction. This distinction issues: your API integration prices rely in your plan tier (which units file limits, object counts, and help degree), not on name quantity.
For a developer sizing prices: a group of 5 on the Plus plan at $29/consumer/month ($145/month complete) will get 250,000 data, 5 {custom} objects, and limitless API calls inside the charge limits. The sensible price constraint is the file ceiling and object depend, not API utilization.
The place the Attio API Falls Brief
These are sensible limits a developer constructing on the Attio API ought to plan round. A number of are scope choices that mirror what Attio is (a CRM) and what it isn’t.
No exterior information search or enrichment endpoints. The API manages data inside Attio. It doesn’t search exterior B2B databases, uncover new contacts, resolve org charts, detect purchaser intent, or enrich data with technographics, funding information, or verified direct-dial cellphone numbers.
Attio’s built-in enrichment populates fundamental firmographic fields routinely, however no API endpoint triggers enrichment on demand or queries a dataset past the workspace. In case your pipeline must determine who to place into the CRM, not simply handle who’s already there, you want a second API.
No standalone REST shopper SDK. The App SDK is a framework for embedded apps, not a REST shopper. Each integration is uncooked HTTP. The OpenAPI spec allows code era, which partially compensates, however you continue to personal the auth layer, retry logic, and error dealing with.
Write charge restrict is agency at 25 req/sec. For bulk imports or migrations, 25 writes per second is an actual constraint. A 100,000-record sync at that ceiling takes at minimal 67 minutes of sustained writes, assuming no errors or retries. The upsert endpoint reduces the necessity for read-before-write patterns, however high-volume write workloads require cautious orchestration.
Rating-based question limits add unpredictability. The complexity-scoring system on listing and file queries means your efficient throughput is determined by question form, not simply name quantity. A manufacturing integration operating frequent complicated queries towards massive objects could hit charge limits properly earlier than the headline 100 reads/sec.
No AI or intelligence endpoints. The REST API exposes no AI capabilities. Ask Attio, AI classification, AI summarization, and the analysis agent can be found within the UI and thru workflows, however not as API endpoints. In case your integration wants AI-powered information processing, you deal with that exterior Attio.
Restricted native integrations for outbound information. Whereas Attio’s App Retailer lists 100+ integrations, the API itself doesn’t push information to exterior techniques. Occasion-driven integrations rely upon webhooks, which ship reliably however don’t embody a documented payload signing rotation coverage.
ZoomInfo API: The B2B Intelligence Layer Past CRM
Attio’s API tells you handle the data in your CRM.
ZoomInfo’s API tells you what needs to be in these data, who’s price contacting, and which accounts are actively in-market.
The 2 APIs sit at totally different layers of a knowledge pipeline. A developer constructing a CRM-powered go-to-market workflow would use Attio’s API to handle the pipeline and ZoomInfo’s API to gas it with verified contacts, firm intelligence, and shopping for alerts. With ZoomInfo Agent Groups, a sign like a job change can kick off the total play, from analysis to outreach, fairly than ending as a process within the CRM.
That intelligence runs via ZoomInfo’s GTM Context Graph, which processes 1.5B+ information factors every day by combining ZoomInfo’s B2B information together with your first-party information to indicate why offers transfer or stall.

What the API Covers
ZoomInfo’s Enterprise API is a REST suite served from https://api.zoominfo.com/gtm, organized into 4 areas documented within the interactive API reference:
-
Knowledge API (Search & Enrich): Search endpoints cowl Contacts, Firms, Intent, Information, and Scoops, returning matched data with out consuming credit. Enrich endpoints unlock the total payload: enterprise emails, direct dials, employment historical past, company hierarchy, org charts, technographics, and hashtag alerts (as much as 25 data per name).
The underlying dataset spans 500M contacts, 100M corporations, 135M+ verified cellphone numbers, and 200M+ verified enterprise e-mail addresses.

The pairing with a CRM API is direct: use ZoomInfo’s search endpoints to search out contacts matching your ICP (free, no credit consumed), enrich those price pursuing, then push them into Attio through its file create/upsert endpoints. The search-then-enrich sample means you filter freely and pay just for the data you decide to.
Authentication & Entry
ZoomInfo makes use of OAuth 2.0 with PKCE through Okta, supporting three flows: Authorization Code with PKCE (internet purposes), Shopper Credentials (server-to-server), and Refresh Token.
Entry tokens are 24-hour Bearer tokens with rotating refresh tokens. Groups register purposes via the ZoomInfo Developer Portal, the place they generate credentials, outline scopes, and take a look at endpoints.

Each Attio and ZoomInfo use OAuth 2.0, which simplifies the combination layer: a developer constructing a pipeline between the 2 APIs works with the identical authentication mannequin on either side.
Charge Limits, Credit & Developer Expertise
Charge limits are revealed by tier: Builder (5 req/sec), Commonplace (25 req/sec), and Scaling (35 req/sec), with per-hour and per-day sliding-window limits enforced concurrently. Each response contains quota headers with remaining capability, and 429 responses embody a Retry-After header with actual backoff timing.

Supply: ZoomInfo
Credit observe a rolling 12-month window: enriching a file for the primary time consumes one credit score; re-enriching the identical file inside the 12 months is free. Search and lookup operations are free and don’t devour credit.
For builders constructing AI brokers, ZoomInfo’s MCP server at https://mcp.zoominfo.com/mcp exposes search, enrich, and account analysis as native instruments for MCP-compatible assistants, at the moment supporting Claude and ChatGPT. Agent Groups builds on that very same information layer, operating full GTM performs finish to finish: coordinated specialist brokers share every account’s context and act inside the approvals and limits you set, fairly than stopping at a single enrichment name.

Supply: ZoomInfo
Each Attio and ZoomInfo now provide MCP servers, that means an AI agent can question each CRM information and B2B intelligence via a single protocol.
Documentation lives at docs.zoominfo.com with an interactive API reference, OAuth recipes in 5 languages, and an llms.txt index for AI growth instruments. ZoomInfo doesn’t publish official SDKs both, so each platforms require direct HTTP integration. ZoomInfo makes use of consumption-based pricing (custom-quoted) and has added API entry to all related plans.
BDO Canada reported an 87% discount in time spent updating inner information dashboards utilizing the ZoomInfo API, with one analyst calling the combination plug-and-play throughout any course of. (ZoomInfo)
Closing Verdict
Attio’s API is a well-documented, brazenly accessible REST floor that offers builders programmatic management over a versatile CRM information mannequin.
OAuth 2.0 with scoped permissions, webhook supply with HMAC signing, an OpenAPI spec for code era, and API entry on each plan (together with free) make it a developer-friendly basis for CRM integrations. The information mannequin, with {custom} objects, 17 attribute varieties, and file references, means you possibly can mannequin what you are promoting in Attio fairly than forcing what you are promoting into a hard and fast schema.
Select the Attio API if your construct is CRM-first: managing contacts, corporations, offers, pipelines, and {custom} objects programmatically, syncing information from product analytics or billing techniques into CRM data, and reacting to file modifications through webhooks. For groups constructing on a contemporary CRM with a clear API floor, Attio delivers what its UI does, with out the UI.
Select the ZoomInfo API when the construct must transcend file administration into who these contacts are, which corporations are price pursuing, and whether or not accounts are actively in-market. The search-then-enrich sample (search is free, enrich consumes credit) and the AI intelligence endpoints present the info and reasoning that CRM APIs don’t.
Discover the ZoomInfo Enterprise API or begin with the developer docs to see the endpoint floor for your self.
A developer who wants neither API ought to know that Attio’s API doesn’t present B2B intelligence, and ZoomInfo’s API doesn’t handle CRM data or pipelines. In case your pipeline wants each, the 2 are complementary layers: ZoomInfo discovers and enriches, Attio manages and orchestrates.
FAQ
Is the Attio API free?
API entry is included on all Attio plans, together with the everlasting Free plan ($0). There aren’t any per-call prices and no API-specific credit score prices.
The Free plan contains 3 seats, 50,000 data, and three objects. The sensible limits are file counts and object counts, not API utilization. Paid plans begin at $29/consumer/month (annual) for Plus, which raises the file ceiling to 250,000 and provides options like Name Intelligence and Ask Attio.
Does Attio have a GraphQL API?
Not as a public REST various. Attio exposes a REST API (v2) that communicates over HTTPS with JSON request and response our bodies. The App SDK features a GraphQL interface for querying workspace information from inside embedded apps, however that’s scoped to the App SDK context, not a general-purpose GraphQL endpoint for exterior integrations.
What’s the Attio API charge restrict?
Learn requests are restricted to 100 per second, and write requests to 25 per second. Charge-limited responses return HTTP 429 with a Retry-After header.
Past these headline limits, the Listing data and Listing entries endpoints carry further complexity-based scoring: every question will get a rating based mostly on filters, types, and dataset measurement, and cumulative scores are tracked on a 10-second sliding window shared throughout all tokens. Easy queries are unlikely to hit rating limits, however complicated filtered queries towards massive objects can.
Are there official Attio SDKs?
Attio doesn’t publish a standalone REST shopper SDK in any programming language. The App SDK is a TypeScript/React framework for constructing embedded apps that run contained in the Attio UI, not a REST API shopper. Builders combine with the REST API instantly over HTTP. The downloadable OpenAPI spec enables you to generate typed shoppers in your language of alternative utilizing customary code-generation instruments.
Does the Attio API help webhooks?
Sure. Attio has a webhook system manageable via the REST API or the developer settings UI. Occasion varieties cowl data, lists, listing entries, attributes, notes, duties, feedback, name recordings, and workspace members. Supply ensures are at-least-once, with retries as much as 10 instances over about 3 days.
Each payload contains an HMAC signature for verification and an idempotency key for deduplication. Server-side filtering through $and/$or guidelines enables you to subscribe to particular objects or lists with out receiving all workspace occasions.
What does ZoomInfo’s API add to an Attio construct?
ZoomInfo’s API provides the B2B intelligence layer that Attio’s API doesn’t cowl.
The place Attio’s API manages CRM data, ZoomInfo’s API supplies the info that determines what belongs in these data: search throughout 500M contacts and 100M corporations, enrich with verified emails, direct dials, org charts, technographics, and employment historical past, detect purchaser intent alerts, and generate AI-powered account analysis and buying-committee suggestions.
The combination sample is simple: use ZoomInfo’s search endpoints to search out contacts matching your ICP (free, no credit consumed), enrich the matches, then use Attio’s file create or upsert endpoints to push them into your CRM. Each APIs help OAuth 2.0 and each provide MCP servers, so an AI agent can question each via a single protocol.