Developer API
Read your workspace from your own code
A small, deliberately read-only surface under /api/v1. Issue a key from your workspace, give it only the scopes it needs, and rotate it whenever you like.
Endpoints
- GET
/api/v1/authany valid keyVerify a key and read back which workspace it belongs to and which scopes it carries. The call to make first when wiring anything up.
- GET
/api/v1/workspaces/{workspaceId}workspace:readThe workspace as the key is permitted to see it.
- GET
/api/v1/workspaces/{workspaceId}/filesfiles:readFiles attached to the workspace.
Scopes
workspace:readRead the workspace record itself.
files:readRead the files attached to a workspace.
A key carries the scopes you pick at creation and no others. A call made without the required scope is refused with 403 insufficient_scope rather than returning a thinner result.
Authenticating
Send the key as a bearer token. Keys are shown once at creation and stored only as a hash, so a lost key is rotated rather than recovered.
curl https://hawiagents.com/api/v1/auth \
-H "Authorization: Bearer $HAWI_API_KEY"The surface is read-only today. There is no write endpoint, and nothing reachable with a key can move money — the API is read-only and sits inside the product, not in front of the API.
Start with one agent and one job.