Boardwise API

Boardwise has a full REST API for AI agents, integrations, and developers. You can manage meetings, documents, written consents, compliance declarations, action items, and board communications programmatically.

Full machine-readable documentation is available at https://app.boardwise.co/llms.txt. This page provides an HTML overview for developers and AI agents that summarise page content.

Authentication

Boardwise uses a device authorization flow — the same pattern used by GitHub CLI and similar tools. Your agent never handles the user's password or passkeys.

Step 1 — Request a device code

POST https://app.boardwise.co/api/v1/auth/device
Content-Type: application/json

{
  "client_name": "Your Agent Name"
}

Returns device_code, user_code (formatted as XXXX-XXXX), verification_uri, expires_in, and interval.

Step 2 — Ask the user to approve

Display the user_code and verification_uri to the user. Ask them to open the URL and enter the code. They approve using their existing Boardwise account.

Step 3 — Poll for the token

POST https://app.boardwise.co/api/v1/auth/device/token
Content-Type: application/json

{
  "device_code": "..."
}

Poll at the returned interval (seconds). Responses:

Waiting: {"error": "authorization_pending"}
Approved: {"access_token": "bw_...", "token_type": "Bearer"}
Denied or expired: error response

Step 4 — Use the token

Authorization: Bearer bw_...

Add this header to all API requests. Verify it works with:

GET https://app.boardwise.co/api/v1/auth/me

The token provides the same access as the user's account. Users can revoke tokens at any time from My Stuff > API Tokens.

Discovering Available Tools

Rather than documenting a fixed set of endpoints, Boardwise exposes a dynamic tool discovery endpoint. Call it after authenticating to get a complete, up-to-date list of everything the API can do:

GET https://app.boardwise.co/api/v1/tools
Authorization: Bearer bw_...

Returns a {"tools": [...]} array. Each tool has:

name — machine identifier, e.g. list_meetings, create_meeting
description — what the tool does
endpoint — HTTP method and path, e.g. GET /{organization_slug}/meetings.json
parameters — array with name, type, required, and description

Replace {organization_slug} in paths with the user's 6-digit organization slug (returned by /api/v1/auth/me).

What You Can Do

The API covers all core Boardwise functionality. The full tool list is returned dynamically by /api/v1/tools, but key areas include:

Meetings

List meetings, view agendas and attendees, create new meetings, add agenda items. Meetings progress through Draft, Announced, Published, and Locked states.

Documents

List accessible documents in the board library. Retrieve document metadata including who has viewed each file.

Written Consents

Create and manage board resolutions for out-of-meeting approval. Each signed consent is authenticated via passkey and generates a SHA-256 integrity digest for the audit record.

People and Roles

List the organization directory. View board and committee members with their roles and group memberships.

Action Items

List and create tasks. Filter by status, group, or assignee. Items carry forward automatically across meetings.

Messages

List and send messages to boards and committees. Messages are isolated from personal email — all communication stays within the platform.

Groups

List and view boards and committees with their members and roles.

Notes for AI Agents

All endpoints use .json suffix and return JSON responses.
The same permission system as the web UI applies — the agent can only access what the authenticated user can access.
Organization slug is a 6-digit identifier returned in the /api/v1/auth/me response.
Use /api/v1/tools to discover endpoints rather than hard-coding paths — the tool list is kept current as the API evolves.
Full machine-readable documentation: https://app.boardwise.co/llms.txt