Documentation Index

Fetch the complete documentation index at: https://support.airtable.com/llms.txt

Use this file to discover all available pages before exploring further.

Airtable Enterprise API

Prev Next

Plan availability

Enterprise Scale plans only

Platform(s)

Web/Browser, Mac app, and Windows app

Related reading

Understanding Airtable Enterprise API

Note

Enterprise member and enterprise admin scopes are for Enterprise Scale plans only.

Airtable’s Enterprise API documentation can be accessed when logged into an Airtable account connected to an Enterprise Scale workspace. The article below is a brief overview of Airtable’s API as it specifically relates to our Enterprise customers.

  • If you or your team have development experience, then using our API can help to perform certain programmatic or bulk actions that would otherwise take tedious, repetitive, and/or manual effort to perform. In order to access and use the Enterprise API you will need:

  • The Airtable Enterprise API uses token-based authentication like Airtable's Web API. All requests should send the access token in the Authorization header. When logged into an Enterprise account, the Enterprise-related documentation is tagged with a purple "Enterprise" icon:

  • Additionally, all requests to these endpoints must be made on the server-side. Client-side requests are not allowed because they would expose the access token.

Note

Do not share your access token with anyone (including anyone at Airtable) since it's effectively a password that allows access to all your bases. If you accidentally reveal your PAT, you should regenerate your personal access token as soon as possible at https://airtable.com/create/tokens.

Using the Airtable Enterprise API

Airtable’s Admin Panel provides an interface for reviewing users, bases, and workspaces, as well as setting enterprise-wide security settings. The Enterprise API allows teams to manage their account programmatically outside of the Admin panel UI through actions like managing users, updating access permissions, and managing bases, tables, and views.

Occasionally, some teams may want to add their own metadata on top of the information pulled by an API request such as department information, managers, or billing units. This allows them to more effectively organize their enterprise resources and take action when necessary.

Airtable’s scripting extension and run a script automation action allow developers to write JavaScript code embedded within their custom application. Using this alongside the Enterprise API means developers can carry out a range of programmatic functions. Example use cases are covered in the next section below.

Example use cases

The API endpoints discussed below represent just some of the ways that our API can be used from an administrative/IT perspective.

Note

Most of the methods described above are only available to users with Enterprise admin permissions.

FAQs

Can I read account/organization-level admin panel settings (SSO config, sharing restrictions, IP allowlist, API access policies) via the Airtable API for a security posture tools?

No. Airtable's Enterprise API is designed for administering users, workspaces, bases, share links, and activity logs — it does not expose the Admin Panel's security/configuration settings (such as SSO/SAML configuration, sharing restrictions, IP allowlist, session length, or API access policies) as readable objects. A posture or asset-management tool can't currently pull those configuration values programmatically. What is available for security visibility:

  • Audit Logs API — programmatic access to a log of actions taken across enterprise workspaces and bases (user activity, object changes). Returned as JSON via API.

  • Change Events API — designed for DLP use cases; this requires enablement, so contact your account manager/account team to turn it on.

  • Enterprise API admin endpoints — you can read/manage users and share links org-wide (e.g., enumerate users, manage/disable share links), which covers some posture needs even though the settings-configuration object itself isn't exposed.

  • Manual documentation — for the configuration settings that have no API, an admin can export or screenshot them from the Admin Panel to provide to your security tooling.