Import archive
Reads a bundle back and returns it as a viewable report.
- Authentication
- Bearer token
- Retries
- Idempotency-Key
- Body
- multipart/form-data
- Version
- 2026-09-03
Writes nothing. It parses, verifies the checksum and signature, and returns a rendered view. That is what makes accepting a file from a user safe at all: the worst a tampered bundle can do is render its own contents back to whoever uploaded it, which is what a file viewer does by definition.
Verification failures are reported specifically - "not from this product", "edited since export", "from a different installation" are genuinely different problems with different answers, and collapsing them into "invalid file" wastes the customer's time.
Headers#
Request body#
Responses#
Errors#
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
validation_error· 422 — The payload was well-formed JSON but failed schema validation.unauthenticated· 401 — The request carried no API key, or one the API could not verify.forbidden· 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.idempotency_key_reused· 422 — This `Idempotency-Key` was used before, for a request with a different body.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-agent limit on top.
More Insights endpoints#
Something unclear or missing? Tell us and we’ll fix it.