th {
    text-align: left;
}

:not(pre) > code {
    padding: 0.125rem;
}

.mermaid-inline button {
    width: 100%;
    display: flex;
    justify-content: center;
    align-items: center;
}

.mermaid-inline button > a {
    width: 100%;
}

img[alt~="logo"] {
    width: 90px;
}

.rounded-xl {
    border-radius: 10px;
}

.rounded-2xl {
    border-radius: 10px;
}

#navbar div > a[href="/sdk/introduction"] {
    position: relative;
}

#navbar div > a[href="/sdk/introduction"]::after {
    content: "Alpha";
    display: inline-block;
    font-size: 0.7rem;
    font-weight: 600;
    color: #0066ff;
    background-color: rgba(0, 102, 255, 0.1);
    padding: 0.1rem 0.4rem;
    border-radius: 4px;
    margin-left: 0.5rem;
}

#navigation-items > ul > li > a[href="/sdk/introduction"] {
    position: relative;
}

#navigation-items > ul > li > a[href="/sdk/introduction"]::after {
    content: "Alpha";
    display: inline-block;
    font-size: 0.7rem;
    font-weight: 600;
    color: #0066ff;
    background-color: rgba(0, 102, 255, 0.1);
    padding: 0.1rem 0.4rem;
    border-radius: 4px;
    margin-left: 0.5rem;
}


Lists all attributes defined on a specific object or list. Attributes are returned in the order that they are sorted by in the UI.

Required scopes: `object_configuration:read`.

List attributes

Rating

A unique slug for the attribute for use in API responses and URLs. Formatted in snake case.

The default value for this attribute. Static values are used to directly populate values using their contents. Dynamic values are used to lookup data at the point of creation. For example, you could use a dynamic value to insert a value for the currently logged in user. Which default values are available is dependent on the type of the attribute.

A UUID to identify the object or list that this attribute belongs to

A UUID representing the workspace this attribute belongs to.

Whether this attribute has been archived. Archived attributes are hidden from most UI, but can be restored either over the API or in workspace settings. See the [guide on archiving and deleting](/docs/archiving-vs-deleting)for more information.

Whether this attribute has a default value enabled. Must be `true` when `is_required` is `true`.

Whether or not this attribute can have multiple values. Multiselect is only available on some value types.

When `is_required` is `true`, new records/entries must have a value for this attribute. If `false`, values may be `null`. This value does not affect existing data and you do not need to backfill `null` values if changing `is_required` from `false` to `true`.

`true` if this is an Attio system-defined attribute, `false` if defined by a user or non-Attio system.

Whether or not new values for this attribute must be unique. Uniqueness restrictions are only applied to new data and do not apply retroactively to previously created data.

Whether or not this attribute can be written to. Can only be false when `is_system_attribute` is `true` (user-defined attributes are always writeable). If `false`, this usually means the attribute is enriched by Attio.

If this attribute is related to another attribute, this is an object that includes an `id` property that identifies the other attribute. `null` means no relationship exists. See [the help center](https://attio.com/help/reference/managing-your-data/attributes#relationship-attributes) for more details about relationship attributes.

A title for the attribute, to be displayed across the app.

The type of the referenced actor. [Read more information on actor types here](/docs/actors).

A boolean representing whether the checkbox is checked or not. The string values 'true' and 'false' are also accepted.

The ISO4217 currency code representing the currency that the value is stored in.

A numerical representation of the currency value. A decimal with a max of 4 decimal places.

A date represents a single calendar year, month and day, independent of timezone. If hours, months, seconds or timezones are provided, they will be trimmed. For example, "2023" and "2023-01" will be coerced into "2023-01-01", and "2023-01-02", "2023-01-02T13:00", "2023-01-02T14:00:00", "2023-01-02T15:00:00.000000000", and "2023-01-02T15:00:00.000000000+02:00" will all be coerced to "2023-01-02". If a timezone is provided that would result in a different calendar date in UTC, the date will be coerced to UTC and then the timezone component will be trimmed. For example, the value "2023-01-02T23:00:00-10:00" will be returned as "2023-01-03". The maximum date is "9999-12-31".

A slug identifying the object that the referenced record belongs to.

A UUID to identify the referenced record.

The type of interaction e.g. calendar or email.

The ISO 3166-1 alpha-2 country code for the country this location is in.

The latitude of the location. Validated by the regular expression `/^[-+]?([1-8]?\d(\.\d+)?|90(\.0+)?)$/`. Note that this value is not currently represented in the UI but will be persisted and readable through API calls.}

