PATCH /v1/jobs/{jobId}/fit-curves
Refit curves with exclusions and decisions
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.Refits the named compounds of a job after you exclude dose points, optionally switching the model, and stores each result with the exclusions and any decision (finalize, notes). This needs write access to the job.
channel and normalize choose and normalize the readouts as for POST. Each entry of updates names a compound by target.compound_label (or target.well) and is processed on its own: the response lists one { target, ok } result per entry, and ok is false for an entry with no target or one whose store failed. A compound with no readout points is still stored as an empty fit.
The same per-user rate limits as POST apply. With a project-scoped API key, a job outside the key's projects returns 404.
Request
Path parameters
Job UUID.
Request body
Example
Responses
200 OK
Response shape:
One result per entry of updates, in order
400 Bad Request
updates is missing or emptyResponse shape: object
401 Unauthorized
Response shape: object
404 Not Found
NOT_FOUND.Response shape: object
405
POST or PATCH; the Allow header says POST, PATCHResponse shape: object
429 Too Many Requests
Retry-After says how long to waitResponse shape: object
500 Internal Server Error
Response shape: object
Was this page helpful?