Skip to main content
GET
List board views

Authorizations

Authorization
string
header
required

Clerk session JWT (deployments with Clerk auth) — validated per request (issuer + signature + lifetime + authorized-party). The internal Boardy tenant/member are resolved from the token's ACTIVE Clerk organization (org_id) → the Boardy tenant it maps to → this user's member in that tenant (#356). A token with no active organization is rejected; production never trusts spoofable X-Tenant-Id/X-Member-Id headers. The same normalized context backs the SPA, this OpenAPI surface, and MCP.

Path Parameters

boardId
string<uuid>
required

Response

OK

id
string<uuid>
required
tenantId
string<uuid>
required
boardId
string<uuid>
required
name
string
required
type
enum<string>
required
Available options:
Table,
Kanban,
Calendar,
Timeline
filters
string
required
sort
string
required
grouping
string
required
visibleColumns
string[]
required
workspaceId
null | string<uuid>