Attio API
✓ Official Vendor SpecCRMContact Managementoauth267 EndpointsREST
For Agents
Read and write Attio CRM data — objects, attributes, records, lists, notes, and meetings — using a consistent shape across standard and custom objects.
Use for: Create a new person record in Attio, Update a deal's stage to closed-won, List all companies modified in the last 24 hours, Find a record by an attribute value
Not supported: Does not handle email sending, marketing automation, or telephony — use for CRM object, record, attribute, note, and meeting management only.
Attio is a customisable CRM built around objects, attributes, and lists rather than fixed contact and deal tables. The API exposes the full data model: standard and custom objects (people, companies, deals, custom records), the attributes that describe them, list entries, notes, meetings, and workspace members. Operations are consistent across object types, so the same shape of call manages a person record, a company record, or a custom object — making it well suited to bidirectional sync with sales, ops, and product systems.
Install Jentic One Beta
Connect the Attio API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Attio API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Attio API.
List, create, get, and update objects (people, companies, deals, custom) via /v2/objects
Manage object and list attributes through /v2/{target}/{identifier}/attributes
Create and read records and list entries to drive bidirectional CRM sync
Attach notes and meetings to records to keep activity history aligned with sales data
Manage workspace members and the SCIM schema surface for identity-aware integrations
Maintain select-option dictionaries on attributes for picklist consistency
Use Cases
Patterns agents use Attio API for, with concrete tasks.
★ Bidirectional Product to CRM Sync
Product teams want signups, plan changes, and usage milestones to land in Attio so the GTM team can act on them. The Attio API lets a sync agent map product events into person and company records via /v2/objects/{object} writes, then read CRM-side updates (deal stage, owner) back into product. The same operation shape works whether the target is a standard 'people' object or a custom 'workspaces' object.
When a product signup event fires, upsert a person record in Attio with the user's email, signup date, and plan, then write the linked company record
Sales Activity Logging
Sales reps log calls, meetings, and notes against the company or deal they relate to. The /v2/notes and /v2/meetings endpoints accept references to the parent record, so a logging agent can post both into Attio with a single call apiece. Combined with deal updates, this keeps the activity stream in Attio rich enough to drive forecast and pipeline reviews.
After a Zoom call, create an Attio meeting record linked to deal id 'deal_123' with the title, attendees, and recording URL
Custom Object Schema Management
Operations teams iterate on the Attio data model — adding attributes, renaming fields, adjusting select options. The attribute and select-option endpoints expose the schema as data, so a schema-management agent can promote changes from staging to production by reading the source workspace and applying matching writes. This avoids manual schema drift between workspaces.
Read attributes on the 'workspaces' object in workspace A and create matching attributes (with select options) in workspace B
Attio Automation via Jentic
Through Jentic, an AI agent automating Attio searches by intent ('create a person record') and Jentic returns the matching /v2/objects/{object}/records operation with its attribute schema. The Attio OAuth credentials are held in the Jentic vault, so the agent never sees the token. This makes CRM updates accessible directly from an LLM chat or scheduled workflow.
Use Jentic to search 'create an Attio person record', load the matching POST operation, and execute with the new contact's email and name
Key Endpoints
67 endpoints — attio is a customisable crm built around objects, attributes, and lists rather than fixed contact and deal tables.
METHOD
PATH
DESCRIPTION
GET
/v2/objects
List objects (standard and custom)
POST
/v2/objects
Create a custom object
GET
/v2/objects/{object}
Get a single object definition
PATCH
/v2/objects/{object}
Update an object definition
GET
/v2/{target}/{identifier}/attributes
List attributes on an object or list
POST
/v2/{target}/{identifier}/attributes
Create an attribute
GET
/v2/{target}/{identifier}/attributes/{attribute}/options
List select options for an attribute
GET
/v2/objects
List objects (standard and custom)
POST
/v2/objects
Create a custom object
GET
/v2/objects/{object}
Get a single object definition
PATCH
/v2/objects/{object}
Update an object definition
GET
/v2/{target}/{identifier}/attributes
List attributes on an object or list
POST
/v2/{target}/{identifier}/attributes
Create an attribute
GET
/v2/{target}/{identifier}/attributes/{attribute}/options
List select options for an attribute
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Attio OAuth 2.0 client credentials are stored encrypted in the Jentic vault (MAXsystem). Jentic exchanges them for a scoped bearer token at call time, so the raw secret never enters the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'create an Attio person record') and Jentic returns the matching /v2/objects/{object}/records operation with its attribute schema, so the agent posts the right shape on the first call across standard and custom objects.
Time to first call
Direct Attio integration: 1-2 days to map OAuth, the object/attribute model, and parent-record references for notes and meetings. Through Jentic: under an hour for the common record, note, and meeting flows.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Attio API through Jentic.
What authentication does the Attio API use?
The Attio API uses OAuth 2.0. Through Jentic, the OAuth credentials are held in the encrypted vault and a scoped access token is exchanged at call time, so the raw client secret never enters the agent's context.
Can I create custom objects with the Attio API?
Yes. POST /v2/objects creates a new object definition in the workspace, and the /v2/{target}/{identifier}/attributes endpoints let you add attributes (including select options) to that object. Records on the new object are then managed through the same shape as standard people and companies.
What are the rate limits for the Attio API?
Attio throttles per workspace, with limits documented in the developer portal. The spec does not encode them numerically — back off on HTTP 429 responses and prefer batched reads (filter + page) over per-id polling.
How do I attach a note to a record through Jentic?
Search Jentic for 'create an Attio note', load the POST /v2/notes operation, and execute with the parent record reference and note body. Jentic injects the OAuth bearer and validates the parent_record_id before the call hits api.attio.com.
Can I list attributes on a list as well as on an object?
Yes. The endpoint shape is /v2/{target}/{identifier}/attributes where {target} is 'objects' or 'lists', so the same call returns attributes on either, keeping a custom integration consistent across both surfaces.
Does the Attio API expose SCIM for identity provisioning?
Yes. The spec includes a SCIM schemas resource, so identity providers can read the schema definitions Attio expects when provisioning workspace members.
GET STARTED