Skip to main content

1. Get an API key

Sign in at app.inspack.com, open Settings → Integration → API keys, and generate a key. Treat it like a password.

2. Pick an inspector

Each review can run one or more inspectors you’ve configured in the portal. From Inspectors, copy the numeric ID of the inspector you want to use and pass it in inspector_ids.

3. Run a review

The response includes each inspector’s results in inspector_results and aggregated findings in summaries; you do not need a separate aggregation call. Check inspector_errors even after HTTP 200, because some or all inspectors can fail. An empty findings list with no inspector errors is a successful review with no violations. To review the same content with several inspectors, add their IDs to inspector_ids. Each request that runs inspectors costs one review credit, regardless of the number of inspectors.

Next steps

  • Review files with the upload lifecycle: initialize, PUT every slot with its exact headers, start, read status/content, then review.
  • Explore every endpoint in the API reference.
  • See the review contract and migration guide for recommendations, memory, finding operations, and migration from retired endpoints.
  • Skip the wiring and use the MCP server from Claude Desktop, Cursor, or ChatGPT.