The first line of the address. Note that this value is not currently represented in the UI but will be persisted and readable through API calls.

The second line of the address. Note that this value is not currently represented in the UI but will be persisted and readable through API calls.

The third line of the address. Note that this value is not currently represented in the UI but will be persisted and readable through API calls.

The fourth line of the address. Note that this value is not currently represented in the UI but will be persisted and readable through API calls.

The town, neighborhood or area the location is in.

The longitude of the location. Validated by the regular expression `/^[-+]?(180(\.0+)?|((1[0-7]\d)|([1-9]?\d))(\.\d+)?)$/`

The postcode or zip code for the location. Note that this value is not currently represented in the UI but will be persisted and readable through API calls.}

The state, county, province or region that the location is in.

The ISO 3166-1 alpha-2 country code representing the country that this phone number belongs to.

The raw, original phone number, as inputted.

The UUID identifying the selected status.

A number between 0 and 5 (inclusive) to represent a star rating.

The UUID identifying the selected select option.

A raw text field. Values are limited to 10MB.

A timestamp value represents a single, universal moment in time using an ISO 8601 formatted string. This means that a timestamp consists of a date, a time (with nanosecond precision), and a time zone. Attio will coerce timestamps which do not provide full nanosecond precision and UTC is assumed if no time zone is provided. For example, "2023", "2023-01", "2023-01-02", "2023-01-02T13:00", "2023-01-02T13:00:00", and "2023-01-02T13:00:00.000000000" will all be coerced to "2023-01-02T13:00:00.000000000Z". Timestamps are always returned in UTC. For example, writing a timestamp value using the string "2023-01-02T13:00:00.000000000+02:00" will result in the value "2023-01-02T11:00:00.000000000Z" being returned. The maximum date is "9999-12-31T23:59:59.999999999Z".

A union of possible value types, as returned in response bodies.

Whether or not to archive the select option. See our [archiving guide](/docs/archiving-vs-deleting) for more information on archiving.

Whether arriving at this status triggers a celebration effect in the UI

Whether or not to archive the status. See our [archiving guide](/docs/archiving-vs-deleting) for more information on archiving.

Target time for a record to spend in given status expressed as a ISO-8601 duration string

oauth2

Attio Docs

Lists all system-defined and user-defined objects in your workspace.

Required scopes: `object_configuration:read`.

List objects

Creates a new custom object in your workspace.

Required scopes: `object_configuration:read-write`.

Create an object

Gets a single object by its `object_id` or slug.

Required scopes: `object_configuration:read`.

Get an object

Updates a single object. The object to be updated is identified by its `object_id`.

Required scopes: `object_configuration:read-write`.

Update an object

Creates a new attribute on either an object or a list.

To create an attribute on an object, you must also have the `object_configuration:read-write` scope.

To create an attribute on a list, you must also have the `list_configuration:read-write` scope.

Create an attribute

Gets information about a single attribute on either an object or a list.

Required scopes: `object_configuration:read`.

Get an attribute

Updates a single attribute on a given object or list.

Required scopes: `object_configuration:read-write`.

Update an attribute

Lists all select options for a particular attribute on either an object or a list.

Required scopes: `object_configuration:read`.

List select options

Adds a select option to a select attribute on an object or a list.

Required scopes: `object_configuration:read-write`.

Create a select option

Updates a select option on an attribute on either an object or a list.

Required scopes: `object_configuration:read-write`.

Update a select option

Lists all statuses for a particular status attribute on either an object or a list.

Required scopes: `object_configuration:read`.

List statuses

Add a new status to a status attribute on either an object or a list.

Required scopes: `object_configuration:read-write`.

Create a status

Update a status on an status attribute on either an object or a list.

Required scopes: `object_configuration:read-write`.

Update a status

Lists people, company or other records, with the option to filter and sort results.

Required scopes: `record_permission:read`, `object_configuration:read`.

List records

Use this endpoint to create or update people, companies and other records. A matching attribute is used to search for existing records. If a record is found with the same value for the matching attribute, that record will be updated. If no record with the same value for the matching attribute is found, a new record will be created instead. If you would like to avoid matching, please use the [Create record endpoint](/rest-api/endpoint-reference/records/create-a-record).

