Drift API v1 — Attention read surface¶
Drift exposes a deliberately small, read-only organisation-scoped API for Attention and other trusted clients.
Authentication uses an existing Drift API key:
The API key determines the organisation. Callers cannot supply another organisation ID.
Endpoints¶
Current organisation¶
GET /api/v1/organisation
Returns the stable organisation identity represented by the key.
Forms¶
GET /api/v1/forms?limit=50
Returns form identity, title, status and provenance URL. It does not return responses.
Recent submissions¶
GET /api/v1/submissions?limit=30&formId=<optional>
Returns a bounded list of submission identity, form identity/title, timestamps, payment status and the field keys present in each submission.
It deliberately does not return response bodies. A client should use this broad read only to find evidence that may matter, then resolve individual submissions.
Exact submission¶
GET /api/v1/submissions/<submissionId>
Returns the full structured response for one submission after verifying that its form belongs to the API key's organisation.
This endpoint may expose sensitive form content. Clients should read exact submissions selectively and avoid copying them into another store.
Workflows¶
GET /api/v1/workflows?status=active&limit=50
Lists workflow identity and status.
Workflow instances¶
GET /api/v1/workflow-instances?status=active&limit=30
Returns bounded process-state summaries. The list exposes context keys, not full workflow context.
Exact workflow instance¶
GET /api/v1/workflow-instances/<instanceId>
Returns the exact instance context plus participant and stage-completion state after organisation scoping.
Attention semantics¶
Drift is authoritative for structured input and process state.
- A submission is evidence received through a structured process.
- A workflow instance is process state.
- Neither becomes a Tending Moment, Swells Observation or Glade commitment merely because it exists.
- Attention should list broadly and read exact records selectively.
- Drift remains canonical; Attention should not mirror responses or workflow state.
The first implementation is read-only. Workflow mutations should only be added later behind explicit Attention approval.
Remote MCP¶
The current Attention integration consumes this API directly through a narrow native read adapter so the semantic model can be tested immediately.
The intended next step is to expose the same contract through Drift remote MCP, then remove the temporary protocol bridge from Attention without changing tool semantics.