> This page is for version v1 (default).
> For other versions, use one of these documentation indexes:
> - v1 (default): https://docs.plextera.com/v-1/llms.txt

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

# Overview

## What you can do

#### [Upload documents](/guides/introduction/quickstart)

Upload PDFs, images, Office files, and more - up to 50 MB per file.

#### [Extract document fields](/guides/core-guides/document-extraction)

Extract structured fields from documents with Document Insights.

#### [Trigger workflow runs](/guides/core-guides/workflow-runs)

Start and monitor workflow runs for document processing pipelines.

#### [Subscribe to events](/guides/core-guides/event-subscriptions)

Receive webhook push notifications when extractions and workflow runs reach terminal states.

## How it works

```mermaid
flowchart LR
    A["Upload file<br />POST /files"] --> B["Process<br />extraction or workflow run"]
    B --> C["Poll<br />GET status + output"]
    B --> D["Subscribe<br />webhook event"]
```

Upload a document to get a `fileId`, process it with Document Insights or a Studio workflow, then either poll for the result or let Plextera push it to your webhook.

## Key concepts

**Workspace** - your API key gives access to one Plextera workspace. You do not pass a workspace identifier in API requests.

**Files** - documents stored in Plextera and referenced by `fileId`. Upload once, reuse across extractions and workflow runs. Extractions can also take a document by URL or as a direct upload, with no separate Files call.

**Document Insights** - asynchronous document extraction that produces typed field values from a document. Each extraction returns an ID you can use to poll status, read output, submit feedback, or correlate events.

**Workflows** - processing pipelines configured in Plextera Studio. Can include Document Insights steps, data transformation, and custom logic.

**Event subscriptions** - HTTPS webhooks that push notifications when document extractions or workflow runs reach terminal states. The Event Subscriptions API records each event and lets you inspect its deliveries, optionally filtered by subscription.

**Pagination** - list endpoints accept `page` (zero-based) and `size` (default 50, max 100) parameters. Every response includes a `pageInfo` object with `totalItems` and `totalPages`.

**Errors** - all error responses share a common envelope with a machine-readable `code`, a human-readable `message`, and a `requestId` for tracing. Validation failures include a `details` array with field-level errors. See [Errors](/guides/introduction/errors) for the full code table and retry guidance.

## Next steps

* [Quickstart](/guides/introduction/quickstart) - choose the right first flow
* [Document Extraction](/guides/core-guides/document-extraction) - extract fields and read output
* [Workflow Runs](/guides/core-guides/workflow-runs) - trigger Studio workflows from your application
* [Event Subscriptions](/guides/core-guides/event-subscriptions) - receive push notifications instead of polling