List jobs

Most jobs to return on one page. A page can hold fewer, so use startKey to tell when you are done.

The startKey from the previous response. Pass it back to get the next page; the last page has none.

A batch name. Returns one page of the batch's jobs; follow startKey for the rest.

List the jobs filed under one project: its ProjectId, as returned by GET /api/projects/list. Newest first, paged with limit (default 1000) and startKey exactly like the plain listing, and answered in the list-page shape with ProjectJobSummary rows, plus projectId echoing the requested id: a response WITHOUT it did not filter by project. A pipeline run has JobStatus: null and a pipelineRunId; move it by sending that as jobId to PUT /api/updateJobProject. Cannot be combined with jobName, batch, jobEmail, organization, batchOnly, includeSubjobs or includeSequences, and repeating it with two different values is refused: both are a 400. A project that does not exist and one you cannot see are the same 404. With projectId, error bodies are {"error": "..."} rather than application/problem+json: a missing or invalid key is a 401 {"error": "Unauthorized"}; a browser session refused by an organization policy such as required MFA is a 403 {"error": "...", "code": "..."}; cursor is refused (page with startKey). An EMPTY or whitespace-only projectId is refused with a 400 in EITHER error shape ({"error": "..."} or the Jobs service's application/problem+json), so branch on the status, not the body; a misspelling such as projectid or project_id is a problem+json 400.