I'm trying to determine from the API whether a table is hidden or shown, but looking at https://airtable.com/developers/web/api/model/table-model there's no obvious field with that information. Is there another API that has it?
Solved
Get Table Hidden/Shown Status from API?
+4Best answer by Saravanan_009
As of now, Airtable's public API does not provide a direct way to determine whether a table is hidden or visible within a base's interface, as the visibility of tables is a user interface preference and not a data-level attribute exposed by the API.
The table visibility (hidden or shown) in Airtable typically refers to the user interface in the Airtable web or mobile app, and this kind of information is generally managed client-side. It isn't exposed in Airtable's REST API, Metadata API, or Web API because these are primarily focused on interacting with the data itself (records, fields, tables, views, etc.) rather than UI-specific details.
+15As of now, Airtable's public API does not provide a direct way to determine whether a table is hidden or visible within a base's interface, as the visibility of tables is a user interface preference and not a data-level attribute exposed by the API.
The table visibility (hidden or shown) in Airtable typically refers to the user interface in the Airtable web or mobile app, and this kind of information is generally managed client-side. It isn't exposed in Airtable's REST API, Metadata API, or Web API because these are primarily focused on interacting with the data itself (records, fields, tables, views, etc.) rather than UI-specific details.
+4Saravanan_009 wrote:
As of now, Airtable's public API does not provide a direct way to determine whether a table is hidden or visible within a base's interface, as the visibility of tables is a user interface preference and not a data-level attribute exposed by the API.
The table visibility (hidden or shown) in Airtable typically refers to the user interface in the Airtable web or mobile app, and this kind of information is generally managed client-side. It isn't exposed in Airtable's REST API, Metadata API, or Web API because these are primarily focused on interacting with the data itself (records, fields, tables, views, etc.) rather than UI-specific details.
Marking as accepted because you're right, but the split in API accessibility on UI attributes vs data elements is a consistent rough edge in the Airtable API, and goes against the de facto API-first design strategy in the industry over the last 10+ years.
1 person likes this
Reply
Most helpful members this week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.