Get assignment
Retrieve retained work already assigned to this connector, without requiring an active session. The original immutable receipt is separate from current public progress. This read does not grant permission to launch or relaunch the work.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Existing assignment identity.
Responses
Section titled “Responses”Original pinned assignment and current state, including after publication or installation revocation.
Immutable original claim receipt beside current progress. No launch authority. Deliberately omit Debug because the specification contains private inputs.
object
Complete pinned specification. Inputs are private; deliberately omit Debug.
object
Pinned identities and scientific schemas checked during registration.
Contract validation checks schemas and examples, not scientific correctness. Registration does not activate a publication or verify the claimed identities.
object
Enumeray’s interpretation of schema restrictions and input/output values. This is independent of the wrapper protocol and JSON Schema dialect.
A named example validated at registration and preserved for discovery.
object
Up to eight optional diagnostics, keyed by [a-z][a-z0-9_-]{0,63}. Paths are confined to the run workspace; diagnostics are independent of results.
object
object
Internal registration snapshot used by connector configuration and execution evidence.
object
First argument is an executable path relative to release_path.
object
Identity claims derived from the retained scientific definition. They do not independently attest the provider’s installed software.
object
Model-supplied batch file relative to release_path; required for Slurm.
Immutable accepted publication and execution context.
Requirements derived from an immutable context and scientific contract. These are execution needs, not observations of backend support.
object
Execution mechanisms, independent of the wrapper’s request/result protocol.
Pinned at acceptance; omitted from historical receipts.
Delivery settlement is independent from the immutable scientific result.
object
connector accounts for normal delivery; operator_abandonment records loss.
Greatest accepted event sequence, including diagnostic-only events.
API receipt time of the latest qualifying execution observation.
API confirmation age: fresh below 60 seconds, stale at or above 60 seconds. Missing or future confirmation times are unknown.
Retained terminal result; null while work remains outstanding.
object
object
Closed immutable collection reference used by scientific inputs and results.
object
object
Closed public stored-file reference, never a path or transfer capability.
object
object
Private bounded failure details, never included in diagnostics or tracing.
object
At most 2048 UTF-8 bytes. Only tab and newline control characters allowed.
Original committed acknowledgement, independent of later inspection time.
object
True only after this result and every file pin have committed. It permits removal of provider work files, never deletion of API-retained artifacts. Historical receipts and operator resolutions carry no cleanup authority.
Public execution state. Delegated preparation and collection are running.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Query parameters are not accepted. Code bad_request.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Active connector credential required, rechecked while holding the connector lock.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Bearer
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Assignment identity is invalid, absent, or belongs to another connector. Code not_found.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
413: the request body exceeds the configured size limit.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Assignment inspection is temporarily unavailable.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
default
Section titled “default”An HTTP request failed; inspect the stable error code and request ID.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Documentation 205dcb3116ea · public sources 8c70356d340f · built .Download documentation identity.