Skip to content

Commit 07c9a7d

Browse files
authored
Merge pull request #393 from nocodb/docs/IDs
Docs: where to find IDs for REST APIs
2 parents e65119c + 8e54756 commit 07c9a7d

19 files changed

+106
-5
lines changed

content/docs/developer-resources/rest-apis/index.mdx

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,97 @@ Additional information on the REST APIs is provided below.
1919
- When querying using v3 apis, see [v3 Where Clause](/docs/product-docs/developer-resources/rest-apis#v3-where-query-parameter) for a slight difference between the two version's where clause.
2020

2121

22+
## Finding Your API IDs
23+
24+
Before making API calls, you'll need to identify and copy the relevant IDs required for constructing your endpoints. This section walks you through locating each essential identifier.
25+
26+
### Workspace ID
27+
28+
**Workspace ID** is an alphanumeric identifier prefixed with `w` (representing *workspace*) that uniquely identifies your workspace in NocoDB. It appears in the URL bar when viewing any base within the workspace.
29+
30+
You can also find it in the workspace context menu (accessible by clicking the workspace icon in the minibar). Click the ID to copy it to your clipboard.
31+
32+
![Workspace ID](/img/v2/developer/workspace-id-1.png)
33+
34+
Workspace ID can also be retrieved from Workspace settings page.
35+
36+
![Workspace ID](/img/v2/developer/workspace-id-2.png)
37+
38+
### Base ID
39+
40+
**Base ID** is required for metadata APIs and administrative operations. It uniquely identifies a specific database (or base) within your workspace.
41+
42+
The Base ID is an alphanumeric identifier prefixed with `p` (representing *project*), visible in the URL when accessing any table or base-level settings. You can also find it in the base context menu (chevron next to the base name) in the left sidebar, where you can click the ID to copy it to your clipboard.
43+
44+
![Base ID](/img/v2/developer/base-id.png)
45+
46+
### Table ID
47+
48+
**Table ID** is the most commonly used identifier and is required for all data API calls. It uniquely identifies a specific table within your base.
49+
50+
The Table ID is an alphanumeric string prefixed with `m` (representing *model*), visible in the URL immediately after the Base ID when viewing a table. You can also find it in the table context menu (three dots next to the table name) in the left sidebar. Click the ID to copy it to your clipboard.
51+
52+
![Table ID](/img/v2/developer/table-id.png)
53+
54+
### View ID
55+
**View ID** is used for view-specific API operations, such as fetching records from a particular view. It uniquely identifies a specific view within a table.
56+
57+
The View ID is an alphanumeric string prefixed with `v` (representing *view*), visible in the URL when a specific view is open. You can also find it in the view context menu (three dots next to the view name) in the left sidebar. Click the ID to copy it to your clipboard.
58+
59+
![View ID](/img/v2/developer/view-id-1.png)
60+
61+
View ID can also be retrieved from view toolbar > more actions (3 dots) menu
62+
63+
![View ID](/img/v2/developer/view-id-2.png)
64+
65+
### Field ID
66+
**Field ID** is used for field-specific API operations, such as updating field properties. It uniquely identifies a specific column within a table.
67+
68+
The Field ID is an alphanumeric string prefixed with `c` (representing *column*), visible in the URL when viewing or editing a field’s settings. You can also find it in the field context menu (chevron next to the field name) in the field header bar. Click the ID to copy it to your clipboard.
69+
70+
![Field ID](/img/v2/developer/field-id-1.png)
71+
72+
Field ID can also be retrieved from `Details` > `Fields` editor
73+
74+
![Field ID](/img/v2/developer/field-id-2.png)
75+
76+
77+
### Record ID
78+
**Record ID** is used for record-specific API operations, such as retrieving or updating an individual record. It uniquely identifies a specific row within a table.
79+
80+
By default, the Record ID is a numeric value starting from 1. You can display the **ID** field (which corresponds to the Record ID) by opening the **Fields** menu in the toolbar and enabling **Show System Fields**.
81+
82+
![Record ID](/img/v2/developer/record-id-1.png)
83+
84+
You can also find it in the URL when viewing a specific record (expanded record view).
85+
86+
![Record ID](/img/v2/developer/record-id-2.png)
87+
88+
You can also access the Record ID in formulas by selecting **ID** from the list of available fields in the formula editor or by using the `RECORD_ID()` function.
89+
90+
![Record ID](/img/v2/developer/record-id-3.png)
91+
92+
### User ID
93+
**User ID** is used for user-specific API operations, such as retrieving user details. It uniquely identifies a specific user within your workspace or organization.
94+
95+
The User ID is an alphanumeric string prefixed with `u` (representing *user*). You can find it on either the **Workspace Members** page or the **Base Members** page by clicking the three dots menu next to a user’s name. Click the ID to copy it to your clipboard.
96+
97+
![User ID](/img/v2/developer/user-id-1.png)
98+
99+
![User ID](/img/v2/developer/user-id-2.png)
100+
101+
### Data Source ID
102+
For external data sources connected to NocoDB (such as Postgres or MySQL), the **Data Source ID** is additionally required to perform data API operations.
103+
104+
The Data Source ID is an alphanumeric string that uniquely identifies the connected data source. You can find it in the context menu by clicking the three dots next to the data source name in the left sidebar. Click the ID to copy it to your clipboard.
105+
106+
![Data Source ID](/img/v2/developer/datasource-id-1.png)
107+
108+
You can also find it in the Data Source settings page.
109+
110+
![Data Source ID](/img/v2/developer/datasource-id-2.png)
111+
112+
22113
## Rate Limits
23114
NocoDB APIs are rate-limited to ensure fair usage and optimal performance for all users. The default rate limit is set to **5 requests per second per user**. These limits are the same across all plans.
24115

300 KB
Loading
222 KB
Loading
177 KB
Loading
143 KB
Loading
218 KB
Loading
259 KB
Loading
285 KB
Loading
58.4 KB
Loading
183 KB
Loading

0 commit comments

Comments
 (0)