Developer-friendly & type-safe JS/TS SDK based on the official OpenAPI spec of Attio.
Attio API: Attio is a CRM platform which is highly customisable, incredibly powerful and data-driven. The public API allows you to manipulate records, lists, notes, tasks and more. You can find more information about the Attio API in the official docs. Unfortunately, an official JavaScript or TypeScript SDK has not been released yet. In the meantime, we maintain this unofficial SDK to bridge the gap until an official SDK becomes available.
The SDK can be installed with either npm, pnpm, bun or yarn package managers.
npm add attio-js
pnpm add attio-js
bun add attio-js
yarn add attio-js zod
# Note that Yarn does not install peer dependencies automatically. You will need
# to install zod as shown above.
Note
This package is published with CommonJS and ES Modules (ESM) support.
For supported JavaScript runtimes, please consult RUNTIMES.md.
import { Attio } from "attio-js";
const attio = new Attio({
apiKey: process.env["ATTIO_API_KEY"] ?? "",
});
async function run() {
const result = await attio.objects.list();
// Handle the result
console.log(result);
}
run();
This SDK supports the following security scheme globally:
Name | Type | Scheme | Environment Variable |
---|---|---|---|
apiKey |
http | HTTP Bearer | ATTIO_API_KEY |
To authenticate with the API the apiKey
parameter must be set when initializing the SDK client instance. For example:
import { Attio } from "attio-js";
const attio = new Attio({
apiKey: process.env["ATTIO_API_KEY"] ?? "",
});
async function run() {
const result = await attio.objects.list();
// Handle the result
console.log(result);
}
run();
Available methods
- list - List attributes
- create - Create an attribute
- get - Get an attribute
- update - Update an attribute
- listSelectOptions - List select options
- createSelectOption - Create a select option
- updateOption - Update a select option
- listStatuses - List statuses
- query - List entries
- create - Create an entry (add record to list)
- assert - Assert a list entry by parent
- getEntry - Get a list entry
- update - Update a list entry (append multiselect values)
- overwrite - Update a list entry (overwrite multiselect values)
- delete - Delete a list entry
- list - List attribute values for a list entry
- identify - Identify
- list - List objects
- create - Create an object
- get - Get an object
- partialUpdate - Update an object
- query - List records
- create - Create a record
- assert - Assert a record
- get - Get a record
- partialUpdate - Update a record (append multiselect values)
- update - Update a record (overwrite multiselect values)
- delete - Delete a record
- listAttributeValues - List record attribute values
- listEntries - List record entries
- list - List tasks
- create - Create a task
- get - Get a task
- update - Update a task
- delete - Delete a task
- list - List webhooks
- create - Create a webhook
- get - Get a webhook
- partialUpdate - Update a webhook
- delete - Delete a webhook
All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.
To read more about standalone functions, check FUNCTIONS.md.
Available standalone functions
attributesCreate
- Create an attributeattributesCreateSelectOption
- Create a select optionattributesGet
- Get an attributeattributesList
- List attributesattributesListSelectOptions
- List select optionsattributesListStatuses
- List statusesattributesStatusesCreate
- Create a statusattributesStatusesUpdate
- Update a statusattributesUpdate
- Update an attributeattributesUpdateOption
- Update a select optioncommentsCreate
- Create a commentcommentsDelete
- Delete a commentcommentsGet
- Get a commententriesAssert
- Assert a list entry by parententriesAttributesValuesList
- List attribute values for a list entryentriesCreate
- Create an entry (add record to list)entriesDelete
- Delete a list entryentriesGetEntry
- Get a list entryentriesOverwrite
- Update a list entry (overwrite multiselect values)entriesQuery
- List entriesentriesUpdate
- Update a list entry (append multiselect values)listsCreate
- Create a listlistsGet
- Get a listlistsListAll
- List all listslistsUpdate
- Update a listmetaIdentify
- IdentifynotesCreate
- Create a notenotesDelete
- Delete a notenotesGet
- Get a notenotesList
- List notesobjectsCreate
- Create an objectobjectsGet
- Get an objectobjectsList
- List objectsobjectsPartialUpdate
- Update an objectrecordsAssert
- Assert a recordrecordsCreate
- Create a recordrecordsDelete
- Delete a recordrecordsGet
- Get a recordrecordsListAttributeValues
- List record attribute valuesrecordsListEntries
- List record entriesrecordsPartialUpdate
- Update a record (append multiselect values)recordsQuery
- List recordsrecordsUpdate
- Update a record (overwrite multiselect values)tasksCreate
- Create a tasktasksDelete
- Delete a tasktasksGet
- Get a tasktasksList
- List taskstasksUpdate
- Update a taskthreadsGet
- Get a threadthreadsList
- List threadswebhooksCreate
- Create a webhookwebhooksDelete
- Delete a webhookwebhooksGet
- Get a webhookwebhooksList
- List webhookswebhooksPartialUpdate
- Update a webhookworkspaceMembersGet
- Get a workspace memberworkspaceMembersList
- List workspace members
Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.
To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:
import { Attio } from "attio-js";
const attio = new Attio({
apiKey: process.env["ATTIO_API_KEY"] ?? "",
});
async function run() {
const result = await attio.objects.list({
retries: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
});
// Handle the result
console.log(result);
}
run();
If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:
import { Attio } from "attio-js";
const attio = new Attio({
retryConfig: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
apiKey: process.env["ATTIO_API_KEY"] ?? "",
});
async function run() {
const result = await attio.objects.list();
// Handle the result
console.log(result);
}
run();
Some methods specify known errors which can be thrown. All the known errors are enumerated in the models/errors/errors.ts
module. The known errors for a method are documented under the Errors tables in SDK docs. For example, the create
method may throw the following errors:
Error Type | Status Code | Content Type |
---|---|---|
errors.PostV2ObjectsSlugConflictError | 409 | application/json |
errors.APIError | 4XX, 5XX | */* |
If the method throws an error and it is not captured by the known errors, it will default to throwing a APIError
.
import { Attio } from "attio-js";
import { PostV2ObjectsSlugConflictError } from "attio-js/models/errors/getv2objectsobject.js";
import { SDKValidationError } from "attio-js/models/errors/sdkvalidationerror.js";
const attio = new Attio({
apiKey: process.env["ATTIO_API_KEY"] ?? "",
});
async function run() {
let result;
try {
result = await attio.objects.create({
data: {
apiSlug: "people",
singularNoun: "Person",
pluralNoun: "People",
},
});
// Handle the result
console.log(result);
} catch (err) {
switch (true) {
// The server response does not match the expected SDK schema
case (err instanceof SDKValidationError): {
// Pretty-print will provide a human-readable multi-line error message
console.error(err.pretty());
// Raw value may also be inspected
console.error(err.rawValue);
return;
}
case (err instanceof PostV2ObjectsSlugConflictError): {
// Handle err.data$: PostV2ObjectsSlugConflictErrorData
console.error(err);
return;
}
default: {
// Other errors such as network errors, see HTTPClientErrors for more details
throw err;
}
}
}
}
run();
Validation errors can also occur when either method arguments or data returned from the server do not match the expected format. The SDKValidationError
that is thrown as a result will capture the raw value that failed validation in an attribute called rawValue
. Additionally, a pretty()
method is available on this error that can be used to log a nicely formatted multi-line string since validation errors can list many issues and the plain error string may be difficult read when debugging.
In some rare cases, the SDK can fail to get a response from the server or even make the request due to unexpected circumstances such as network conditions. These types of errors are captured in the models/errors/httpclienterrors.ts
module:
HTTP Client Error | Description |
---|---|
RequestAbortedError | HTTP request was aborted by the client |
RequestTimeoutError | HTTP request timed out due to an AbortSignal signal |
ConnectionError | HTTP client was unable to make a request to a server |
InvalidRequestError | Any input used to create a request is invalid |
UnexpectedClientError | Unrecognised or unexpected error |
The default server can be overridden globally by passing a URL to the serverURL: string
optional parameter when initializing the SDK client instance. For example:
import { Attio } from "attio-js";
const attio = new Attio({
serverURL: "https://api.attio.com",
apiKey: process.env["ATTIO_API_KEY"] ?? "",
});
async function run() {
const result = await attio.objects.list();
// Handle the result
console.log(result);
}
run();
The TypeScript SDK makes API calls using an HTTPClient
that wraps the native
Fetch API. This
client is a thin wrapper around fetch
and provides the ability to attach hooks
around the request lifecycle that can be used to modify the request or handle
errors and response.
The HTTPClient
constructor takes an optional fetcher
argument that can be
used to integrate a third-party HTTP client or when writing tests to mock out
the HTTP client and feed in fixtures.
The following example shows how to use the "beforeRequest"
hook to to add a
custom header and a timeout to requests and how to use the "requestError"
hook
to log errors:
import { Attio } from "attio-js";
import { HTTPClient } from "attio-js/lib/http";
const httpClient = new HTTPClient({
// fetcher takes a function that has the same signature as native `fetch`.
fetcher: (request) => {
return fetch(request);
}
});
httpClient.addHook("beforeRequest", (request) => {
const nextRequest = new Request(request, {
signal: request.signal || AbortSignal.timeout(5000)
});
nextRequest.headers.set("x-custom-header", "custom value");
return nextRequest;
});
httpClient.addHook("requestError", (error, request) => {
console.group("Request Error");
console.log("Reason:", `${error}`);
console.log("Endpoint:", `${request.method} ${request.url}`);
console.groupEnd();
});
const sdk = new Attio({ httpClient });
You can setup your SDK to emit debug logs for SDK requests and responses.
You can pass a logger that matches console
's interface as an SDK option.
Warning
Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.
import { Attio } from "attio-js";
const sdk = new Attio({ debugLogger: console });
You can also enable a default debug logger by setting an environment variable ATTIO_DEBUG
to true.
This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.
While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.