Skip to main content
This guide shows the shortest useful Titan workflow: authenticate, create a task, run it once, poll the execution, and export the result. It uses the classic pattern—URLs, objective, and output schema—which matches most product monitors and extraction jobs. Titan also supports modular actions and multi-step tasks; see What is Titan Web Scraping? and Action types overview when you need search, crawl, or API steps in the same model. It is written as a practical API walkthrough, not a conceptual tour.
Rust snippets use ureq and serde_json. Tab titles (cURL, Go, TypeScript, Python, Rust) match Authentication and Use the Task Service API so your language choice stays in sync across pages.

What you will do

By the end of this guide, you will:
  1. Configure your API connection
  2. Create a task
  3. Start an execution
  4. Check execution state
  5. Export the result

Before you begin

Quickstart architecture

The sequence below is schematic: real responses wrap payloads in { "success": true, "data": … } except for file exports, which return raw bytes (see Step 4).

Step 1: create a task

Successful responses use the standard Titan envelope. The task identifier is data.id:

Capture TASK_ID

Step 2: run the task

The run endpoint returns 202 Accepted with an ExecutionResponse inside data. The execution UUID is data.id (not execution_id):

Capture EXECUTION_ID

Step 3: poll execution status

The JSON body is again the standard envelope; poll data.status until it reaches a terminal value. Typical statuses include: Keep polling until the execution reaches a terminal state.

Step 4: export the result

Once the execution is completed (or completed_with_errors when data still exists), export the dataset. GET /api/v1/executions/:id/results/export returns a file attachment (raw JSON, NDJSON, or CSV per the format query parameter). It does not use the { success, data } envelope. The default format is json.

Export JSON to a file

Download CSV

GET /api/v1/executions/:id/results (metadata) does use the standard success envelope; see the Task Service API group in the API Reference tab (OpenAPI) for the exact data shape.

Step 5: access media if present

If your output schema includes media fields, those fields will contain Titan-managed URLs. Use the execution media download endpoint when you want to resolve those assets directly.

End-to-end (one script)

Troubleshooting

Next steps