If the matching attribute is a multiselect attribute, new values will be added and existing values will not be deleted. For any other multiselect attribute, all values will be either created or deleted as necessary to match the list of supplied values.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Assert a record

Creates a new person, company or other record. This endpoint will throw on conflicts of unique attributes. If you would prefer to update records on conflicts, please use the [Assert record endpoint](/rest-api/endpoint-reference/records/assert-a-record) instead.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Create a record

Gets a single person, company or other record by its `record_id`.

Required scopes: `record_permission:read`, `object_configuration:read`.

Get a record

Use this endpoint to update people, companies, and other records by `record_id`. If the update payload includes multiselect attributes, the values supplied will overwrite/remove the list of values that already exist (if any). Use the `PATCH` endpoint to append multiselect values without removing those that already exist.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Update a record (overwrite multiselect values)

Deletes a single record (e.g. a company or person) by ID.

Required scopes: `object_configuration:read`, `record_permission:read-write`.

Delete a record

Use this endpoint to update people, companies, and other records by `record_id`. If the update payload includes multiselect attributes, the values supplied will be created and prepended to the list of values that already exist (if any). Use the `PUT` endpoint to overwrite or remove multiselect attribute values.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Update a record (append multiselect values)

Gets all values for a given attribute on a record. If the attribute is historic, this endpoint has the ability to return all historic values using the `show_historic` query param.

Required scopes: `record_permission:read`, `object_configuration:read`.

List record attribute values

List all entries, across all lists, for which this record is the parent.

Required scopes: `record_permission:read`, `object_configuration:read`, `list_entry:read`.

List record entries

List all lists that your access token has access to. lists are returned in the order that they are sorted in the sidebar.

Required scopes: `list_configuration:read`.

List all lists

Creates a new list.

Once you have your list, add attributes to it using the [Create attribute](/rest-api/endpoint-reference/attributes/create-an-attribute) API, and add records to it using the [Add records to list](/rest-api/endpoint-reference/entries/create-an-entry-add-record-to-list) API. 

New lists must specify which records can be added with the `parent_object` parameter which accepts either an object slug or an object ID. Permissions for the list are controlled with the `workspace_access` and `workspace_member_access` parameters.

Please note that new lists must have either `workspace_access` set to `"full-access"` or one or more element of `workspace_member_access` with a `"full-access"` level. It is also possible to receive a `403` billing error if your workspace is not on a plan that supports either advanced workspace or workspace member-level access for lists.

Required scopes: `list_configuration:read-write`.

Create a list

Gets a single list in your workspace that your access token has access to.

Required scopes: `list_configuration:read`.

Get a list

Updates an existing list. Permissions for the list are controlled with the `workspace_access` and `workspace_member_access` parameters. Please note that lists must have either `workspace_access` set to `"full-access"` or one or more element of `workspace_member_access` with a `"full-access"` level. It is also possible to receive a `403` billing error if your workspace is not on a plan that supports either advanced workspace or workspace member level access for lists. Changing the parent object of a list is not possible through the API as it can have unintended side-effects that should be considered carefully. If you wish to carry out a parent object change you should do so through the UI.

Required scopes: `list_configuration:read-write`.

Update a list

Lists entries in a given list, with the option to filter and sort results.

Required scopes: `list_entry:read`, `list_configuration:read`.

List entries

Use this endpoint to create or update a list entry for a given parent record. If an entry with the specified parent record is found, that entry will be updated. If no such entry is found, a new entry will be created instead. If there are multiple entries with the same parent record, this endpoint with return the "MULTIPLE_MATCH_RESULTS" error. When writing to multi-select attributes, all values will be either created or deleted as necessary to match the list of values supplied in the request body.

Required scopes: `list_entry:read-write`, `list_configuration:read`.

Assert a list entry by parent

Adds a record to a list as a new list entry. This endpoint will throw on conflicts of unique attributes. Multiple list entries are allowed for the same parent record

Required scopes: `list_entry:read-write`, `list_configuration:read`.

Create an entry (add record to list)

Gets a single list entry by its `entry_id`.

Required scopes: `list_entry:read`, `list_configuration:read`.

Get a list entry

Use this endpoint to update list entries by `entry_id`. If the update payload includes multiselect attributes, the values supplied will overwrite/remove the list of values that already exist (if any). Use the `PATCH` endpoint to add multiselect attribute values without removing those value that already exist.

Required scopes: `list_entry:read-write`, `list_configuration:read`.

