Pipelines

Create and run a new pipeline

Defines a multi-stage pipeline inline and submits it. Each stage names a task and the tools to run for it; a stage's outputs feed the next. This is the legacy pipeline API — new integrations should use the pipelines endpoints under /api/pipelines, which separate a reusable template from a run.

post/api/submit-pipeline

Request

  • Base URL: https://app.tamarind.bio
  • URL: https://app.tamarind.bio/api/submit-pipeline
  • Auth: API key in header x-api-key

Request body

jobNamestring required

Name for this pipeline, unique within your account.

initialInputsstring[]

Inputs fed into the first stage. Required (non-empty) whenever any first-stage setting has the value "pipe", which marks the field that each initial input is substituted into; omitting it then is a 400 Missing initial inputs. Each entry is a raw sequence, or the name of a file you uploaded — .pdb/.sdf are passed through as file inputs, and a .fa/.fasta is expanded server-side into its sequences.

projectTagstring

An organization project to tag the job(s) with — its project id, or its name. Applies to the whole batch on /submit-batch, and to every job a pipeline creates on /submit-pipeline. Usually optional. It is REQUIRED when your organization has turned on "require a project tag": those accounts get 400 on any submission that does not resolve to an ORGANIZATION project (a personal project does not satisfy the policy). That 400 body carries availableProjects — the projects you may use — so you can retry without looking them up elsewhere.

Example request

{
  "projectTag": "8f1c2b64-9a3e-4c77-b0d1-4a2f6e5d8c90"
}

Response

Submitted. Body is the plain-text confirmation Pipeline {jobName} submitted to queue.

Changes

No recorded changes to this operation across all 1 revision of this API.