DEV Community

OnaEiuspkz
OnaEiuspkz

Posted on

APITable public shares extend the space permission model

APITable public shares extend the space permission model

APITable is a self-hostable API-oriented table and collaboration platform. Its permissions are attached to organizations, spaces, folders, datasheets, records, and public share links. The API is designed to act with the same permissions as the user who created the token. That makes the token and the share link different paths into the same data.

The self-hosted API documentation says an authenticated request has the same permissions as the corresponding user in the APITable interface. It also describes a public share ID for a node and a developer access token. A token is not automatically a tenant-wide key, and a public share is not automatically limited to read-only unless the product configuration says so.

What the measurement shows

On 2026-11-21 between 06:47 and 06:49 CST, an SDK query with sub_type=all, page 1, and page size 1 returned 293 matches for app="APITable" and 219 for title="APITable". The application count is the more product-specific signal. Both are index matches, not a confirmed list of exposed workspaces.

The query can be reviewed through the ZoomEye search link.

Map the space and node permissions

Create a matrix for each role and node type: organization member, space member, folder editor, datasheet editor, record-level permission, and API token. A user who can view a dashboard may not be able to view the underlying records. A token that can read a datasheet may be able to write through a different endpoint if the role is broader than its label.

Test public shares separately. Generate a read-only embed for a test table, open it as an anonymous user, and confirm that no hidden field or linked record is exposed. Then test a public link with write or comment behavior if the deployment supports it. Remove the link and verify that it stops resolving.

Review the API identity

API tokens are user-bound. Record the creator, scopes, spaces, nodes, expiration, and owner. Rotate a token when its user changes role. Do not place a token in a browser front end, a shared note, or a public repository. If a script needs data from one space, confirm that it cannot list every space.

The APITable API can expose records and automation actions, so response-size limits, rate limits, and audit logs matter. Log the token ID and endpoint result without recording full record bodies. Alert on unusual exports, share-link creation, and permission changes.

Harden the deployment

Put the web UI and API behind TLS. Separate the internal database and worker services from the public network. Disable the OpenAPI documentation endpoint in production unless it is intentionally public. Review integration callbacks and webhooks for outbound access to untrusted destinations.

For a discovered application, identify the owner and product edition without enumerating space IDs. APITable's public-share and token model is useful when the two paths are governed separately. The 293 application matches are a review queue, not a claim that those workspaces are accessible.

References

Top comments (0)