Attio APIConnect Attio without building on its API
Attio has a public REST API with webhooks. Any developer can register an app in Attio's developer console. A single workspace can use an API key from the app's developer settings; only workspace admins can grant workspace-level tokens. If you're reading the docs because you need Attio to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show the job on a screenshare or describe it in chat, and it runs across Attio and your other tools.
The differenceBuilding on the Attio API gets you one connection your team then maintains. Caddi runs the whole job across Attio and every tool it touches, including the screens with no API, and keeps it running when fields change.
- APIREST (JSON)
- AuthOAuth 2.0 or API key
- AccessSelf-serve
What the Attio API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 or a workspace API key (bearer token)
- Who can get access
- Any developer can register an app in Attio's developer console. A single workspace can use an API key from the app's developer settings; only workspace admins can grant workspace-level tokens.
- What it covers
- Objects, records, lists and list entries, plus webhooks.
- Limits
- 100 read requests and 25 write requests per second; the list records and list entries endpoints also use score-based limits over a 10-second sliding window.
Official docs: docs.attio.com. Checked October 2026. Vendors change access terms, so confirm with Attio before you build.
Building on the Attio API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Attio credentials, and manage tokens and refreshes. | Connect your Attio account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Attio task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Attio work off someone's desk, the build is the slow part.
What teams usually want the Attio API for
Meeting note write-back
Caddi turns each meeting into a note on the right Attio record, with follow-up tasks for the owner.
Inbox triage to CRM
Caddi reads inbound email, identifies the person and company, and updates the Attio record and list stage.
Signed-deal handoff
When an agreement is signed, Caddi moves the Attio deal to won, files the document and starts onboarding.
Attio API questions
Does Attio have an API?
Yes. Attio has a public REST API with webhooks, authenticated with OAuth 2.0 or a workspace API key (bearer token). The official documentation is at https://docs.attio.com/rest-api/overview.
How do I get access to the Attio API?
Any developer can register an app in Attio's developer console. A single workspace can use an API key from the app's developer settings; only workspace admins can grant workspace-level tokens.
Does the Attio API have rate limits?
100 read requests and 25 write requests per second; the list records and list entries endpoints also use score-based limits over a 10-second sliding window.
Can I connect Attio to my other tools without writing code against its API?
Yes. With Caddi you show the Attio task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Attio and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Attio with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Attio is reviewed before it runs in production, and every run is logged.
Connect Attio without the build.
Drop your work email and pick a time. We'll show you Caddi running your Attio workflow end to end.