Resume Snapshot build
Resumes a build that waits at QA because its live credentials were rejected, as build.waiting reports. Refresh each credential it names with PATCH /v1/credentials/ first: QA then runs again with their current values, and the build goes on to finalize. Returns the Snapshot, still building. The wait does not count toward the build’s time limit: the build resumes with the time it had left when it began waiting. A build that is not waiting returns 409 simulator_not_waiting.
Authorizations
Use a Continuous API key. Send it in the Authorization header as a Bearer token.
Path Parameters
API Box Snapshot ID.
^abs_[0-9A-HJKMNP-TV-Z]{26}$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