PUT /api/fleets/{fleetId}/session-operations/{operationId}/receipt

Record the actual native session outcome#

Listed permission codes are alternatives, not token scopes. The service also checks access to the requested records and rejects stale revisions or controller generations.

• Authentication, envelopes and pagination
• Language-neutral client examples

Path parameters#

object; fields below; unknown fields rejected

Validation#

check.object({ fleetId: check.identifier, operationId: check.identifier })

Referenced definitions:

• object
• identifier

Query parameters#

custom validation: none ; see function below

Query parameters are URL text. The validation function below specifies their format, defaults and combinations. Pagination applies only to operations that use it.

Additional checks#

The following checks apply in addition to the field limits.

Constraint on value:

export function none(input: unknown) {
    const parsed = listQuery([])(input);
    return parsed.ok ? success({}) : parsed;
}

Validation#

query.none

Referenced definitions:

• none

Request body#

object; fields below; unknown fields rejected; constraint: Invalid session receipt ( runtimeReceipt )

Additional checks#

The following checks apply in addition to the field limits.

Constraint on object:

value => (value.status === 'failed') === (value.errorMessage !== null)

Validation#

fleetRuntime.runtimeReceipt

Referenced definitions:

• runtimeReceipt

Response data#

object; fields below; unknown fields rejected ( recorded )

Validation#

res.recorded

Referenced definitions:

• recorded

Response envelope#

A successful JSON response contains data and meta. Replace the data placeholder below with the response fields described above. Errors contain error instead of data.

{
  "data": "<value matching the response-data validator>",
  "meta": {
    "requestId": "00000000-0000-0000-0000-000000000001"
  }
}