Skip to main content
The Inspack REST API is versioned under /api/v1 and protected by bearer tokens. See Authentication to get a key. The OpenAPI spec powering this reference is generated from the live server at:
Every endpoint below is auto-rendered from that spec — request shapes, response shapes, and example payloads stay in sync with the deployed service.

​
Conventions

  • Base URL — https://app.inspack.com
  • Auth — Authorization: Bearer <YOUR_INSPACK_API_KEY> on every request
  • Content type — application/json for request and response bodies
  • Errors — public validation errors include error and, when applicable, details; proxied backend failures preserve their original HTTP status and body.
  • Uploads — initialize → PUT → process → status; process takes an optional typed ctx (review extraction by default, inspector drafting, references, or an answer to a steering question). Customer organization comes from authentication, system tokens supply explicit org_id. PUT uses signed URLs and every returned required header, without a bearer token. Artifact GET uses authenticated portal storage. doc-parse and the old /start route are retired with HTTP 410 migration guidance.