---
title: "Get a pipeline element's job_config"
method: GET
path: "/pipelines/elements/{element_id}/job_config"
tags: ["Pipeline"]
---

# Get a pipeline element's job_config

`GET /pipelines/elements/{element_id}/job_config`

## Request

- Base URL: `https://api.ionworks.com`
- URL: `https://api.ionworks.com/pipelines/elements/{element_id}/job_config`
- Auth: none declared

Return one element's ``job_config``, hydrated lazily on expand.

The bulk `/elements` response projects the bigger keys (`parameters`,
`optimizer`, `cost`) out of every element so the details page loads fast;
this fills them back in for the one element a drawer is showing. Returns
``{}`` for an element that does not exist or is not visible to the caller.

Note this is the DB row, not the storage copy — the two differ only by
`objectives`, the multi-MB serialized measurement payload the worker reads
directly and no client needs.

## Path parameters

- `element_id` string, uuid, required

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

## Changes

- **2026-09-30** `ea3d377fec1a`: 1 breaking
  - for the `path` request parameter `element_id`, the format changed from no format to `uuid`

[Operation history](https://skmtc.dev/ionworks/apis/ionworks-api/changes/pipelines/elements/:element_id/job_config/get.md)

---

[API](https://skmtc.dev/ionworks/apis/ionworks-api.md) - [All operations](https://skmtc.dev/ionworks/apis/ionworks-api/llms.txt) - [OpenAPI document](https://skmtc.dev/ionworks/apis/ionworks-api/revisions/abebbbc5f60a?raw)