Create API Box Snapshot
Starts an asynchronous build and returns the API Box Snapshot with status pending. Get the Snapshot until its status is ready, failed or canceled; API Boxes start from a ready one. The build is a Simulator build in api mode, run in real time: the built service has no simulated clock, and its scheduled work runs at the first request at or after its time. Builds queue with Simulator builds and count toward the same quotas. Send multipart/form-data with a JSON part named request, a file part named spec with the OpenAPI, WSDL or GraphQL document, and optional file parts named document with vendor documentation.
Authorizations
Use a Continuous API key. Send it in the Authorization header as a Bearer token.
Headers
Optional key for retrying this create safely. A retry with the same key and request returns the original result with its status; the same key with a different request returns 409 idempotency_conflict. Without a key, each request creates a new resource. The key is recorded before the build starts, so a retry never starts a second build.
256Body
Build options as JSON.
Vendor documentation the builder and reviewer read before they start, as repeated file parts: UTF-8 text (.md, .txt, .html, .json, .yaml, .xml, .csv) or PDF (.pdf). The documents share the request body limit with the spec.
OpenAPI, WSDL or GraphQL document, UTF-8 encoded, at most 64 MiB.
Response
Accepted
The build's latest progress report, or null before the first report. A settled Snapshot keeps its last report. A build waiting for its live credentials resumes with POST /v1/apibox-snapshots/{id}/resume.
What a ready Snapshot serves, or null.
Snapshot creation time.
Workspace credentials the build was allowed to call real systems with. Empty when none.
Why the build failed or was canceled, or null.
Limitations the Snapshot records beyond those listed in limitations.
x >= 0API Box Snapshot ID.
^abs_[0-9A-HJKMNP-TV-Z]{26}$The instructions the build followed, or empty when none were given.
Behavior the Snapshot does not serve like the real system, most important first, whether it was built or published. Empty when none.
Customer JSON metadata, or null.
Snapshot name. The ID is its identity, and names need not be unique.
128The build's research stage, or null when research did not run.
catalog for a Snapshot Continuous publishes, build for one built or published into the workspace.
catalog, build The specification the Snapshot was built from, or null until the build has read it.
openapi, wsdl, graphql, null pending while waiting for capacity; building while the build runs; ready when API Boxes can start from it; failed when the build failed; canceled when a cancel request took effect.
pending, building, ready, failed, canceled