v1
latestOpenAPI 3.0.42026-08-04342835917.6 KBRetrieves a flow by its ID.
Path parameters
The ID of the flow to retrieve.
Response
OK
The unique identifier of the flow.
The name of the flow.
The ID of the campaign associated with this flow.
The total number of items that have been added to this flow. Incremented atomically on each item creation.
Target average response count per completed item. Enables PID-based automatic rate control when set. Null disables PID.
PID proportional gain. Controls how strongly the rate reacts to the current error between target and actual response counts.
PID integral gain. Eliminates steady-state error by accumulating error over time. Includes anti-windup clamping.
PID derivative gain. Provides damping by reacting to the rate of change of the error, helping prevent overshoot.
Constant offset added to the PID output before clamping, shifting the controller's operating point so the P/I/D terms trim around a non-zero baseline.
Minimum sessions per minute the PID controller can set. Prevents the rate from dropping to zero.
Maximum sessions per minute the PID controller can set. Prevents the rate from exceeding infrastructure capacity.
Maximum time in seconds a user has to submit an answer after loading the task. Null uses the system-wide default.
Grace period in seconds after an item stops receiving new serves, allowing in-flight responses to complete.
Ratio of serves to responses used to calculate how many tasks to serve per expected response.
The comparison instruction shown to annotators during ranking tasks (e.g. "Which image is sharper?").
The initial Elo rating assigned to new items entering the ranking. Standard default is 1200.
Minimum number of responses a ranking item must receive before it is considered sufficiently evaluated.
Maximum number of responses a ranking item can receive before being removed from active ranking. Null allows unlimited responses.
Number of accepted responses per rapid at which to stop serving. Null defaults to MaxResponses.
The ID of the customer who owns the flow.
The email of the customer who owns the flow.
The id of the organization that owns the entity.
The timestamp when the flow was created.