The REST API, API clients, and webhooks — What you can call

The API reaches everything in a workspace. Endpoints, with the scope each needs: • Meta — GET /meta (any scope): the workspace a token opens, its scopes, and expiry. • Members — GET /members (read): every member's person id, name, and role — the ids People fields store. It lists no email addresses, deliberately: a People write accepts a member's address instead. • Tables — GET /tables (read) lists every table with its fields and field keys; POST /tables (schema) creates a table and optional starting fields; PATCH /tables/{tableId} (schema) renames one (its slug and field keys stay stable). • Fields — POST /tables/{tableId}/fields (schema) adds a field; PATCH /fields/{fieldId} (schema) renames a field or edits a Select/MultiSelect's options. A field's key never changes; Relation fields need a relatedTableId, and computed Lookup and Rollup fields can't be created through the API.