Create Private View Documentation

POST/views

Required Tokens

Field	Type	Required	Description
Bearer	Authorization: Bearer <token>	Optional	Your user token.
Organization token	x-Organization-Token	Optional	Run Authorize Organization in the Authorization folder.

Creates a view visible only to the calling user. Identical to Create View apart from isPrivate: true.

Two things differ from a shared create and are easy to get wrong:

index is 1, not "next in the strip." Private views are their own 1-based sequence. If the table already has three shared views, the first private view is still index: 1.
isDefault: true does not demote the shared default. One shared default and one private default per user coexist. On load the user's private default wins for them, and nobody else's view of the table changes.

Verify with Get Views: the response contains the shared views plus this one with isPrivate: true, and the pre-existing shared default still shows isDefault: true.

The Bearer token must be a user token. An API key has no acting user and is rejected with 400 A private view requires a signed-in user.

Cross-user check (needs two accounts)

Scope is only meaningful if a second user cannot see it. Run this request as user A, then re-authenticate as user B and confirm:

Get Views for the same tableId omits A's private view entirely.
Get View with A's view id returns 404 for B, not 403.
Update View and Delete View with A's view id also return 404 for B, so PUT never confirms the id exists.

Response

Returns 201 Created with an empty body.