Sessions

Chat does not expose a public widget session API like Importer. There is no POST /api/v1/sessions for the embed to start or complete. Operational counts for the workspace are available to secret keys and the dashboard Sessions page.

GET /api/v1/usage

Authenticate with Authorization: Bearer and a secret key (bsw_test_sec_ / bsw_live_sec_). Response is wrapped as { "data": ... }. Counts are scoped to the key's workspace and environment. They are operational information, not a metered invoice line. They never include message body or file bytes. Do not treat usage as a content export.

curl -s https://chat.bootstrapware.co/api/v1/usage \
  -H "Authorization: Bearer $BSW_SECRET"

Dashboard Sessions

The platform Sessions page lists usage metadata and Hosted attachment bytes vs cap. That is how you see the freeze approaching. It is not a message search.

Hosted content is separate

On Hosted ($19.99), Bootstrapware stores messages and files. That content path uses the publishable Hosted conversation routes and the dashboard inbox, not usage counts and not MCP. BYO adapters keep messages on your backend entirely.

MCP configures apps only. Never send message body or file bytes through MCP tools.

Related: API overview · Webhooks · Attachments · API keys