---
title: "Get Multiple Pipelines By Pipeline IDs"
method: POST
path: "/v1/pipeline/multi-query"
tags: ["Talent", "Jobs"]
---

# Get Multiple Pipelines By Pipeline IDs

`POST /v1/pipeline/multi-query`

Returns details about the specified pipelines.

## Headers

- `RequestId` string, uuid — The unique request identifier used to correlate request data with log entries and events, formatted as a UUID.
- `FrontOfficeTenantId` integer
- `Tenant` string

## Request body

- IntegerSchema[]

## Response `200`

A list of talent pipeline details.

- TalentPipeline[]
  - `talentId` integer — The identifier for the pipelined talent.
  - `jobId` integer — The identifier for the job.
  - `source` integer — The identifier for the source.
  - `pipelineStage` string — The current pipeline stage for the talent for a specific job.
  - `pipelinedDate` string, date-time — The date the talent was pipelined for a job. The field follows the YYYY-MM-DDTHH:mm:ss.sssZ format for UTC time. For example, 2024-12-01T14:30:00.546Z.
  - `pipelinedUser` integer — The identifier for the user that added the talent to the pipeline stage for a job.
  - `nominatedDate` string, date-time — The date when the talent was nominated for a job. The field follows the YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss formats and also supports fractional seconds, such as YYYY-MM-DDTHH:mm:ss.sss. For example, 2024-12-01, 2024-12-01T14:30:00, and 2024-12-01T14:30:00.546.
  - `declinedDate` string, date-time — The date when the nomination was declined. The field follows the YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss formats and also supports fractional seconds, such as YYYY-MM-DDTHH:mm:ss.sss. For example, 2024-12-01, 2024-12-01T14:30:00, and 2024-12-01T14:30:00.546.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Access Denied
- `404` — Not found
- `405` — Unsupported method
- `406` — Unsupported format(s) indicated by Accept header
- `415` — Unsupported format(s) indicated by the Content-Type header
- `429` — Too many requests
- `500` — An unexpected error occurred
- `502` — Service Unavailable
- `504` — Gateway Timeout

---

[API](https://skmtc.net/avionte/apis/aviont-partner-authorization-api.md) · [All operations](https://skmtc.net/avionte/apis/aviont-partner-authorization-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/avionte/aviont-partner-authorization-api/versions/846b33e4e71b/schema)
