/jobs

Lists jobs.

Sending any of team_id, team, or schema as an empty value (e.g. schema=) behaves exactly like omitting that parameter — this gateway does not forward empty query-string values to the backend.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string

Legacy alias for team_id, kept for existing integrations. New integrations should use team_id instead. Same format: one or more team IDs, as a comma-separated list (e.g. 123,456). Ignored if team_id is also supplied with a real value — see team_id above.

string

The maximum number of jobs to return in a single response. Defaults to 30. Must be a whole number between 1 and 2200 — a limit outside that range is rejected with a 400. Use offset to page through large result sets.

string

One or more team IDs to filter jobs by, as a comma-separated list (e.g. 123,456). Preferred over the legacy team parameter below — if both are supplied with a real value, team_id takes precedence.

Omit both team_id and team to return jobs across every team you have access to. Sending team_id as an empty value does not override a populated team — an empty value is treated the same as not sending it at all, so team would still apply. Leave team_id out of the request entirely if you mean "no team filter" while still sending team.

string

The number of jobs to skip before returning results, used for pagination. Defaults to 0. To page through all jobs, increment offset by limit on each request (e.g. limit=50&offset=0, then limit=50&offset=50, ...) until a page returns fewer than limit results.

string

Set to summary for an abbreviated job object.

Omit this parameter entirely for the full job object — do not send it as an empty value (schema=) or any value other than summary; both are rejected with a 400.

Responses

400

400 response

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json