POST /v1/jobs/{jobId}/fit-curves
Fit dose-response curves for a job
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.Fits 4PL or 5PL dose-response curves to the plate readouts of a job, one fit per compound label, and returns them. The readouts of the chosen channel are optionally normalized first (normalize). With model set to auto, each compound gets whichever of 4PL and 5PL the fit statistics prefer.
By default nothing is stored. With persist set to true the fits are also saved for the job, which needs write access to it, and the job's rollups are refreshed on a best-effort basis. Persisting failures are not reported: the response is still 200. Without persist read access is enough.
The response carries X-Elapsed-Ms and X-Model-Mode headers. Requests are rate limited per user: 3 per second, 8 per 3 seconds and 8 per minute. With a project-scoped API key, a job outside the key's projects returns 404.
Request
Path parameters
Job UUID.
Request body
Readout channel to fit
auto picks 4PL or 5PL per compound from the fit statistics
Also store the fits for the job; needs write access to it
Example
Responses
200 OK
Response shape:
400 Bad Request
Response 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?