- POST /aircraft/:id/draft_batches turns a visit's work items into one
unsigned entry per logbook, signed in the app (by a user with a
certificate, or a mechanic through a returned or emailed invitation link).
- The squawks they resolve and inspections they complete (with their result)
are held until every entry is signed, then applied, attributed to the last
signer; draft_batch.completed webhook. A draft never clears a squawk alone.
- Drafts are for owners (integrations act for one, drafts:write scope);
unsigned drafts can be withdrawn; lookup by external_ref.
- The signing and entry pages show where a draft came from and what signing
will do.
- The suggested recordkeeping procedures describe the API once it's in use.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Personal tokens (Profile → API tokens) act as their owner; integration
tokens (Admin → Integrations) reach chosen aircraft and scopes, and their
writes name the person they're for (SAM-On-Behalf-Of). Tokens are stored
hashed, shown once, revocable, with last use recorded.
- GET aircraft, components, due list, inspections, ADs, logbook entries and
squawks; POST/PATCH squawks with external_ref links to the other system.
- Idempotency-Key for safe retries, paging, JSON errors, rate limits.
- Record history keeps the token with each change (in the hashed payload).
- Webhooks (squawk created/updated/resolved, entry signed), HMAC-signed,
retried, never sent to the server itself; deliveries listed for admins.
- The outbound address check is shared by AirTrail and webhooks; reporting a
squawk is announced the same way from the form and the API.
- docs/guide/api.md: the API reference.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>