New report2026 State of AI at Enterprise RIAs2026 State of AI at RIAsRead it freeOn demandOther eventsNext: AI for Mid-Sized Law, Nov 5
Attio APIIntegration guide

Integrate the Attio API.Caddi writes and runs the integration for you.

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.

  • 99%of agent runs complete successfully
  • ~45 minon average to build your first agent
  • 1M+back-office tasks completed
01Getting access

The connection is a project before it does anything.

Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. 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.

On your own

Register an app, store Attio credentials, refresh tokens and code around the rate limits.

With Caddi

Connect your Attio account once. Caddi holds the connection.

02The whole job

The job doesn't stop at Attio.

An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Attio API only reaches Attio.

On your own

Each extra system is another API, another set of credentials, another integration to own.

With Caddi

One automation runs across every tool the job touches, each through its API.

03After launch

Someone has to own the code.

API versions change, fields get added and your process moves.

On your own

A developer patches and redeploys the integration each time.

With Caddi

The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.

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.

When to build the Attio integration in-house

When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Attio work off someone's desk, the build is the slow part, and Caddi does it for you.

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.

Everything Caddi does with Attio.

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. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.

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.