Skip to main content
GET
List the runs your team started
A run is listed when a team member started it, in the Dashboard, through an agent or with an API key, on any tool: the team’s own or a public one.
  • Every member sees every run the team started, whoever started it.
  • Filter by integration, status, source and time range, or find one run by its ID.
  • Runs stay listed for 90 days.
  • To follow a run you just started, use jobs.get with its job ID. Use this list to look back over the team’s runs.
  • Callers: an MCP OAuth token or a Dashboard session.
  • Permission: jobs:read.
  • Effect: Changes nothing.
  • Errors: business_account_required, and the errors any request can get.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

integration_id
string

an integration ID: int_ and 32 lowercase hex digits

Example:

"int_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190"

status
enum<string>
Available options:
queued,
running,
needs_input,
succeeded,
failed,
cancelled
source
enum<string>

mcp: an agent over MCP signed in with OAuth. dashboard: a member in the Dashboard. api: an API key, an MCP connection that uses one, or OAuth on the API

Available options:
mcp,
api,
dashboard
from
string

Accepted at or after, inclusive (default and earliest: 90 days ago)

to
string

Accepted before (default: now)

run_id
string

a job ID: job_ and 32 lowercase hex digits

Example:

"job_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190"

page
string

The page to read, from 1 (default 1)

limit
string

Runs per page, 1 to 100 (default 20)

Response

One page of the team's runs

data
object[]
required
page
integer
required

a non-negative number

Required range: x >= 0
limit
integer
required

a non-negative number

Required range: x >= 0
total
integer
required

Runs matching the filters, on every page

Required range: x >= 0
summary
object
required