POST /v1/jobs/{jobId}/plate

Saves one or more wells on a job you can write to. Each update is keyed by row and col: an existing well at that position is replaced, otherwise it is created. The well name is derived from row and col when you do not send well.

If you send compound_smiles without compound_id, the SMILES is resolved to a molecule id, which is stored on the well and linked to the job. If you do not send concentration_uM, it is computed as stock_uM divided by dilution_ratio when both are present and dilution_ratio is above zero. Updates whose row or col is not a finite number are dropped.

After saving, the route refreshes the job's rollups and appends a plate-update event with the previous and new values to the job's manifest. Both steps are best effort: manifestEventWritten tells you whether the manifest event was written, and a failure in either does not fail the request. A project viewer can read a plate but not save it; saving returns 404 for them.

{
  "updates": [
    {
      "row": 1,
      "col": 1,
      "compound_smiles": "CCO",
      "stock_uM": 10000,
      "dilution_ratio": 100,
      "volume_uL": 25
    }
  ]
}

curl -X POST 'https://ivybiosciences.com/api/v1/jobs/{jobId}/plate' \
  -H "Authorization: Bearer $IVY_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
  "updates": [
    {
      "row": 1,
      "col": 1,
      "compound_smiles": "CCO",
      "stock_uM": 10000,
      "dilution_ratio": 100,
      "volume_uL": 25
    }
  ]
}'