POST /v1/jobs/{jobId}/plate-config
Save a job's plate type
ivy_ API key (Authorization: Bearer ivy_… or X-Ivy-Api-Key), a Clerk session JWT (Authorization: Bearer …) or the Clerk __session cookie (browser sessions). See Authentication.Records the plate type (and optionally the assay use case) chosen for a job you can write to. The values are written to the plate_config entry of the provenance in the job's manifest, together with the time and the user who saved them, and the job's latest-manifest pointer is moved to the new manifest. A second call overwrites the previous plate_type_id and use_case.
plate_type_id is stored as sent; it is not checked against the plate catalogue. A project viewer cannot save; saving returns 404 for them, the same as for a job that does not exist. Only POST is served on this path.
Request
Path parameters
UUID of the job.
Request body
Plate type identifier, stored as sent.
Assay use case, stored as sent. Stored as null when omitted.
Example
Responses
200 OK
Response shape:
400 Bad Request
plate_type_id is missing or emptyResponse shape: object
401 Unauthorized
Response shape: object
404 Not Found
Response shape: object
409 Conflict
code is MANIFEST_POINTER_REFUSED)Response shape: object
429 Too Many Requests
Response shape: object
500 Internal Server Error
Response shape: object
Was this page helpful?