Update a list entry (overwrite multiselect values)

Deletes a single list entry by its `entry_id`.

Required scopes: `list_entry:read-write`, `list_configuration:read`.

Delete a list entry

Use this endpoint to update list entries by `entry_id`. If the update payload includes multiselect attributes, the values supplied will be created and prepended to the list of values that already exist (if any). Use the `PUT` endpoint to overwrite or remove multiselect attribute values.

Required scopes: `list_entry:read-write`, `list_configuration:read`.

Update a list entry (append multiselect values)

Gets all values for a given attribute on a list entry. If the attribute is historic, this endpoint has the ability to return all historic values using the `show_historic` query param.

Required scopes: `list_entry:read`, `list_configuration:read`.

List attribute values for a list entry

Lists all workspace members in the workspace.

Required scopes: `user_management:read`.

List workspace members

Gets a single workspace member by ID.

Required scopes: `user_management:read`.

Get a workspace member

List notes for all records or for a specific record.

Required scopes: `note:read`, `object_configuration:read`, `record_permission:read`.

List notes

Creates a new note for a given record.

Required scopes: `note:read-write`, `object_configuration:read`, `record_permission:read`.

Create a note

Get a single note by ID.

Required scopes: `note:read`, `object_configuration:read`, `record_permission:read`.

Get a note

Delete a single note by ID.

Required scopes: `note:read-write`.

Delete a note

List all tasks. Results are sorted by creation date, from oldest to newest.

Required scopes: `task:read`, `object_configuration:read`, `record_permission:read`, `user_management:read`.

List tasks

Creates a new task.

At present, tasks can only be created from plaintext without record reference formatting.

Required scopes: `task:read-write`, `object_configuration:read`, `record_permission:read`, `user_management:read`.

Create a task

Get a single task by ID.

Required scopes: `task:read`, `object_configuration:read`, `record_permission:read`, `user_management:read`.

Get a task

Delete a task by ID.

Required scopes: `task:read-write`.

Delete a task

Updates an existing task by `task_id`. At present, only the `deadline_at`, `is_completed`, `linked_records`, and `assignees` fields can be updated.

Required scopes: `task:read-write`, `object_configuration:read`, `record_permission:read`, `user_management:read`.

Update a task

List threads of comments on a record or list entry.

To view threads on records, you will need the `object_configuration:read` and `record_permission:read` scopes.

To view threads on list entries, you will need the `list_configuration:read` and `list_entry:read` scopes.

Required scopes: `comment:read`.

List threads

Get all comments in a thread.

To view threads on records, you will need the `object_configuration:read` and `record_permission:read` scopes.

To view threads on list entries, you will need the `list_configuration:read` and `list_entry:read` scopes.

Required scopes: `comment:read`.

Get a thread

Creates a new comment related to an existing thread, record or entry.

To create comments on records, you will need the `object_configuration:read` and `record_permission:read` scopes.

To create comments on list entries, you will need the `list_configuration:read` and `list_entry:read` scopes.

Required scopes: `comment:read-write`.

Create a comment

Get a single comment by ID.

To view comments on records, you will need the `object_configuration:read` and `record_permission:read` scopes.

To view comments on list entries, you will need the `list_configuration:read` and `list_entry:read` scopes.

Required scopes: `comment:read`.

Get a comment

Deletes a comment by ID. If deleting a comment at the head of a thread, all messages in the thread are also deleted.

Required scopes: `comment:read-write`.

Delete a comment

Get all of the webhooks in your workspace.

Required scopes: `webhook:read`.

List webhooks

Create a webhook and associated subscriptions.

Required scopes: `webhook:read-write`.

Create a webhook

Get a single webhook.

Required scopes: `webhook:read`.

Get a webhook

Delete a webhook by ID.

Required scopes: `webhook:read-write`.

Delete a webhook

Update a webhook and associated subscriptions.

Required scopes: `webhook:read-write`.

Update a webhook

Identify the current access token, the workspace it is linked to, and any permissions it has.

Identify

Lists person records, with the option to filter and sort results.

Required scopes: `record_permission:read`, `object_configuration:read`.

List person records 

Use this endpoint to create or update person records, using a unique attribute to search for existing People (for example the `email_addresses` attribute). If a person is found with the same value for the matching attribute, that person will be updated. If no person with the same value for the matching attribute is found, a new person will be created instead. If you would like to avoid matching, please use the Create person endpoint.


