How to Find Airtable Base ID, Get Your ID Easily 2026

From your Airtable Home screen, click into the specific base — not just any base in the account, since every base has its own distinct ID. The Home screen lists each base with the workspace it belongs to, which is useful if you manage several bases across different teams and need to confirm you're opening the right one before you go hunting for its ID.

With the base open, look at your browser's address bar. The URL contains a string starting with "app" followed by a run of letters and numbers — that's your Base ID, and you don't need to open any menu to get it. It's the fastest of the two methods, but it's easy to grab the wrong segment if you're not sure what you're looking at, since the same URL also contains table and view IDs (starting with "tbl" and "viw") right alongside it.

If you'd rather confirm the ID through Airtable's own documentation instead of parsing a URL, click the Help icon in the upper right of any screen. The dropdown groups Support, Education, and Upgrade options, and under Education you'll find API documentation — that's the link that takes you to Airtable's developer reference generated specifically for your account.

The API Reference page opens on an Introduction section describing the Airtable API in general — REST semantics, official and community client libraries, and so on. Scroll down and you'll see a line explaining that documentation is auto-generated for each of your bases, followed by a list of your workspaces and the bases inside them, each shown as a clickable card with its name and icon.

Click the card for the base you need. That opens a documentation page scoped to just that base, and its Base ID is displayed right at the top of the introduction section, ready to copy. Because this page is generated per base, it's a good way to double-check you copied the ID from the URL correctly, or to grab it in the first place if you'd rather not parse a raw address bar string.

The Base ID on its own isn't a secret — it identifies which base to talk to, but it doesn't grant access by itself. The credential that actually matters is your API key or personal access token, which is what determines whether a request with that Base ID is allowed to read or write anything. Keep the two together in whatever environment variables or secrets manager your integration uses, and avoid pasting either directly into shared documents or public code.