---
title: "Get Custom Pipeline Status"
method: GET
path: "/api/v1/custom_processors/{lookup_key}"
tags: ["Custom Processors"]
---

# Get Custom Pipeline Status

`GET /api/v1/custom_processors/{lookup_key}`

Check the status of a custom processor generation request using the request_check_url from the initial submission.

## Path parameters

- `lookup_key` string, required

## Cookies

- `wos-session` string
- `datalab_active_team` string

## Response `200`

Successful Response

- CustomProcessorStatusResponse — Response schema for checking the status of a custom processor request.
  - `status` string, required — Current status: 'processing', 'completed', or 'failed'
  - `processor_id` string, nullable — Unique ID for executing this processor (format: cp_XXXXX). Only available when status='completed' and success=True.
  - `request_description` string, nullable — Request description (from active version)
  - `sent_at` string, required — ISO timestamp when request was submitted
  - `success` boolean, nullable — Whether generation succeeded
  - `error_message` string, nullable — Error message if failed
  - `runtime` number, nullable — Execution time in seconds
  - `completed_at` string, nullable — ISO timestamp when request completed
  - `pipeline_params` object, nullable — Active version pipeline parameters
  - `pipeline_id` string, nullable — Pipeline ID (pl_XXXXX) for the auto-created workspace pipeline. Only available when status='completed' and success=True.

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/datalab/apis/datalab-api.md) · [All operations](https://skmtc.dev/datalab/apis/datalab-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/datalab/datalab-api/revisions/aa9f8ee18efb/schema)