If the matching attribute is a multiselect attribute, new values will be added and existing values will not be deleted. For any other multiselect attribute, all values will be either created or deleted as necessary to match the list of supplied values.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Assert a person Record

Creates a new person Record. This endpoint will throw on conflicts of unique attributes, like `email_addresses`. If you would prefer to update person records on conflicts, please use the Assert person record endpoint instead. Please note, the `avatar_url` attribute cannot currently be set via the API.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Create a person Record

Gets a single person record by its `record_id`.

Required scopes: `record_permission:read`, `object_configuration:read`.

Get a person Record

Deletes a single person record by ID.

Required scopes: `object_configuration:read`, `record_permission:read-write`.

Delete a person Record

Use this endpoint to update person records by `record_id`. If the update payload includes multiselect attributes, the values supplied will be created and prepended to the list of values that already exist (if any). Use the [Assert person endpoint](/reference/put_v2-objects-people-records) to overwrite or remove multiselect attribute values. Please note, the `avatar_url` attribute cannot currently be updated via the API.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Update a person Record

Gets all values for a given attribute on a person Record. If the attribute is historic, this endpoint has the ability to return all historic values using the `show_historic` query param.

Required scopes: `record_permission:read`, `object_configuration:read`.

List person record attribute values

List all entries, across all lists, for which this person record is the parent.

Required scopes: `record_permission:read`, `object_configuration:read`, `list_entry:read`.

List person record entries

Lists company records, with the option to filter and sort results.

Required scopes: `record_permission:read`, `object_configuration:read`.

List company records

Use this endpoint to create or update company records, using a unique attribute to search for existing companies (for example, the `domains` attribute). If a company is found with the same value for the matching attribute, that company will be updated. If no company with the same value for the matching attribute is found, a new company will be created instead. If you would like to avoid matching, please use the Create company endpoint.


If the matching attribute is a multiselect attribute, new values will be added and existing values will not be deleted. For any other multiselect attribute, all values will be either created or deleted as necessary to match the list of supplied values.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Assert a company record

Creates a new company record. This endpoint will throw on conflicts of unique attributes, like `domains`. If you would prefer to update company records on conflicts, please use the Assert company record endpoint instead. Please note, the `logo_url` attribute cannot currently be set via the API.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Create a company record

Gets a single company record by its `record_id`.

Required scopes: `record_permission:read`, `object_configuration:read`.

Get a company record

Deletes a single company record by ID.

Required scopes: `object_configuration:read`, `record_permission:read-write`.

Delete a company record

Use this endpoint to update company records by `record_id`. If the update payload includes multiselect attributes, the values supplied will be created and prepended to the list of values that already exist (if any). Use the [Assert company endpoint](/rest-api/endpoint-reference/standard-objects/companies/assert-a-company-record) to overwrite or remove multiselect attribute values. Please note, the `logo_url` attribute cannot currently be updated via the API.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Update a company record

Gets all values for a given attribute on a company record. If the attribute is historic, this endpoint has the ability to return all historic values using the `show_historic` query param.

Required scopes: `record_permission:read`, `object_configuration:read`.

List company record attribute values

List all entries, across all lists, for which this company record is the parent.

Required scopes: `record_permission:read`, `object_configuration:read`, `list_entry:read`.

List company record entries

Lists user records, with the option to filter and sort results.

Required scopes: `record_permission:read`, `object_configuration:read`.

List user records

Use this endpoint to create or update user records, using a unique attribute to search for existing users (for example the `primary_email_address` attribute). If a user is found with the same value for the matching attribute, that user will be updated, otherwise a new user will be created instead. If the matching attribute is a multiselect attribute, new values will be added and existing values will not be deleted. For any other multiselect attribute, all values will be either created or deleted as necessary to match the list of supplied values.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Assert a user record

Creates a new user record. This endpoint will throw on conflicts of unique attributes, like `primary_email_address`. If you would prefer to update user records on conflicts, please use the Assert user record endpoint instead. Please note, the `avatar_url` attribute cannot currently be set via the API.

Required scopes: `record_permission:read-write`, `object_configuration:read`.

Create a user record

Gets a single user record by its `record_id`.

Required scopes: `record_permission:read`, `object_configuration:read`.

Introduction

How-to guides

Tutorials

Endpoint reference

List attributes

Authorizations

Path Parameters

Query Parameters

Response