> ## Documentation Index > Fetch the complete documentation index at: https://docs.stardex.com/llms.txt > Use this file to discover all available pages before exploring further. # List pipeline stages > Retrieve all candidate pipeline stages for the team, including Stardex stage categories (`is_rejection_stage`, `is_interviewing_stage`, `is_offer_stage`, `is_placement_stage`). Use the returned `id` values when filtering persons by pipeline stage or moving candidates with POST /v1/candidates/update-stage. Stages are returned in display order (`stage_order` ascending). This is the team-level catalog; a job's ordered stages also appear on GET /v1/jobs/{id}. ## OpenAPI ````yaml /api-reference/openapi-v1.json get /v1/jobs/pipeline-stages openapi: 3.1.0 info: title: Stardex API (v1) version: 1.0.0 description: >- Stardex ATS API — manage candidates, jobs, companies, and recruiting workflows. servers: - url: https://api.stardex.ai description: Production API server security: - bearerAuth: [] tags: - name: Persons description: Manage person records — contacts, work history, and custom fields. - name: Jobs description: Manage job postings — pipeline stages, team members, and custom fields. - name: Candidates description: Manage candidate records and pipeline stage transitions. - name: Companies description: Browse and retrieve company records. - name: Lists description: Create, search, and retrieve saved person and company lists. - name: Person Activities description: Create and manage activity records (notes, emails, meetings) for persons. - name: Team Members description: List team members for use in search filters and assignments. - name: Custom Fields description: Retrieve custom field definitions and tag options for search filters. paths: /v1/jobs/pipeline-stages: get: tags: - Jobs summary: List pipeline stages description: >- Retrieve all candidate pipeline stages for the team, including Stardex stage categories (`is_rejection_stage`, `is_interviewing_stage`, `is_offer_stage`, `is_placement_stage`). Use the returned `id` values when filtering persons by pipeline stage or moving candidates with POST /v1/candidates/update-stage. Stages are returned in display order (`stage_order` ascending). This is the team-level catalog; a job's ordered stages also appear on GET /v1/jobs/{id}. operationId: listPipelineStages responses: '200': description: Pipeline stages fetched content: application/json: schema: $ref: '#/components/schemas/PipelineStagesResponse' example: success: true data: - id: 345e6789-e01b-23c4-d567-890123456789 name: Application Review stage_order: 1 is_rejection_stage: false is_interviewing_stage: false is_offer_stage: false is_placement_stage: false - id: 456e7890-f12b-34d5-e678-901234567890 name: Phone Screen stage_order: 2 is_rejection_stage: false is_interviewing_stage: true is_offer_stage: false is_placement_stage: false - id: 567e8901-e23c-45d6-e789-012345678901 name: Technical Interview stage_order: 3 is_rejection_stage: false is_interviewing_stage: true is_offer_stage: false is_placement_stage: false - id: 678e9012-f34d-56e7-f890-123456789012 name: Offer stage_order: 4 is_rejection_stage: false is_interviewing_stage: false is_offer_stage: true is_placement_stage: false - id: 789e0123-a45b-67c8-d901-234567890123 name: Rejected stage_order: 5 is_rejection_stage: true is_interviewing_stage: false is_offer_stage: false is_placement_stage: false meta: total: 5 offset: 0 limit: 5 '400': description: Validation error content: application/json: schema: type: object properties: success: type: boolean enum: - false description: Always false for error responses. error: type: object properties: code: type: string description: >- Machine-readable error code (e.g. "VALIDATION_ERROR", "NOT_FOUND"). message: type: string description: Human-readable error description. required: - code - message required: - success - error '404': description: Resource not found content: application/json: schema: type: object properties: success: type: boolean enum: - false description: Always false for error responses. error: type: object properties: code: type: string description: >- Machine-readable error code (e.g. "VALIDATION_ERROR", "NOT_FOUND"). message: type: string description: Human-readable error description. required: - code - message required: - success - error '500': description: Internal server error content: application/json: schema: type: object properties: success: type: boolean enum: - false description: Always false for error responses. error: type: object properties: code: type: string description: >- Machine-readable error code (e.g. "VALIDATION_ERROR", "NOT_FOUND"). message: type: string description: Human-readable error description. required: - code - message required: - success - error components: schemas: PipelineStagesResponse: type: object properties: success: type: boolean enum: - true data: type: array items: $ref: '#/components/schemas/PipelineStage' meta: type: object properties: total: type: number description: Total matching records across all pages. offset: type: number description: Current pagination offset. limit: type: number description: Page size used for this request. required: - total - offset - limit required: - success - data - meta PipelineStage: type: object properties: id: type: string description: >- Pipeline stage UUID. Use in pipeline_stage_ids_included/excluded filters in POST /v1/persons/search, or as stage_id in POST /v1/candidates/update-stage. name: type: string description: >- Stage display name (e.g. "Application Review", "Technical Interview"). stage_order: type: number description: >- Position in the pipeline (1 = first stage). Stages are ordered ascending. is_rejection_stage: type: boolean description: True if this stage represents rejection/disqualification. is_interviewing_stage: type: boolean description: True if this stage represents an interview round. is_offer_stage: type: boolean description: True if this stage represents an offer. is_placement_stage: type: boolean description: True if this stage represents a placement (candidate hired). required: - id - name - stage_order - is_rejection_stage - is_interviewing_stage - is_offer_stage - is_placement_stage securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- Authenticate with a Bearer token: API key, OAuth token, or session token. ````