Moving from Platform to Production

Overview

The Pulse Playground is designed for building and testing your extraction pipeline visually. Once you’re happy with the results, the Show Code feature generates ready-to-run SDK code that reproduces your exact configuration — making the transition from Playground to production seamless.

The Show Code Feature

What Gets Included

The generated code reflects your exact Playground configuration:

Setting	Included?
Page range	✅ If set
Figure extraction	✅ If enabled
Figure descriptions	✅ If enabled
Show images	✅ If enabled
Return HTML	✅ If enabled
Effort mode	✅ If enabled
Chunking settings	✅ If configured
Chunk size	✅ If set
Split topics	✅ If split step added
Schema (single mode)	✅ If schema step added
Per-topic schemas (split mode)	✅ If split + schema configured
Saved preset IDs	✅ Uses config IDs when presets are loaded

Generated Code Examples

Extract Only

Python
TypeScript
curl

from pulse import Pulse

client = Pulse(api_key="YOUR_API_KEY")

result = client.extract(
    file=open("your_document.pdf", "rb"),
    storage={"enabled": True}
)

print(result.markdown)
print(f"Extraction ID: {result.extraction_id}")

import { PulseClient } from "pulse-ts-sdk";
import fs from "fs";

const client = new PulseClient({
    apiKey: "YOUR_API_KEY"
});

const result = await client.extract({
    file: fs.createReadStream("your_document.pdf"),
    storage: { enabled: true }
});

console.log(result.markdown);
console.log("Extraction ID:", result.extraction_id);

curl -X POST https://api.runpulse.com/extract \
  -H "x-api-key: YOUR_API_KEY" \
  -F "file=@your_document.pdf"

Extract → Split → Schema

Python
TypeScript
curl

from pulse import Pulse

client = Pulse(api_key="YOUR_API_KEY")

# Extract
result = client.extract(
    file=open("your_document.pdf", "rb"),
    storage={"enabled": True}
)
extraction_id = result.extraction_id

# Split
split_result = client.split(
    extraction_id=extraction_id,
    split_config={
        "split_input": [
            {"name": "Financials", "description": "Revenue and expense data"},
            {"name": "Leadership", "description": "Executive team information"}
        ]
    }
)
split_id = split_result.split_id

# Schema per topic
schema_result = client.schema(
    split_id=split_id,
    split_schema_config={
        "Financials": {
            "schema": {"type": "object", "properties": {"revenue": {"type": "number"}}},
            "schema_prompt": "Extract financial metrics"
        },
        "Leadership": {
            "schema": {"type": "object", "properties": {"ceo": {"type": "string"}}},
            "schema_prompt": "Extract leadership info"
        }
    }
)

print(schema_result.results)

import { PulseClient } from "pulse-ts-sdk";
import fs from "fs";

const client = new PulseClient({
    apiKey: "YOUR_API_KEY"
});

// Extract
const result = await client.extract({
    file: fs.createReadStream("your_document.pdf"),
    storage: { enabled: true }
});
const extractionId = result.extraction_id;

// Split
const splitResult = await client.split({
    extraction_id: extractionId,
    split_config: {
        split_input: [
            { name: "Financials", description: "Revenue and expense data" },
            { name: "Leadership", description: "Executive team information" }
        ]
    }
});
const splitId = splitResult.split_id;

// Schema per topic
const schemaResult = await client.schema({
    split_id: splitId,
    split_schema_config: {
        Financials: {
            schema: { type: "object", properties: { revenue: { type: "number" } } },
            schema_prompt: "Extract financial metrics"
        },
        Leadership: {
            schema: { type: "object", properties: { ceo: { type: "string" } } },
            schema_prompt: "Extract leadership info"
        }
    }
});

console.log(schemaResult.results);

# 1. Extract
curl -X POST https://api.runpulse.com/extract \
  -H "x-api-key: YOUR_API_KEY" \
  -F "file=@your_document.pdf"
# Save extraction_id

# 2. Split
curl -X POST https://api.runpulse.com/split \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "extraction_id": "EXTRACTION_ID",
    "split_config": {
      "split_input": [
        {"name": "Financials", "description": "Revenue and expense data"},
        {"name": "Leadership", "description": "Executive team information"}
      ]
    }
  }'
# Save split_id

# 3. Schema per topic
curl -X POST https://api.runpulse.com/schema \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "split_id": "SPLIT_ID",
    "split_schema_config": {
      "Financials": {
        "schema": {"type": "object", "properties": {"revenue": {"type": "number"}}},
        "schema_prompt": "Extract financial metrics"
      },
      "Leadership": {
        "schema": {"type": "object", "properties": {"ceo": {"type": "string"}}},
        "schema_prompt": "Extract leadership info"
      }
    }
  }'

Using Presets in Production

If your pipeline uses a saved preset (rather than inline configuration), the generated code references the preset’s config ID:

# Show Code output when using a saved preset
result = client.extract(
    file=open("your_document.pdf", "rb"),
    extraction_config_id="abc123-saved-preset-id",
    storage={"enabled": True}
)

This is the recommended approach for production because:

Centralized config — update the preset once, all future runs pick up the change
Team consistency — everyone references the same validated configuration
Cleaner code — no need to inline large schemas in every request

If you’ve edited a preset’s settings in the current session without saving, the generated code uses the edited inline settings rather than the preset ID — ensuring the code matches what you see in the Playground.

See Step Preset Library for the full guide on saving and using presets.

Production Best Practices

Use async mode for production workloads

Always use async_=True (Python) or async: true (TypeScript/curl) in production. This returns immediately with a job_id that you poll, preventing request timeouts on large documents.See Async Processing for the polling pattern.

Enable storage

Pass storage={"enabled": True} so Pulse saves the extraction result. This lets you run /split and /schema on the same extraction later without re-processing.

Use webhooks for event-driven architectures

Instead of polling, register a webhook URL and Pulse will POST the result to you when processing completes.See Webhooks for setup.

Handle errors gracefully

The API returns structured error codes. Always check for error responses and implement retry logic for transient failures.See Error Handling for the full error code reference.

Use config IDs for repeatability

If you’re running the same pipeline across many documents, save your settings as presets and use the config IDs. This makes your API calls shorter and your configuration auditable.

Step Preset Library

Save and reuse pipeline configurations with config IDs

API Quickstart

Get started with the Pulse API in 5 minutes

Platform Reference

Pipelines

Forms

Production Workflow

Library & Exports

Moving from Platform to Production

Overview

The Show Code Feature

What Gets Included

Generated Code Examples

Extract Only

Extract → Split → Schema

Using Presets in Production

Production Best Practices

Step Preset Library

API Quickstart

​Overview

​The Show Code Feature

​What Gets Included

​Generated Code Examples

​Extract Only

​Extract → Split → Schema

​Using Presets in Production

​Production Best Practices

​Related

Step Preset Library

API Quickstart

Overview

The Show Code Feature

What Gets Included

Generated Code Examples

Extract Only

Extract → Split → Schema

Using Presets in Production

Production Best Practices

Related