Resolve Dynamic Field Defaults

POST

/v1/pipelines/resolve

curl --request POST \
  --url https://example.com/v1/pipelines/resolve \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <X-API-Key>' \
  --data '{ "pipeline_template_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "field": "example", "values": {} }'

Run a launch field’s declared defaults resolver against the caller’s current input values. Which fields resolve, and from which sibling inputs, is published per template in its launch_fields.

Authorizations

• ApiKey
• Bearer

Request Body ^required

Media type application/json

ResolveRequest

object

pipeline_template_id

required

string format: uuid

field

required

string

values

object

key

additional properties

any

Example ^generated

{
  "pipeline_template_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
  "field": "example",
  "values": {}
}

Responses

200

Successful Response

Media type application/json

ResolveResponse

object

field

required

string

default

nullable

Example ^generated

{
  "field": "example",
  "default": "example"
}

400

Field declares no resolver

Media type application/json

ErrorResponse

Standard error response.

object

detail

required

Error message describing what went wrong

string

Example ^generated

{
  "detail": "example"
}

401

Invalid or missing API key

Media type application/json

ErrorResponse

Standard error response.

object

detail

required

Error message describing what went wrong

string

Example ^generated

{
  "detail": "example"
}

404

Template or field not found

Media type application/json

ErrorResponse

Standard error response.

object

detail

required

Error message describing what went wrong

string

Example ^generated

{
  "detail": "example"
}

422

Validation error