Get Run Inputs
uid is used for all the endpoints and Run manipulation.The id is an internal identifier returned to smooth and improve speed and accuracy if you have questions about your runs you will want
to submit to the team.Overview
TheGET /runs/{run_uid}/inputs endpoint returns the complete list of inputs associated with a run, including their execution status and any associated errors. This endpoint is essential for recovering detailed input-level results and errors, especially when webhook callbacks are missed or need to be verified.
Pagination
This endpoint uses cursor-based pagination by default. Follow theX-Pagination-Next response header to retrieve subsequent pages.
limitcontrols the page size (default: 100, max: 500).- The
X-Pagination-Nextheader contains the full URL for the next page, includinglimitandcursor. - When the
X-Pagination-Nextheader is absent, there are no more pages.
Authorizations
Path Parameters
Run UUID
Query Parameters
Number of inputs to return
1 <= x <= 500(deprecated) Number of inputs to skip for pagination
x >= 0(optional) Cursor value obtained from the X-Pagination-Next response header of a previous request, used to continue pagination. If not provided, the first page will be returned.
Response
Returns the run inputs
Unique identifier for the input.
Current status of the input.
CREATED, QUEUED, SCHEDULED, RUNNING, BLOCKED, FAILED, SUCCEEDED, STOPPED Input payload.
Custom metadata or additional information.
Information about the last execution attempt.
Information about the last execution attempt.
Number of outputs generated by the input.
Number of retry attempts for the input.
Timestamp when the input started.
Timestamp when the input finished.
Timestamp when the input was created.
Timestamp when the input was last updated.

