> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.cloudraker.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server.

# Run several capabilities over one set of files

POST https://api.cloudraker.com/v1/pipeline
Content-Type: application/json

Runs several capabilities over one set of files in a single call.

Every file is parsed once, then each step runs over the parsed set — **in parallel, not chained**. A step never consumes another step's output.

**A step is one of:**

- `{ "extract": {…} }`, `{ "redact": {…} }`, `{ "fill": {…} }`, `{ "sign": {…} }` — the same inline config the matching verb takes.
- `{ "action": "act_… | slug", "params": {…} }` — a [saved action](https://docs.cloudraker.com/api/cloud-raker-api/actions/get-action).

There is no `parse` step: parsing is automatic.

**Always asynchronous.** The response is `202` carrying the run id and one `{id, capability}` per step. Poll [the run](https://docs.cloudraker.com/api/cloud-raker-api/runs/get-run) — its `steps[]` reports each step's status and result under the id you were handed at create.

```json
{
  "files": [{ "id": "a04d6597-4e34-4a99-94ea-964c289a4c68" }],
  "steps": [
    { "extract": { "schema": { "type": "object", "properties": { "business_name": { "type": ["string", "null"] } } } } },
    { "redact": { "mode": "targeted" } }
  ]
}
```

**Learn more:** [Pipeline guide](https://docs.cloudraker.com/capabilities/pipeline)

Reference: https://docs.cloudraker.com/api/cloud-raker-api/capabilities/pipeline

## OpenAPI Specification

```yaml
openapi: 3.1.0
info:
  title: CloudRaker API
  version: 1.0.0
paths:
  /v1/pipeline:
    post:
      operationId: pipeline
      summary: Run several capabilities over one set of files
      description: >-
        Runs several capabilities over one set of files in a single call.


        Every file is parsed once, then each step runs over the parsed set —
        **in parallel, not chained**. A step never consumes another step's
        output.


        **A step is one of:**


        - `{ "extract": {…} }`, `{ "redact": {…} }`, `{ "fill": {…} }`, `{
        "sign": {…} }` — the same inline config the matching verb takes.

        - `{ "action": "act_… | slug", "params": {…} }` — a [saved
        action](https://docs.cloudraker.com/api/cloud-raker-api/actions/get-action).


        There is no `parse` step: parsing is automatic.


        **Always asynchronous.** The response is `202` carrying the run id and
        one `{id, capability}` per step. Poll [the
        run](https://docs.cloudraker.com/api/cloud-raker-api/runs/get-run) — its
        `steps[]` reports each step's status and result under the id you were
        handed at create.


        ```json

        {
          "files": [{ "id": "a04d6597-4e34-4a99-94ea-964c289a4c68" }],
          "steps": [
            { "extract": { "schema": { "type": "object", "properties": { "business_name": { "type": ["string", "null"] } } } } },
            { "redact": { "mode": "targeted" } }
          ]
        }

        ```


        **Learn more:** [Pipeline
        guide](https://docs.cloudraker.com/capabilities/pipeline)
      tags:
        - ''
      parameters:
        - name: Authorization
          in: header
          description: Bearer authentication
          required: true
          schema:
            type: string
      responses:
        '202':
          description: Accepted.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V1PipelineAccepted'
        '400':
          description: Invalid request (`invalid_request` / `invalid_schema`).
          content:
            application/json:
              schema:
                description: Any type
        '422':
          description: Unusable input file or webhook endpoint.
          content:
            application/json:
              schema:
                description: Any type
        '429':
          description: >-
            Rate limited. The `/v1` API allows at least **67 requests per minute
            per organization** (about 1,000 requests per 15 minutes) — a
            guaranteed floor, enforced per edge location, so a geographically
            spread caller may get more. Wait for the `Retry-After` interval and
            retry — the error is `retryable`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PipelineRequestTooManyRequestsError'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/V1PipelineBody'
servers:
  - url: https://api.cloudraker.com
    description: Production
  - url: https://api.staging.raker.one
    description: Staging
  - url: https://api.dev.raker.one
    description: Development
components:
  schemas:
    V1PipelineBodyFilesItemsOneOf0Processing:
      type: string
      enum:
        - auto
        - ocr
        - simple
        - transcribe
        - transcribe_diarize
      title: V1PipelineBodyFilesItemsOneOf0Processing
    V1PipelineBodyFilesItems0:
      type: object
      properties:
        url:
          type: string
          format: uri
        name:
          type: string
        processing:
          $ref: '#/components/schemas/V1PipelineBodyFilesItemsOneOf0Processing'
      required:
        - url
      title: V1PipelineBodyFilesItems0
    V1PipelineBodyFilesItems1:
      type: object
      properties:
        id:
          type: string
      required:
        - id
      title: V1PipelineBodyFilesItems1
    V1PipelineBodyFilesItems:
      oneOf:
        - $ref: '#/components/schemas/V1PipelineBodyFilesItems0'
        - $ref: '#/components/schemas/V1PipelineBodyFilesItems1'
      description: >-
        An input file, given one of two ways.


        - `{ "url": "…", "name"?: "…", "processing"?: "…" }` — fetched over
        http(s) for this run and purged with it.

        - `{ "id": "…" }` — a file you already registered with `POST /v1/files`,
        reusable across runs and never re-parsed.
      title: V1PipelineBodyFilesItems
    V1PipelineStepOneOf0ExtractUnit:
      type: string
      enum:
        - per_document
        - across_documents
        - rows_per_document
      description: >-
        What one extraction result covers.


        - `per_document` — one result object per file (the default).

        - `across_documents` — one result object for the whole set, read as a
        single body of evidence.

        - `rows_per_document` — a list of results per file, for documents that
        hold repeated records.
      title: V1PipelineStepOneOf0ExtractUnit
    V1PipelineStepOneOf0Extract:
      type: object
      properties:
        schema:
          type: object
          additionalProperties:
            description: Any type
          description: >-
            The shape to extract, as a JSON Schema object. Send `action` instead
            to use a saved shape, or neither to have one inferred.


            The root must be `{"type": "object"}`. The dialect is deliberately
            narrow — no `$ref`, `$defs`, `oneOf`, `anyOf`, `allOf`, `const` or
            `pattern` — with a maximum nesting depth of 5 and a 64 KB size
            limit. Make primitives nullable (`{"type": ["string", "null"]}`) so
            a missing value reads as `null` rather than a hallucination.
        action:
          type: string
          description: >-
            A saved action to run, by id or slug. An alternative to `schema`.


            The action carries the output shape and any saved settings. Config
            you send inline on the same call is merged over it, so `action` plus
            `instructions` refines a saved action for one run without redefining
            it.
        hints:
          type: string
          description: >-
            Prose guidance for **schema inference** — only valid when you send
            neither `schema` nor `action`.


            Say what the documents are and what matters in them ("freight bills
            of lading; I care about the load number, the shipper and the total")
            and the shape is inferred from the document itself. Sending `hints`
            alongside `schema` or `action` is a `400`: the shape is already
            decided.
        instructions:
          type: string
          description: >-
            Free-form guidance for the extraction, applied on top of the schema
            — house rules, formatting preferences, how to handle ambiguity.
        citations:
          type: boolean
          description: >-
            Whether to ground each extracted value in the source document. On by
            default.


            When on, `output.citations` maps every JSON path in the result to
            where it came from — `fileId` plus page and bounding box for
            documents, or a timecode for audio. Set to `false` to skip grounding
            when you only need the values.
        unit:
          $ref: '#/components/schemas/V1PipelineStepOneOf0ExtractUnit'
          description: >-
            What one extraction result covers.


            - `per_document` — one result object per file (the default).

            - `across_documents` — one result object for the whole set, read as
            a single body of evidence.

            - `rows_per_document` — a list of results per file, for documents
            that hold repeated records.
        model:
          type: string
          description: >-
            Pin the extraction to a specific model. Leave it unset to use the
            current default, which tracks the best available.
        judge:
          type: boolean
          description: >-
            Run a second review pass over the extracted values to catch
            mistakes. Slower and more thorough — worth it on documents where an
            error is expensive.
      title: V1PipelineStepOneOf0Extract
    V1PipelineStep0:
      type: object
      properties:
        extract:
          $ref: '#/components/schemas/V1PipelineStepOneOf0Extract'
      required:
        - extract
      title: V1PipelineStep0
    V1PipelineStepOneOf1RedactMode:
      type: string
      enum:
        - targeted
        - lines
      title: V1PipelineStepOneOf1RedactMode
    V1PipelineStepOneOf1RedactStyle:
      type: string
      enum:
        - beep
        - silence
      title: V1PipelineStepOneOf1RedactStyle
    V1PipelineStepOneOf1Redact:
      type: object
      properties:
        categories:
          type: array
          items:
            type: string
        instructions:
          type: string
        mode:
          $ref: '#/components/schemas/V1PipelineStepOneOf1RedactMode'
        style:
          $ref: '#/components/schemas/V1PipelineStepOneOf1RedactStyle'
        action:
          type: string
      title: V1PipelineStepOneOf1Redact
    V1PipelineStep1:
      type: object
      properties:
        redact:
          $ref: '#/components/schemas/V1PipelineStepOneOf1Redact'
      required:
        - redact
      title: V1PipelineStep1
    V1PipelineStepOneOf2FillTemplate0:
      type: object
      properties:
        id:
          type: string
      required:
        - id
      title: V1PipelineStepOneOf2FillTemplate0
    V1PipelineStepOneOf2FillTemplate1:
      type: object
      properties:
        url:
          type: string
          format: uri
        name:
          type: string
      required:
        - url
      title: V1PipelineStepOneOf2FillTemplate1
    V1PipelineStepOneOf2FillTemplate:
      oneOf:
        - $ref: '#/components/schemas/V1PipelineStepOneOf2FillTemplate0'
        - $ref: '#/components/schemas/V1PipelineStepOneOf2FillTemplate1'
      description: >-
        The blank form to fill, given one of two ways.


        - `{ "id": "…" }` — a saved template from `POST /v1/templates`, or any
        file you own.

        - `{ "url": "…", "name"?: "…" }` — fetched for this run only and purged
        with it.
      title: V1PipelineStepOneOf2FillTemplate
    V1PipelineStepOneOf2FillReview:
      type: string
      enum:
        - none
        - required
      description: >-
        Whether a person checks the drafted values before the form is produced.


        `none` (the default) fills and finishes. `required` parks the run at
        `needs_input` with one task per document — read it at `GET
        /v1/runs/{id}/task`, submit corrections to `POST /v1/runs/{id}/task`, or
        send someone to the ready-made page at `tasks[].url`.
      title: V1PipelineStepOneOf2FillReview
    V1PipelineStepOneOf2FillOutput:
      type: string
      enum:
        - flattened
        - editable
      description: >-
        What the produced PDF looks like. `flattened` (the default) bakes the
        values in so nothing can be changed; `editable` leaves the form
        fillable.
      title: V1PipelineStepOneOf2FillOutput
    V1PipelineStepOneOf2Fill:
      type: object
      properties:
        template:
          $ref: '#/components/schemas/V1PipelineStepOneOf2FillTemplate'
          description: >-
            The blank form to fill, given one of two ways.


            - `{ "id": "…" }` — a saved template from `POST /v1/templates`, or
            any file you own.

            - `{ "url": "…", "name"?: "…" }` — fetched for this run only and
            purged with it.
        instructions:
          type: string
          description: >-
            Free-form guidance for the drafting pass — which source document
            wins a conflict, how to format dates, which fields to leave blank.
        review:
          $ref: '#/components/schemas/V1PipelineStepOneOf2FillReview'
          description: >-
            Whether a person checks the drafted values before the form is
            produced.


            `none` (the default) fills and finishes. `required` parks the run at
            `needs_input` with one task per document — read it at `GET
            /v1/runs/{id}/task`, submit corrections to `POST
            /v1/runs/{id}/task`, or send someone to the ready-made page at
            `tasks[].url`.
        output:
          $ref: '#/components/schemas/V1PipelineStepOneOf2FillOutput'
          description: >-
            What the produced PDF looks like. `flattened` (the default) bakes
            the values in so nothing can be changed; `editable` leaves the form
            fillable.
        action:
          type: string
          description: >-
            A saved fill action to run, by id or slug. Config you send inline is
            merged over the saved config.
      required:
        - template
      title: V1PipelineStepOneOf2Fill
    V1PipelineStep2:
      type: object
      properties:
        fill:
          $ref: '#/components/schemas/V1PipelineStepOneOf2Fill'
      required:
        - fill
      title: V1PipelineStep2
    V1PipelineStepOneOf3SignSignersItems:
      type: object
      properties:
        name:
          type: string
        email:
          type: string
          format: email
      required:
        - name
        - email
      title: V1PipelineStepOneOf3SignSignersItems
    V1PipelineStepOneOf3SignPlacement:
      type: string
      enum:
        - page
        - tags
      description: >-
        Where signatures land in the document.


        `page` (the default) appends a signature certificate page. `tags` puts
        each signer's stamp over a `[Signature N]` placeholder already present
        in the document — every signer needs one, or the run fails.
      title: V1PipelineStepOneOf3SignPlacement
    V1PipelineStepOneOf3Sign:
      type: object
      properties:
        signers:
          type: array
          items:
            $ref: '#/components/schemas/V1PipelineStepOneOf3SignSignersItems'
          description: >-
            Who has to sign, in order — up to 50 people, each with a `name` and
            an `email`.


            Every signer verifies their email with a one-time code, then signs
            by typing their name. Track them individually at `GET
            /v1/runs/{id}/envelope`.
        message:
          type: string
          description: A note included in the invitation email each signer receives.
        placement:
          $ref: '#/components/schemas/V1PipelineStepOneOf3SignPlacement'
          description: >-
            Where signatures land in the document.


            `page` (the default) appends a signature certificate page. `tags`
            puts each signer's stamp over a `[Signature N]` placeholder already
            present in the document — every signer needs one, or the run fails.
      required:
        - signers
      title: V1PipelineStepOneOf3Sign
    V1PipelineStep3:
      type: object
      properties:
        sign:
          $ref: '#/components/schemas/V1PipelineStepOneOf3Sign'
      required:
        - sign
      title: V1PipelineStep3
    V1PipelineStep4:
      type: object
      properties:
        parse:
          type: object
          additionalProperties:
            description: Any type
      required:
        - parse
      title: V1PipelineStep4
    V1PipelineStep5:
      type: object
      properties:
        action:
          type: string
        config:
          type: object
          additionalProperties:
            description: Any type
        params:
          type: object
          additionalProperties:
            description: Any type
      required:
        - action
      title: V1PipelineStep5
    V1PipelineStep:
      oneOf:
        - $ref: '#/components/schemas/V1PipelineStep0'
        - $ref: '#/components/schemas/V1PipelineStep1'
        - $ref: '#/components/schemas/V1PipelineStep2'
        - $ref: '#/components/schemas/V1PipelineStep3'
        - $ref: '#/components/schemas/V1PipelineStep4'
        - $ref: '#/components/schemas/V1PipelineStep5'
      title: V1PipelineStep
    V1PipelineBodyWebhook0:
      type: object
      properties:
        url:
          type: string
          format: uri
      required:
        - url
      title: V1PipelineBodyWebhook0
    V1PipelineBodyWebhook1:
      type: object
      properties:
        id:
          type: string
      required:
        - id
      title: V1PipelineBodyWebhook1
    V1PipelineBodyWebhook:
      oneOf:
        - $ref: '#/components/schemas/V1PipelineBodyWebhook0'
        - $ref: '#/components/schemas/V1PipelineBodyWebhook1'
      description: >-
        Where to deliver this run's events, given one of two ways.


        - `{ "url": "…" }` — a one-off https endpoint for this run only.

        - `{ "id": "whe_…" }` — a saved endpoint from `POST /v1/webhooks`. Runs
        hold the reference, so pausing or re-pointing that endpoint applies to
        this run too.


        Deliveries are at-least-once and signed — dedupe on `eventId` and verify
        against `GET /v1/webhooks/jwks.json`.
      title: V1PipelineBodyWebhook
    V1PipelineBody:
      type: object
      properties:
        files:
          type: array
          items:
            $ref: '#/components/schemas/V1PipelineBodyFilesItems'
          description: >-
            The input files, up to 100. They are parsed once and every step sees
            the same parsed set.
        steps:
          type: array
          items:
            $ref: '#/components/schemas/V1PipelineStep'
          description: >-
            What to run over the files — up to 20 steps, executed in parallel
            rather than chained.


            Each step is either an inline capability config (`{ "extract": {…}
            }`, `{ "redact": {…} }`, `{ "fill": {…} }`, `{ "sign": {…} }`) or a
            saved action (`{ "action": "…", "params": {…} }`). There is no
            `parse` step: parsing is automatic. A step never consumes another
            step's output.
        metadata:
          type: object
          additionalProperties:
            description: Any type
          description: >-
            Arbitrary JSON you attach to the run and get back on every read of
            it.


            Use it to carry your own identifiers — an order number, a customer
            id — so a webhook or a polled run reconciles without a lookup table.
            Capped at 10 KB serialized.
        webhook:
          $ref: '#/components/schemas/V1PipelineBodyWebhook'
          description: >-
            Where to deliver this run's events, given one of two ways.


            - `{ "url": "…" }` — a one-off https endpoint for this run only.

            - `{ "id": "whe_…" }` — a saved endpoint from `POST /v1/webhooks`.
            Runs hold the reference, so pausing or re-pointing that endpoint
            applies to this run too.


            Deliveries are at-least-once and signed — dedupe on `eventId` and
            verify against `GET /v1/webhooks/jwks.json`.
        ttl:
          type: integer
          description: >-
            How long, in seconds, to keep this run and its files before purging
            them automatically.


            Defaults to 24 hours; the maximum is 604800 (7 days). The deadline
            comes back as `expiresAt` on every read of the run. Call `POST
            /v1/runs/{id}/keep` before then to clear the TTL and move the
            results into a space permanently.


            E-signature runs are exempt — an envelope waits for its signers
            however long that takes.
      required:
        - files
        - steps
      title: V1PipelineBody
    V1PipelineAcceptedStatus:
      type: string
      enum:
        - queued
        - processing
        - processed
        - failed
        - cancelled
        - expired
        - needs_input
      description: |-
        Where the run is in its life.

        | Status | Meaning |
        | --- | --- |
        | `queued` | Accepted, not started |
        | `processing` | Work in flight |
        | `needs_input` | Parked for a person — see `tasks[]` |
        | `processed` | Finished; `output` is populated |
        | `failed` | Finished unsuccessfully |
        | `cancelled` | Stopped on request |
        | `expired` | TTL elapsed and the data was purged |

        The last four are terminal.
      title: V1PipelineAcceptedStatus
    V1PipelineAcceptedStepsItemsCapability:
      type: string
      enum:
        - extract
        - parse
        - redact
        - fill
        - sign
        - action
      title: V1PipelineAcceptedStepsItemsCapability
    V1PipelineAcceptedStepsItems:
      type: object
      properties:
        id:
          type:
            - string
            - 'null'
        capability:
          $ref: '#/components/schemas/V1PipelineAcceptedStepsItemsCapability'
      required:
        - id
        - capability
      title: V1PipelineAcceptedStepsItems
    V1PipelineAccepted:
      type: object
      properties:
        object:
          type: string
          enum:
            - pipeline_run
        id:
          type: string
        status:
          $ref: '#/components/schemas/V1PipelineAcceptedStatus'
          description: |-
            Where the run is in its life.

            | Status | Meaning |
            | --- | --- |
            | `queued` | Accepted, not started |
            | `processing` | Work in flight |
            | `needs_input` | Parked for a person — see `tasks[]` |
            | `processed` | Finished; `output` is populated |
            | `failed` | Finished unsuccessfully |
            | `cancelled` | Stopped on request |
            | `expired` | TTL elapsed and the data was purged |

            The last four are terminal.
        statusUrl:
          type: string
        steps:
          type: array
          items:
            $ref: '#/components/schemas/V1PipelineAcceptedStepsItems'
      required:
        - object
        - id
        - status
        - statusUrl
        - steps
      title: V1PipelineAccepted
    V1PipelinePostResponsesContentApplicationJsonSchemaCode:
      type: string
      enum:
        - rate_limited
      title: V1PipelinePostResponsesContentApplicationJsonSchemaCode
    PipelineRequestTooManyRequestsError:
      type: object
      properties:
        code:
          $ref: >-
            #/components/schemas/V1PipelinePostResponsesContentApplicationJsonSchemaCode
        message:
          type: string
        retryable:
          type: boolean
        requestId:
          type: string
        docUrl:
          type: string
      required:
        - code
        - message
        - retryable
        - requestId
      title: PipelineRequestTooManyRequestsError
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer

```

## Examples



**Request**

```json
{
  "files": [
    {
      "url": "https://example.com/documents/invoice_12345.pdf"
    }
  ],
  "steps": [
    {
      "extract": {}
    }
  ]
}
```

**Response**

```json
{
  "object": "pipeline_run",
  "id": "run_7f9c8a2b-3d4e-4a1f-bb2e-9c8d7e6f5a4b",
  "status": "queued",
  "statusUrl": "https://api.cloudraker.com/v1/runs/run_7f9c8a2b-3d4e-4a1f-bb2e-9c8d7e6f5a4b/status",
  "steps": [
    {
      "id": "step_3a1b2c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d",
      "capability": "extract"
    }
  ]
}
```

**SDK Code**

```python
import requests

url = "https://api.cloudraker.com/v1/pipeline"

payload = {
    "files": [{ "url": "https://example.com/documents/invoice_12345.pdf" }],
    "steps": [{ "extract": {} }]
}
headers = {
    "Authorization": "Bearer <token>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.json())
```

```javascript
const url = 'https://api.cloudraker.com/v1/pipeline';
const options = {
  method: 'POST',
  headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
  body: '{"files":[{"url":"https://example.com/documents/invoice_12345.pdf"}],"steps":[{"extract":{}}]}'
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}
```

```go
package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "https://api.cloudraker.com/v1/pipeline"

	payload := strings.NewReader("{\n  \"files\": [\n    {\n      \"url\": \"https://example.com/documents/invoice_12345.pdf\"\n    }\n  ],\n  \"steps\": [\n    {\n      \"extract\": {}\n    }\n  ]\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("Authorization", "Bearer <token>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(res)
	fmt.Println(string(body))

}
```

```ruby
require 'uri'
require 'net/http'

url = URI("https://api.cloudraker.com/v1/pipeline")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "{\n  \"files\": [\n    {\n      \"url\": \"https://example.com/documents/invoice_12345.pdf\"\n    }\n  ],\n  \"steps\": [\n    {\n      \"extract\": {}\n    }\n  ]\n}"

response = http.request(request)
puts response.read_body
```

```java
import com.mashape.unirest.http.HttpResponse;
import com.mashape.unirest.http.Unirest;

HttpResponse<String> response = Unirest.post("https://api.cloudraker.com/v1/pipeline")
  .header("Authorization", "Bearer <token>")
  .header("Content-Type", "application/json")
  .body("{\n  \"files\": [\n    {\n      \"url\": \"https://example.com/documents/invoice_12345.pdf\"\n    }\n  ],\n  \"steps\": [\n    {\n      \"extract\": {}\n    }\n  ]\n}")
  .asString();
```

```php
<?php
require_once('vendor/autoload.php');

$client = new \GuzzleHttp\Client();

$response = $client->request('POST', 'https://api.cloudraker.com/v1/pipeline', [
  'body' => '{
  "files": [
    {
      "url": "https://example.com/documents/invoice_12345.pdf"
    }
  ],
  "steps": [
    {
      "extract": {}
    }
  ]
}',
  'headers' => [
    'Authorization' => 'Bearer <token>',
    'Content-Type' => 'application/json',
  ],
]);

echo $response->getBody();
```

```csharp
using RestSharp;

var client = new RestClient("https://api.cloudraker.com/v1/pipeline");
var request = new RestRequest(Method.POST);
request.AddHeader("Authorization", "Bearer <token>");
request.AddHeader("Content-Type", "application/json");
request.AddParameter("application/json", "{\n  \"files\": [\n    {\n      \"url\": \"https://example.com/documents/invoice_12345.pdf\"\n    }\n  ],\n  \"steps\": [\n    {\n      \"extract\": {}\n    }\n  ]\n}", ParameterType.RequestBody);
IRestResponse response = client.Execute(request);
```

```swift
import Foundation

let headers = [
  "Authorization": "Bearer <token>",
  "Content-Type": "application/json"
]
let parameters = [
  "files": [["url": "https://example.com/documents/invoice_12345.pdf"]],
  "steps": [["extract": []]]
] as [String : Any]

let postData = JSONSerialization.data(withJSONObject: parameters, options: [])

let request = NSMutableURLRequest(url: NSURL(string: "https://api.cloudraker.com/v1/pipeline")! as URL,
                                        cachePolicy: .useProtocolCachePolicy,
                                    timeoutInterval: 10.0)
request.httpMethod = "POST"
request.allHTTPHeaderFields = headers
request.httpBody = postData as Data

let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
  if (error != nil) {
    print(error as Any)
  } else {
    let httpResponse = response as? HTTPURLResponse
    print(httpResponse)
  }
})

dataTask.resume()
```