extend-ai 0.0.18 → 0.1.0

package/reference.md

@@ -78,9 +78,9 @@ await client.parseAsync({
 
 ##
 
-## WorkflowRun
+## File
 
-<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">list</a>({ ...params }) -> Extend.WorkflowRunListResponse</code></summary>
+<details><summary><code>client.file.<a href="/src/api/resources/file/client/Client.ts">list</a>({ ...params }) -> Extend.FileListResponse</code></summary>
 <dl>
 <dd>
 
@@ -92,7 +92,7 @@ await client.parseAsync({
 <dl>
 <dd>
 
-List runs of a Workflow. Workflows are sequences of steps that process files and data in a specific order to achieve a desired outcome. A WorkflowRun represents a single execution of a workflow against a file.
+List files in your account. Files represent documents that have been uploaded to Extend. This endpoint returns a paginated response. You can use the `nextPageToken` to fetch subsequent results.
 
 </dd>
 </dl>
@@ -108,12 +108,8 @@ List runs of a Workflow. Workflows are sequences of steps that process files and
 <dd>
 
 ```typescript
-await client.workflowRun.list({
-    status: "PENDING",
-    workflowId: "workflowId",
-    batchId: "batchId",
-    fileNameContains: "fileNameContains",
-    sortBy: "updatedAt",
+await client.file.list({
+    nameContains: "nameContains",
     sortDir: "asc",
     nextPageToken: "xK9mLPqRtN3vS8wF5hB2cQ==:zWvUxYjM4nKpL7aDgE9HbTcR2mAyX3/Q+CNkfBSw1dZ=",
     maxPageSize: 1,
@@ -133,7 +129,7 @@ await client.workflowRun.list({
 <dl>
 <dd>
 
-**request:** `Extend.WorkflowRunListRequest`
+**request:** `Extend.FileListRequest`
 
 </dd>
 </dl>
@@ -141,7 +137,7 @@ await client.workflowRun.list({
 <dl>
 <dd>
 
-**requestOptions:** `WorkflowRun.RequestOptions`
+**requestOptions:** `File_.RequestOptions`
 
 </dd>
 </dl>
@@ -152,7 +148,7 @@ await client.workflowRun.list({
 </dl>
 </details>
 
-<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">create</a>({ ...params }) -> Extend.WorkflowRunCreateResponse</code></summary>
+<details><summary><code>client.file.<a href="/src/api/resources/file/client/Client.ts">get</a>(id, { ...params }) -> Extend.FileGetResponse</code></summary>
 <dl>
 <dd>
 
@@ -164,7 +160,7 @@ await client.workflowRun.list({
 <dl>
 <dd>
 
-Run a Workflow with files. A Workflow is a sequence of steps that process files and data in a specific order to achieve a desired outcome. A WorkflowRun will be created for each file processed. A WorkflowRun represents a single execution of a workflow against a file.
+Fetch a file by its ID to obtain additional details and the raw file content.
 
 </dd>
 </dl>
@@ -180,8 +176,10 @@ Run a Workflow with files. A Workflow is a sequence of steps that process files
 <dd>
 
 ```typescript
-await client.workflowRun.create({
-    workflowId: "workflow_id_here",
+await client.file.get("file_id_here", {
+    rawText: true,
+    markdown: true,
+    html: true,
 });
 ```
 
@@ -198,7 +196,11 @@ await client.workflowRun.create({
 <dl>
 <dd>
 
-**request:** `Extend.WorkflowRunCreateRequest`
+**id:** `string`
+
+Extend's ID for the file. It will always start with `"file_"`. This ID is returned when creating a new File, or the value on the `fileId` field in a WorkflowRun.
+
+Example: `"file_Xj8mK2pL9nR4vT7qY5wZ"`
 
 </dd>
 </dl>
@@ -206,7 +208,15 @@ await client.workflowRun.create({
 <dl>
 <dd>
 
-**requestOptions:** `WorkflowRun.RequestOptions`
+**request:** `Extend.FileGetRequest`
+
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `File_.RequestOptions`
 
 </dd>
 </dl>
@@ -217,7 +227,7 @@ await client.workflowRun.create({
 </dl>
 </details>
 
-<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">get</a>(workflowRunId) -> Extend.WorkflowRunGetResponse</code></summary>
+<details><summary><code>client.file.<a href="/src/api/resources/file/client/Client.ts">delete</a>(id) -> Extend.FileDeleteResponse</code></summary>
 <dl>
 <dd>
 
@@ -229,7 +239,9 @@ await client.workflowRun.create({
 <dl>
 <dd>
 
-Once a workflow has been run, you can check the status and output of a specific WorkflowRun.
+Delete a file and all associated data from Extend. This operation is permanent and cannot be undone.
+
+This endpoint can be used if you'd like to manage data retention on your own rather than automated data retention policies. Or make one-off deletions for your downstream customers.
 
 </dd>
 </dl>
@@ -245,7 +257,7 @@ Once a workflow has been run, you can check the status and output of a specific
 <dd>
 
 ```typescript
-await client.workflowRun.get("workflow_run_id_here");
+await client.file.delete("file_id_here");
 ```
 
 </dd>
@@ -261,11 +273,11 @@ await client.workflowRun.get("workflow_run_id_here");
 <dl>
 <dd>
 
-**workflowRunId:** `string`
+**id:** `string`
 
-The ID of the WorkflowRun that was outputted after a Workflow was run through the API.
+The ID of the file to delete.
 
-Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
+Example: `"file_xK9mLPqRtN3vS8wF5hB2cQ"`
 
 </dd>
 </dl>
@@ -273,7 +285,7 @@ Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
 <dl>
 <dd>
 
-**requestOptions:** `WorkflowRun.RequestOptions`
+**requestOptions:** `File_.RequestOptions`
 
 </dd>
 </dl>
@@ -284,7 +296,7 @@ Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
 </dl>
 </details>
 
-<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">update</a>(workflowRunId, { ...params }) -> Extend.WorkflowRunUpdateResponse</code></summary>
+<details><summary><code>client.file.<a href="/src/api/resources/file/client/Client.ts">upload</a>(file) -> Extend.FileUploadResponse</code></summary>
 <dl>
 <dd>
 
@@ -296,7 +308,15 @@ Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
 <dl>
 <dd>
 
-You can update the name and metadata of an in progress WorkflowRun at any time using this endpoint.
+Upload and create a new file in Extend.
+
+This endpoint accepts file contents and registers them as a File in Extend, which can be used for [running workflows](https://docs.extend.ai/2025-04-21/developers/api-reference/workflow-endpoints/run-workflow), [creating evaluation set items](https://docs.extend.ai/2025-04-21/developers/api-reference/evaluation-set-endpoints/bulk-create-evaluation-set-items), [parsing](https://docs.extend.ai/2025-04-21/developers/api-reference/parse-endpoints/parse-file), etc.
+
+If an uploaded file is detected as a Word or PowerPoint document, it will be automatically converted to a PDF.
+
+Supported file types can be found [here](/product/general/supported-file-types).
+
+This endpoint requires multipart form encoding. Most HTTP clients will handle this encoding automatically (see the examples).
 
 </dd>
 </dl>
@@ -312,7 +332,7 @@ You can update the name and metadata of an in progress WorkflowRun at any time u
 <dd>
 
 ```typescript
-await client.workflowRun.update("workflow_run_id_here");
+await client.file.upload(createReadStream("path/to/file"));
 ```
 
 </dd>
@@ -328,19 +348,7 @@ await client.workflowRun.update("workflow_run_id_here");
 <dl>
 <dd>
 
-**workflowRunId:** `string`
-
-The ID of the WorkflowRun. This ID will start with "workflow_run". This ID can be found in the API response when creating a Workflow Run, or in the "history" tab of a workflow on the Extend platform.
-
-Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
-
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request:** `Extend.WorkflowRunUpdateRequest`
+**file:** `File | fs.ReadStream | Blob`
 
 </dd>
 </dl>
@@ -348,7 +356,7 @@ Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
 <dl>
 <dd>
 
-**requestOptions:** `WorkflowRun.RequestOptions`
+**requestOptions:** `File_.RequestOptions`
 
 </dd>
 </dl>
@@ -359,7 +367,9 @@ Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
 </dl>
 </details>
 
-<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">delete</a>(workflowRunId) -> Extend.WorkflowRunDeleteResponse</code></summary>
+## ParserRun
+
+<details><summary><code>client.parserRun.<a href="/src/api/resources/parserRun/client/Client.ts">get</a>(id, { ...params }) -> Extend.ParserRunGetResponse</code></summary>
 <dl>
 <dd>
 
@@ -371,9 +381,11 @@ Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
 <dl>
 <dd>
 
-Delete a workflow run and all associated data from Extend. This operation is permanent and cannot be undone.
+Retrieve the status and results of a parser run.
 
-This endpoint can be used if you'd like to manage data retention on your own rather than automated data retention policies. Or make one-off deletions for your downstream customers.
+Use this endpoint to get results for a parser run that has already completed, or to check on the status of an asynchronous parser run initiated via the [Parse File Asynchronously](https://docs.extend.ai/2025-04-21/developers/api-reference/parse-endpoints/parse-file-async) endpoint.
+
+If parsing is still in progress, you'll receive a response with just the status. Once complete, you'll receive the full parsed content in the response.
 
 </dd>
 </dl>
@@ -389,7 +401,9 @@ This endpoint can be used if you'd like to manage data retention on your own rat
 <dd>
 
 ```typescript
-await client.workflowRun.delete("workflow_run_id_here");
+await client.parserRun.get("parser_run_id_here", {
+    responseType: "json",
+});
 ```
 
 </dd>
@@ -405,11 +419,11 @@ await client.workflowRun.delete("workflow_run_id_here");
 <dl>
 <dd>
 
-**workflowRunId:** `string`
+**id:** `string`
 
-The ID of the workflow run to delete.
+The unique identifier for the parser run.
 
-Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
+Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 
 </dd>
 </dl>
@@ -417,7 +431,15 @@ Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
 <dl>
 <dd>
 
-**requestOptions:** `WorkflowRun.RequestOptions`
+**request:** `Extend.ParserRunGetRequest`
+
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `ParserRun.RequestOptions`
 
 </dd>
 </dl>
@@ -428,7 +450,7 @@ Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
 </dl>
 </details>
 
-<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">cancel</a>(workflowRunId) -> Extend.WorkflowRunCancelResponse</code></summary>
+<details><summary><code>client.parserRun.<a href="/src/api/resources/parserRun/client/Client.ts">delete</a>(id) -> Extend.ParserRunDeleteResponse</code></summary>
 <dl>
 <dd>
 
@@ -440,9 +462,9 @@ Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
 <dl>
 <dd>
 
-Cancel a running workflow run by its ID. This endpoint allows you to stop a workflow run that is currently in progress.
+Delete a parser run and all associated data from Extend. This operation is permanent and cannot be undone.
 
-Note: Only workflow runs with a status of `PROCESSING` or `PENDING` can be cancelled. Workflow runs that are completed, failed, in review, rejected, or already cancelled cannot be cancelled.
+This endpoint can be used if you'd like to manage data retention on your own rather than automated data retention policies. Or make one-off deletions for your downstream customers.
 
 </dd>
 </dl>
@@ -458,7 +480,7 @@ Note: Only workflow runs with a status of `PROCESSING` or `PENDING` can be cance
 <dd>
 
 ```typescript
-await client.workflowRun.cancel("workflow_run_id_here");
+await client.parserRun.delete("parser_run_id_here");
 ```
 
 </dd>
@@ -474,11 +496,11 @@ await client.workflowRun.cancel("workflow_run_id_here");
 <dl>
 <dd>
 
-**workflowRunId:** `string`
+**id:** `string`
 
-The ID of the workflow run to cancel.
+The ID of the parser run to delete.
 
-Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
+Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 
 </dd>
 </dl>
@@ -486,7 +508,7 @@ Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
 <dl>
 <dd>
 
-**requestOptions:** `WorkflowRun.RequestOptions`
+**requestOptions:** `ParserRun.RequestOptions`
 
 </dd>
 </dl>
@@ -497,9 +519,9 @@ Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
 </dl>
 </details>
 
-## BatchWorkflowRun
+## Edit
 
-<details><summary><code>client.batchWorkflowRun.<a href="/src/api/resources/batchWorkflowRun/client/Client.ts">create</a>({ ...params }) -> Extend.BatchWorkflowRunCreateResponse</code></summary>
+<details><summary><code>client.edit.<a href="/src/api/resources/edit/client/Client.ts">create</a>({ ...params }) -> Extend.EditRun</code></summary>
 <dl>
 <dd>
 
@@ -511,23 +533,13 @@ Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
 <dl>
 <dd>
 
-This endpoint allows you to efficiently initiate large batches of workflow runs in a single request (up to 1,000 in a single request, but you can queue up multiple batches in rapid succession). It accepts an array of inputs, each containing a file and metadata pair. The primary use case for this endpoint is for doing large bulk runs of >1000 files at a time that can process over the course of a few hours without needing to manage rate limits that would likely occur using the primary run endpoint.
-
-Unlike the single [Run Workflow](/developers/api-reference/workflow-endpoints/run-workflow) endpoint which returns the details of the created workflow runs immediately, this batch endpoint returns a `batchId`.
-
-Our recommended usage pattern is to integrate with [Webhooks](/product/webhooks/configuration) for consuming results, using the `metadata` and `batchId` to match up results to the original inputs in your downstream systems. However, you can integrate in a polling mechanism by using a combination of the [List Workflow Runs](https://docs.extend.ai/2025-04-21/developers/api-reference/workflow-endpoints/list-workflow-runs) endpoint to fetch all runs via a batch, and then [Get Workflow Run](https://docs.extend.ai/2025-04-21/developers/api-reference/workflow-endpoints/get-workflow-run) to fetch the full outputs each run.
-
-**Priority:** All workflow runs created through this batch endpoint are automatically assigned a priority of 90.
-
-**Processing and Monitoring:**
-Upon successful submission, the endpoint returns a `batchId`. The individual workflow runs are then queued for processing.
+Edit and manipulate PDF documents by detecting and filling form fields.
+This is a synchronous endpoint that will wait for the edit operation to complete (up to 5 minutes) before returning results. For longer operations, use the [Edit File Async](/developers/api-reference/edit-endpoints/edit-file-async) endpoint.
 
-- **Monitoring:** Track the progress and consume results of individual runs using [Webhooks](/product/webhooks/configuration). Subscribe to events like `workflow_run.completed`, `workflow_run.failed`, etc. The webhook payload for these events will include the corresponding `batchId` and the `metadata` you provided for each input.
-- **Fetching Results:** You can also use the [List Workflow Runs](https://docs.extend.ai/2025-04-21/developers/api-reference/workflow-endpoints/list-workflow-runs) endpoint and filter using the `batchId` query param.
-  </dd>
-  </dl>
-  </dd>
-  </dl>
+</dd>
+</dl>
+</dd>
+</dl>
 
 #### 🔌 Usage
 
@@ -538,9 +550,8 @@ Upon successful submission, the endpoint returns a `batchId`. The individual wor
 <dd>
 
 ```typescript
-await client.batchWorkflowRun.create({
-    workflowId: "workflow_id_here",
-    inputs: [{}],
+await client.edit.create({
+    file: {},
 });
 ```
 
@@ -557,7 +568,7 @@ await client.batchWorkflowRun.create({
 <dl>
 <dd>
 
-**request:** `Extend.BatchWorkflowRunCreateRequest`
+**request:** `Extend.EditCreateRequest`
 
 </dd>
 </dl>
@@ -565,7 +576,7 @@ await client.batchWorkflowRun.create({
 <dl>
 <dd>
 
-**requestOptions:** `BatchWorkflowRun.RequestOptions`
+**requestOptions:** `Edit.RequestOptions`
 
 </dd>
 </dl>
@@ -576,9 +587,7 @@ await client.batchWorkflowRun.create({
 </dl>
 </details>
 
-## ProcessorRun
-
-<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">list</a>({ ...params }) -> Extend.ProcessorRunListResponse</code></summary>
+<details><summary><code>client.edit.<a href="/src/api/resources/edit/client/Client.ts">createAsync</a>({ ...params }) -> Extend.EditRunStatus</code></summary>
 <dl>
 <dd>
 
@@ -590,12 +599,19 @@ await client.batchWorkflowRun.create({
 <dl>
 <dd>
 
-List runs of a Processor. A ProcessorRun represents a single execution of a processor against a file.
+Edit and manipulate PDF documents **asynchronously** by filling forms, adding/modifying text fields, and applying structured changes.
 
-</dd>
-</dl>
-</dd>
-</dl>
+The Edit Async endpoint allows you to convert and edit documents asynchronously and get an edit run ID that can be used to check status and retrieve results with the [Get Edit Run](/developers/api-reference/edit-endpoints/get-edit-run) endpoint.
+
+This is useful for:
+
+- Large files that may take longer to process
+- Avoiding timeout issues with synchronous editing
+- Processing multiple files in parallel
+  </dd>
+  </dl>
+  </dd>
+  </dl>
 
 #### 🔌 Usage
 
@@ -606,17 +622,8 @@ List runs of a Processor. A ProcessorRun represents a single execution of a proc
 <dd>
 
 ```typescript
-await client.processorRun.list({
-    status: "PENDING",
-    processorId: "processorId",
-    processorType: "EXTRACT",
-    sourceId: "sourceId",
-    source: "ADMIN",
-    fileNameContains: "fileNameContains",
-    sortBy: "updatedAt",
-    sortDir: "asc",
-    nextPageToken: "xK9mLPqRtN3vS8wF5hB2cQ==:zWvUxYjM4nKpL7aDgE9HbTcR2mAyX3/Q+CNkfBSw1dZ=",
-    maxPageSize: 1,
+await client.edit.createAsync({
+    file: {},
 });
 ```
 
@@ -633,7 +640,7 @@ await client.processorRun.list({
 <dl>
 <dd>
 
-**request:** `Extend.ProcessorRunListRequest`
+**request:** `Extend.EditCreateAsyncRequest`
 
 </dd>
 </dl>
@@ -641,7 +648,7 @@ await client.processorRun.list({
 <dl>
 <dd>
 
-**requestOptions:** `ProcessorRun.RequestOptions`
+**requestOptions:** `Edit.RequestOptions`
 
 </dd>
 </dl>
@@ -652,7 +659,7 @@ await client.processorRun.list({
 </dl>
 </details>
 
-<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">create</a>({ ...params }) -> Extend.ProcessorRunCreateResponse</code></summary>
+<details><summary><code>client.edit.<a href="/src/api/resources/edit/client/Client.ts">get</a>(id) -> Extend.EditGetResponse</code></summary>
 <dl>
 <dd>
 
@@ -664,21 +671,16 @@ await client.processorRun.list({
 <dl>
 <dd>
 
-Run processors (extraction, classification, splitting, etc.) on a given document.
-
-**Synchronous vs Asynchronous Processing:**
+Retrieve the status and results of an edit run.
 
-- **Asynchronous (default)**: Returns immediately with `PROCESSING` status. Use webhooks or polling to get results.
-- **Synchronous**: Set `sync: true` to wait for completion and get final results in the response (5-minute timeout).
+Use this endpoint to get results for an edit run that has already completed, or to check on the status of an asynchronous edit run initiated via the [Edit File Asynchronously](/developers/api-reference/edit-endpoints/edit-file-async) endpoint.
 
-**For asynchronous processing:**
+If editing is still in progress, you'll receive a response with just the status. Once complete, you'll receive the full edited file information in the response.
 
-- You can [configure webhooks](https://docs.extend.ai/2025-04-21/developers/webhooks/configuration) to receive notifications when a processor run is complete or failed.
-- Or you can [poll the get endpoint](https://docs.extend.ai/2025-04-21/developers/api-reference/processor-endpoints/get-processor-run) for updates on the status of the processor run.
-  </dd>
-  </dl>
-  </dd>
-  </dl>
+</dd>
+</dl>
+</dd>
+</dl>
 
 #### 🔌 Usage
 
@@ -689,9 +691,7 @@ Run processors (extraction, classification, splitting, etc.) on a given document
 <dd>
 
 ```typescript
-await client.processorRun.create({
-    processorId: "processor_id_here",
-});
+await client.edit.get("edit_run_id_here");
 ```
 
 </dd>
@@ -707,7 +707,11 @@ await client.processorRun.create({
 <dl>
 <dd>
 
-**request:** `Extend.ProcessorRunCreateRequest`
+**id:** `string`
+
+The unique identifier for the edit run.
+
+Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 
 </dd>
 </dl>
@@ -715,7 +719,7 @@ await client.processorRun.create({
 <dl>
 <dd>
 
-**requestOptions:** `ProcessorRun.RequestOptions`
+**requestOptions:** `Edit.RequestOptions`
 
 </dd>
 </dl>
@@ -726,7 +730,7 @@ await client.processorRun.create({
 </dl>
 </details>
 
-<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">get</a>(id) -> Extend.ProcessorRunGetResponse</code></summary>
+<details><summary><code>client.edit.<a href="/src/api/resources/edit/client/Client.ts">delete</a>(id) -> Extend.EditDeleteResponse</code></summary>
 <dl>
 <dd>
 
@@ -738,9 +742,9 @@ await client.processorRun.create({
 <dl>
 <dd>
 
-Retrieve details about a specific processor run, including its status, outputs, and any edits made during review.
+Delete an edit run and all associated data from Extend. This operation is permanent and cannot be undone.
 
-A common use case for this endpoint is to poll for the status and final output of an async processor run when using the [Run Processor](https://docs.extend.ai/2025-04-21/developers/api-reference/processor-endpoints/run-processor) endpoint. For instance, if you do not want to not configure webhooks to receive the output via completion/failure events.
+This endpoint can be used if you'd like to manage data retention on your own rather than relying on automated data retention policies, or to make one-off deletions for your downstream customers.
 
 </dd>
 </dl>
@@ -756,7 +760,7 @@ A common use case for this endpoint is to poll for the status and final output o
 <dd>
 
 ```typescript
-await client.processorRun.get("processor_run_id_here");
+await client.edit.delete("edit_run_id_here");
 ```
 
 </dd>
@@ -774,9 +778,9 @@ await client.processorRun.get("processor_run_id_here");
 
 **id:** `string`
 
-The unique identifier for this processor run.
+The ID of the edit run to delete.
 
-Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
+Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 
 </dd>
 </dl>
@@ -784,7 +788,7 @@ Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**requestOptions:** `ProcessorRun.RequestOptions`
+**requestOptions:** `Edit.RequestOptions`
 
 </dd>
 </dl>
@@ -795,7 +799,9 @@ Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 </dl>
 </details>
 
-<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">delete</a>(id) -> Extend.ProcessorRunDeleteResponse</code></summary>
+## Workflow
+
+<details><summary><code>client.workflow.<a href="/src/api/resources/workflow/client/Client.ts">create</a>({ ...params }) -> Extend.WorkflowCreateResponse</code></summary>
 <dl>
 <dd>
 
@@ -807,9 +813,9 @@ Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-Delete a processor run and all associated data from Extend. This operation is permanent and cannot be undone.
+Create a new workflow in Extend. Workflows are sequences of steps that process files and data in a specific order to achieve a desired outcome.
 
-This endpoint can be used if you'd like to manage data retention on your own rather than automated data retention policies. Or make one-off deletions for your downstream customers.
+This endpoint will create a new workflow in Extend, which can then be configured and deployed. Typically, workflows are created from our UI, however this endpoint can be used to create workflows programmatically. Configuration of the flow still needs to be done in the dashboard.
 
 </dd>
 </dl>
@@ -825,7 +831,9 @@ This endpoint can be used if you'd like to manage data retention on your own rat
 <dd>
 
 ```typescript
-await client.processorRun.delete("processor_run_id_here");
+await client.workflow.create({
+    name: "Invoice Processing",
+});
 ```
 
 </dd>
@@ -841,11 +849,7 @@ await client.processorRun.delete("processor_run_id_here");
 <dl>
 <dd>
 
-**id:** `string`
-
-The ID of the processor run to delete.
-
-Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
+**request:** `Extend.WorkflowCreateRequest`
 
 </dd>
 </dl>
@@ -853,7 +857,7 @@ Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**requestOptions:** `ProcessorRun.RequestOptions`
+**requestOptions:** `Workflow.RequestOptions`
 
 </dd>
 </dl>
@@ -864,7 +868,9 @@ Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 </dl>
 </details>
 
-<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">cancel</a>(id) -> Extend.ProcessorRunCancelResponse</code></summary>
+## WorkflowRun
+
+<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">list</a>({ ...params }) -> Extend.WorkflowRunListResponse</code></summary>
 <dl>
 <dd>
 
@@ -876,9 +882,7 @@ Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-Cancel a running processor run by its ID. This endpoint allows you to stop a processor run that is currently in progress.
-
-Note: Only processor runs with a status of `"PROCESSING"` can be cancelled. Processor runs that have already completed, failed, or been cancelled cannot be cancelled again.
+List runs of a Workflow. Workflows are sequences of steps that process files and data in a specific order to achieve a desired outcome. A WorkflowRun represents a single execution of a workflow against a file.
 
 </dd>
 </dl>
@@ -894,7 +898,16 @@ Note: Only processor runs with a status of `"PROCESSING"` can be cancelled. Proc
 <dd>
 
 ```typescript
-await client.processorRun.cancel("processor_run_id_here");
+await client.workflowRun.list({
+    status: "PENDING",
+    workflowId: "workflowId",
+    batchId: "batchId",
+    fileNameContains: "fileNameContains",
+    sortBy: "updatedAt",
+    sortDir: "asc",
+    nextPageToken: "xK9mLPqRtN3vS8wF5hB2cQ==:zWvUxYjM4nKpL7aDgE9HbTcR2mAyX3/Q+CNkfBSw1dZ=",
+    maxPageSize: 1,
+});
 ```
 
 </dd>
@@ -910,11 +923,7 @@ await client.processorRun.cancel("processor_run_id_here");
 <dl>
 <dd>
 
-**id:** `string`
-
-The unique identifier for the processor run to cancel.
-
-Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
+**request:** `Extend.WorkflowRunListRequest`
 
 </dd>
 </dl>
@@ -922,7 +931,7 @@ Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**requestOptions:** `ProcessorRun.RequestOptions`
+**requestOptions:** `WorkflowRun.RequestOptions`
 
 </dd>
 </dl>
@@ -933,9 +942,7 @@ Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 </dl>
 </details>
 
-## Processor
-
-<details><summary><code>client.processor.<a href="/src/api/resources/processor/client/Client.ts">list</a>({ ...params }) -> Extend.ListProcessorsResponse</code></summary>
+<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">create</a>({ ...params }) -> Extend.WorkflowRunCreateResponse</code></summary>
 <dl>
 <dd>
 
@@ -947,7 +954,7 @@ Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-List all processors in your organization
+Run a Workflow with files. A Workflow is a sequence of steps that process files and data in a specific order to achieve a desired outcome. A WorkflowRun will be created for each file processed. A WorkflowRun represents a single execution of a workflow against a file.
 
 </dd>
 </dl>
@@ -963,12 +970,8 @@ List all processors in your organization
 <dd>
 
 ```typescript
-await client.processor.list({
-    type: "EXTRACT",
-    nextPageToken: "nextPageToken",
-    maxPageSize: 1,
-    sortBy: "createdAt",
-    sortDir: "asc",
+await client.workflowRun.create({
+    workflowId: "workflow_id_here",
 });
 ```
 
@@ -985,7 +988,7 @@ await client.processor.list({
 <dl>
 <dd>
 
-**request:** `Extend.ProcessorListRequest`
+**request:** `Extend.WorkflowRunCreateRequest`
 
 </dd>
 </dl>
@@ -993,7 +996,7 @@ await client.processor.list({
 <dl>
 <dd>
 
-**requestOptions:** `Processor.RequestOptions`
+**requestOptions:** `WorkflowRun.RequestOptions`
 
 </dd>
 </dl>
@@ -1004,7 +1007,7 @@ await client.processor.list({
 </dl>
 </details>
 
-<details><summary><code>client.processor.<a href="/src/api/resources/processor/client/Client.ts">create</a>({ ...params }) -> Extend.ProcessorCreateResponse</code></summary>
+<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">get</a>(workflowRunId) -> Extend.WorkflowRunGetResponse</code></summary>
 <dl>
 <dd>
 
@@ -1016,7 +1019,7 @@ await client.processor.list({
 <dl>
 <dd>
 
-Create a new processor in Extend, optionally cloning from an existing processor
+Once a workflow has been run, you can check the status and output of a specific WorkflowRun.
 
 </dd>
 </dl>
@@ -1032,10 +1035,7 @@ Create a new processor in Extend, optionally cloning from an existing processor
 <dd>
 
 ```typescript
-await client.processor.create({
-    name: "My Processor Name",
-    type: "EXTRACT",
-});
+await client.workflowRun.get("workflow_run_id_here");
 ```
 
 </dd>
@@ -1051,7 +1051,11 @@ await client.processor.create({
 <dl>
 <dd>
 
-**request:** `Extend.ProcessorCreateRequest`
+**workflowRunId:** `string`
+
+The ID of the WorkflowRun that was outputted after a Workflow was run through the API.
+
+Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
 
 </dd>
 </dl>
@@ -1059,7 +1063,7 @@ await client.processor.create({
 <dl>
 <dd>
 
-**requestOptions:** `Processor.RequestOptions`
+**requestOptions:** `WorkflowRun.RequestOptions`
 
 </dd>
 </dl>
@@ -1070,7 +1074,7 @@ await client.processor.create({
 </dl>
 </details>
 
-<details><summary><code>client.processor.<a href="/src/api/resources/processor/client/Client.ts">update</a>(id, { ...params }) -> Extend.ProcessorUpdateResponse</code></summary>
+<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">update</a>(workflowRunId, { ...params }) -> Extend.WorkflowRunUpdateResponse</code></summary>
 <dl>
 <dd>
 
@@ -1082,7 +1086,7 @@ await client.processor.create({
 <dl>
 <dd>
 
-Update an existing processor in Extend
+You can update the name and metadata of an in progress WorkflowRun at any time using this endpoint.
 
 </dd>
 </dl>
@@ -1098,7 +1102,7 @@ Update an existing processor in Extend
 <dd>
 
 ```typescript
-await client.processor.update("processor_id_here");
+await client.workflowRun.update("workflow_run_id_here");
 ```
 
 </dd>
@@ -1114,11 +1118,11 @@ await client.processor.update("processor_id_here");
 <dl>
 <dd>
 
-**id:** `string`
+**workflowRunId:** `string`
 
-The ID of the processor to update.
+The ID of the WorkflowRun. This ID will start with "workflow_run". This ID can be found in the API response when creating a Workflow Run, or in the "history" tab of a workflow on the Extend platform.
 
-Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
+Example: `"workflow_run_8k9m-xyzAB_Pqrst-Nvw4"`
 
 </dd>
 </dl>
@@ -1126,7 +1130,7 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**request:** `Extend.ProcessorUpdateRequest`
+**request:** `Extend.WorkflowRunUpdateRequest`
 
 </dd>
 </dl>
@@ -1134,7 +1138,7 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**requestOptions:** `Processor.RequestOptions`
+**requestOptions:** `WorkflowRun.RequestOptions`
 
 </dd>
 </dl>
@@ -1145,9 +1149,7 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 </dl>
 </details>
 
-## ProcessorVersion
-
-<details><summary><code>client.processorVersion.<a href="/src/api/resources/processorVersion/client/Client.ts">get</a>(processorId, processorVersionId) -> Extend.ProcessorVersionGetResponse</code></summary>
+<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">delete</a>(workflowRunId) -> Extend.WorkflowRunDeleteResponse</code></summary>
 <dl>
 <dd>
 
@@ -1159,7 +1161,9 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-Retrieve a specific version of a processor in Extend
+Delete a workflow run and all associated data from Extend. This operation is permanent and cannot be undone.
+
+This endpoint can be used if you'd like to manage data retention on your own rather than automated data retention policies. Or make one-off deletions for your downstream customers.
 
 </dd>
 </dl>
@@ -1175,7 +1179,7 @@ Retrieve a specific version of a processor in Extend
 <dd>
 
 ```typescript
-await client.processorVersion.get("processor_id_here", "processor_version_id_here");
+await client.workflowRun.delete("workflow_run_id_here");
 ```
 
 </dd>
@@ -1191,23 +1195,11 @@ await client.processorVersion.get("processor_id_here", "processor_version_id_her
 <dl>
 <dd>
 
-**processorId:** `string`
-
-The ID of the processor.
-
-Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
-
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**processorVersionId:** `string`
+**workflowRunId:** `string`
 
-The ID of the specific processor version to retrieve.
+The ID of the workflow run to delete.
 
-Example: `"dpv_QYk6jgHA_8CsO8rVWhyNC"`
+Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
 
 </dd>
 </dl>
@@ -1215,7 +1207,7 @@ Example: `"dpv_QYk6jgHA_8CsO8rVWhyNC"`
 <dl>
 <dd>
 
-**requestOptions:** `ProcessorVersion.RequestOptions`
+**requestOptions:** `WorkflowRun.RequestOptions`
 
 </dd>
 </dl>
@@ -1226,7 +1218,7 @@ Example: `"dpv_QYk6jgHA_8CsO8rVWhyNC"`
 </dl>
 </details>
 
-<details><summary><code>client.processorVersion.<a href="/src/api/resources/processorVersion/client/Client.ts">list</a>(id) -> Extend.ProcessorVersionListResponse</code></summary>
+<details><summary><code>client.workflowRun.<a href="/src/api/resources/workflowRun/client/Client.ts">cancel</a>(workflowRunId) -> Extend.WorkflowRunCancelResponse</code></summary>
 <dl>
 <dd>
 
@@ -1238,10 +1230,9 @@ Example: `"dpv_QYk6jgHA_8CsO8rVWhyNC"`
 <dl>
 <dd>
 
-This endpoint allows you to fetch all versions of a given processor, including the current `draft` version.
+Cancel a running workflow run by its ID. This endpoint allows you to stop a workflow run that is currently in progress.
 
-Versions are typically returned in descending order of creation (newest first), but this should be confirmed in the actual implementation.
-The `draft` version is the latest unpublished version of the processor, which can be published to create a new version. It might not have any changes from the last published version.
+Note: Only workflow runs with a status of `PROCESSING` or `PENDING` can be cancelled. Workflow runs that are completed, failed, in review, rejected, or already cancelled cannot be cancelled.
 
 </dd>
 </dl>
@@ -1257,7 +1248,7 @@ The `draft` version is the latest unpublished version of the processor, which ca
 <dd>
 
 ```typescript
-await client.processorVersion.list("processor_id_here");
+await client.workflowRun.cancel("workflow_run_id_here");
 ```
 
 </dd>
@@ -1273,11 +1264,11 @@ await client.processorVersion.list("processor_id_here");
 <dl>
 <dd>
 
-**id:** `string`
+**workflowRunId:** `string`
 
-The ID of the processor to retrieve versions for.
+The ID of the workflow run to cancel.
 
-Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
+Example: `"workflow_run_xKm9pNv3qWsY_jL2tR5Dh"`
 
 </dd>
 </dl>
@@ -1285,7 +1276,7 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**requestOptions:** `ProcessorVersion.RequestOptions`
+**requestOptions:** `WorkflowRun.RequestOptions`
 
 </dd>
 </dl>
@@ -1296,7 +1287,9 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 </dl>
 </details>
 
-<details><summary><code>client.processorVersion.<a href="/src/api/resources/processorVersion/client/Client.ts">create</a>(id, { ...params }) -> Extend.ProcessorVersionCreateResponse</code></summary>
+## WorkflowRunOutput
+
+<details><summary><code>client.workflowRunOutput.<a href="/src/api/resources/workflowRunOutput/client/Client.ts">update</a>(workflowRunId, outputId, { ...params }) -> Extend.WorkflowRunOutputUpdateResponse</code></summary>
 <dl>
 <dd>
 
@@ -1308,9 +1301,11 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-This endpoint allows you to publish a new version of an existing processor. Publishing a new version creates a snapshot of the processor's current configuration and makes it available for use in workflows.
+Use this endpoint to submit corrected outputs for a WorkflowRun for future processor evaluation and tuning in Extend.
 
-Publishing a new version does not automatically update existing workflows using this processor. You may need to manually update workflows to use the new version if desired.
+If you are using our Human-in-the-loop workflow review, then we already will be collecting your operator submitted corrections. However, if you are receiving data via the API without human review, there could be incorrect outputs that you would like to correct for future usage in evaluation and tuning within the Extend platform. This endpoint allows you to submit corrected outputs for a WorkflowRun, by providing the correct output for a given output ID.
+
+The output ID, would be found in a given entry within the outputs arrays of a Workflow Run payload. The ID would look something like `dpr_gwkZZNRrPgkjcq0y-***`.
 
 </dd>
 </dl>
@@ -1326,8 +1321,12 @@ Publishing a new version does not automatically update existing workflows using
 <dd>
 
 ```typescript
-await client.processorVersion.create("processor_id_here", {
-    releaseType: "major",
+await client.workflowRunOutput.update("workflow_run_id_here", "output_id_here", {
+    reviewedOutput: {
+        value: {
+            key: "value",
+        },
+    },
 });
 ```
 
@@ -1344,11 +1343,15 @@ await client.processorVersion.create("processor_id_here", {
 <dl>
 <dd>
 
-**id:** `string`
+**workflowRunId:** `string`
 
-The ID of the processor to publish a new version for.
+</dd>
+</dl>
 
-Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
+<dl>
+<dd>
+
+**outputId:** `string`
 
 </dd>
 </dl>
@@ -1356,7 +1359,7 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**request:** `Extend.ProcessorVersionCreateRequest`
+**request:** `Extend.WorkflowRunOutputUpdateRequest`
 
 </dd>
 </dl>
@@ -1364,7 +1367,7 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**requestOptions:** `ProcessorVersion.RequestOptions`
+**requestOptions:** `WorkflowRunOutput.RequestOptions`
 
 </dd>
 </dl>
@@ -1375,9 +1378,9 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 </dl>
 </details>
 
-## ParserRun
+## BatchWorkflowRun
 
-<details><summary><code>client.parserRun.<a href="/src/api/resources/parserRun/client/Client.ts">get</a>(id, { ...params }) -> Extend.ParserRunGetResponse</code></summary>
+<details><summary><code>client.batchWorkflowRun.<a href="/src/api/resources/batchWorkflowRun/client/Client.ts">create</a>({ ...params }) -> Extend.BatchWorkflowRunCreateResponse</code></summary>
 <dl>
 <dd>
 
@@ -1389,16 +1392,23 @@ Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-Retrieve the status and results of a parser run.
+This endpoint allows you to efficiently initiate large batches of workflow runs in a single request (up to 1,000 in a single request, but you can queue up multiple batches in rapid succession). It accepts an array of inputs, each containing a file and metadata pair. The primary use case for this endpoint is for doing large bulk runs of >1000 files at a time that can process over the course of a few hours without needing to manage rate limits that would likely occur using the primary run endpoint.
 
-Use this endpoint to get results for a parser run that has already completed, or to check on the status of an asynchronous parser run initiated via the [Parse File Asynchronously](https://docs.extend.ai/2025-04-21/developers/api-reference/parse-endpoints/parse-file-async) endpoint.
+Unlike the single [Run Workflow](/developers/api-reference/workflow-endpoints/run-workflow) endpoint which returns the details of the created workflow runs immediately, this batch endpoint returns a `batchId`.
 
-If parsing is still in progress, you'll receive a response with just the status. Once complete, you'll receive the full parsed content in the response.
+Our recommended usage pattern is to integrate with [Webhooks](/product/webhooks/configuration) for consuming results, using the `metadata` and `batchId` to match up results to the original inputs in your downstream systems. However, you can integrate in a polling mechanism by using a combination of the [List Workflow Runs](https://docs.extend.ai/2025-04-21/developers/api-reference/workflow-endpoints/list-workflow-runs) endpoint to fetch all runs via a batch, and then [Get Workflow Run](https://docs.extend.ai/2025-04-21/developers/api-reference/workflow-endpoints/get-workflow-run) to fetch the full outputs each run.
 
-</dd>
-</dl>
-</dd>
-</dl>
+**Priority:** All workflow runs created through this batch endpoint are automatically assigned a priority of 90.
+
+**Processing and Monitoring:**
+Upon successful submission, the endpoint returns a `batchId`. The individual workflow runs are then queued for processing.
+
+- **Monitoring:** Track the progress and consume results of individual runs using [Webhooks](/product/webhooks/configuration). Subscribe to events like `workflow_run.completed`, `workflow_run.failed`, etc. The webhook payload for these events will include the corresponding `batchId` and the `metadata` you provided for each input.
+- **Fetching Results:** You can also use the [List Workflow Runs](https://docs.extend.ai/2025-04-21/developers/api-reference/workflow-endpoints/list-workflow-runs) endpoint and filter using the `batchId` query param.
+  </dd>
+  </dl>
+  </dd>
+  </dl>
 
 #### 🔌 Usage
 
@@ -1409,8 +1419,9 @@ If parsing is still in progress, you'll receive a response with just the status.
 <dd>
 
 ```typescript
-await client.parserRun.get("parser_run_id_here", {
-    responseType: "json",
+await client.batchWorkflowRun.create({
+    workflowId: "workflow_id_here",
+    inputs: [{}],
 });
 ```
 
@@ -1427,19 +1438,7 @@ await client.parserRun.get("parser_run_id_here", {
 <dl>
 <dd>
 
-**id:** `string`
-
-The unique identifier for the parser run.
-
-Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
-
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request:** `Extend.ParserRunGetRequest`
+**request:** `Extend.BatchWorkflowRunCreateRequest`
 
 </dd>
 </dl>
@@ -1447,7 +1446,7 @@ Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-**requestOptions:** `ParserRun.RequestOptions`
+**requestOptions:** `BatchWorkflowRun.RequestOptions`
 
 </dd>
 </dl>
@@ -1458,7 +1457,9 @@ Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 </dl>
 </details>
 
-<details><summary><code>client.parserRun.<a href="/src/api/resources/parserRun/client/Client.ts">delete</a>(id) -> Extend.ParserRunDeleteResponse</code></summary>
+## BatchProcessorRun
+
+<details><summary><code>client.batchProcessorRun.<a href="/src/api/resources/batchProcessorRun/client/Client.ts">get</a>(id) -> Extend.BatchProcessorRunGetResponse</code></summary>
 <dl>
 <dd>
 
@@ -1470,9 +1471,7 @@ Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-Delete a parser run and all associated data from Extend. This operation is permanent and cannot be undone.
-
-This endpoint can be used if you'd like to manage data retention on your own rather than automated data retention policies. Or make one-off deletions for your downstream customers.
+Retrieve details about a batch processor run, including evaluation runs
 
 </dd>
 </dl>
@@ -1488,7 +1487,7 @@ This endpoint can be used if you'd like to manage data retention on your own rat
 <dd>
 
 ```typescript
-await client.parserRun.delete("parser_run_id_here");
+await client.batchProcessorRun.get("batch_processor_run_id_here");
 ```
 
 </dd>
@@ -1506,9 +1505,9 @@ await client.parserRun.delete("parser_run_id_here");
 
 **id:** `string`
 
-The ID of the parser run to delete.
+The unique identifier of the batch processor run to retrieve. The ID will always start with "bpr\_".
 
-Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
+Example: `"bpr_Xj8mK2pL9nR4vT7qY5wZ"`
 
 </dd>
 </dl>
@@ -1516,7 +1515,7 @@ Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-**requestOptions:** `ParserRun.RequestOptions`
+**requestOptions:** `BatchProcessorRun.RequestOptions`
 
 </dd>
 </dl>
@@ -1527,9 +1526,9 @@ Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 </dl>
 </details>
 
-## Edit
+## EvaluationSet
 
-<details><summary><code>client.edit.<a href="/src/api/resources/edit/client/Client.ts">create</a>({ ...params }) -> Extend.EditRun</code></summary>
+<details><summary><code>client.evaluationSet.<a href="/src/api/resources/evaluationSet/client/Client.ts">list</a>({ ...params }) -> Extend.EvaluationSetListResponse</code></summary>
 <dl>
 <dd>
 
@@ -1541,8 +1540,9 @@ Example: `"parser_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-Edit and manipulate PDF documents by detecting and filling form fields.
-This is a synchronous endpoint that will wait for the edit operation to complete (up to 5 minutes) before returning results. For longer operations, use the [Edit File Async](/developers/api-reference/edit-endpoints/edit-file-async) endpoint.
+List evaluation sets in your account. You can use the `processorId` parameter to filter evaluation sets by processor.
+
+This endpoint returns a paginated response. You can use the `nextPageToken` to fetch subsequent results.
 
 </dd>
 </dl>
@@ -1558,8 +1558,12 @@ This is a synchronous endpoint that will wait for the edit operation to complete
 <dd>
 
 ```typescript
-await client.edit.create({
-    file: {},
+await client.evaluationSet.list({
+    processorId: "processor_id_here",
+    sortBy: "updatedAt",
+    sortDir: "asc",
+    nextPageToken: "xK9mLPqRtN3vS8wF5hB2cQ==:zWvUxYjM4nKpL7aDgE9HbTcR2mAyX3/Q+CNkfBSw1dZ=",
+    maxPageSize: 1,
 });
 ```
 
@@ -1576,7 +1580,7 @@ await client.edit.create({
 <dl>
 <dd>
 
-**request:** `Extend.EditCreateRequest`
+**request:** `Extend.EvaluationSetListRequest`
 
 </dd>
 </dl>
@@ -1584,7 +1588,7 @@ await client.edit.create({
 <dl>
 <dd>
 
-**requestOptions:** `Edit.RequestOptions`
+**requestOptions:** `EvaluationSet.RequestOptions`
 
 </dd>
 </dl>
@@ -1595,7 +1599,7 @@ await client.edit.create({
 </dl>
 </details>
 
-<details><summary><code>client.edit.<a href="/src/api/resources/edit/client/Client.ts">createAsync</a>({ ...params }) -> Extend.EditRunStatus</code></summary>
+<details><summary><code>client.evaluationSet.<a href="/src/api/resources/evaluationSet/client/Client.ts">create</a>({ ...params }) -> Extend.EvaluationSetCreateResponse</code></summary>
 <dl>
 <dd>
 
@@ -1607,19 +1611,14 @@ await client.edit.create({
 <dl>
 <dd>
 
-Edit and manipulate PDF documents **asynchronously** by filling forms, adding/modifying text fields, and applying structured changes.
-
-The Edit Async endpoint allows you to convert and edit documents asynchronously and get an edit run ID that can be used to check status and retrieve results with the [Get Edit Run](/developers/api-reference/edit-endpoints/get-edit-run) endpoint.
+Evaluation sets are collections of files and expected outputs that are used to evaluate the performance of a given processor in Extend. This endpoint will create a new evaluation set in Extend, which items can be added to using the [Create Evaluation Set Item](https://docs.extend.ai/2025-04-21/developers/api-reference/evaluation-set-endpoints/create-evaluation-set-item) endpoint.
 
-This is useful for:
+Note: it is not necessary to create an evaluation set via API. You can also create an evaluation set via the Extend dashboard and take the ID from there.
 
-- Large files that may take longer to process
-- Avoiding timeout issues with synchronous editing
-- Processing multiple files in parallel
-  </dd>
-  </dl>
-  </dd>
-  </dl>
+</dd>
+</dl>
+</dd>
+</dl>
 
 #### 🔌 Usage
 
@@ -1630,8 +1629,10 @@ This is useful for:
 <dd>
 
 ```typescript
-await client.edit.createAsync({
-    file: {},
+await client.evaluationSet.create({
+    name: "My Evaluation Set",
+    description: "My Evaluation Set Description",
+    processorId: "processor_id_here",
 });
 ```
 
@@ -1648,7 +1649,7 @@ await client.edit.createAsync({
 <dl>
 <dd>
 
-**request:** `Extend.EditCreateAsyncRequest`
+**request:** `Extend.EvaluationSetCreateRequest`
 
 </dd>
 </dl>
@@ -1656,7 +1657,7 @@ await client.edit.createAsync({
 <dl>
 <dd>
 
-**requestOptions:** `Edit.RequestOptions`
+**requestOptions:** `EvaluationSet.RequestOptions`
 
 </dd>
 </dl>
@@ -1667,7 +1668,7 @@ await client.edit.createAsync({
 </dl>
 </details>
 
-<details><summary><code>client.edit.<a href="/src/api/resources/edit/client/Client.ts">get</a>(id) -> Extend.EditGetResponse</code></summary>
+<details><summary><code>client.evaluationSet.<a href="/src/api/resources/evaluationSet/client/Client.ts">get</a>(id) -> Extend.EvaluationSetGetResponse</code></summary>
 <dl>
 <dd>
 
@@ -1679,11 +1680,7 @@ await client.edit.createAsync({
 <dl>
 <dd>
 
-Retrieve the status and results of an edit run.
-
-Use this endpoint to get results for an edit run that has already completed, or to check on the status of an asynchronous edit run initiated via the [Edit File Asynchronously](/developers/api-reference/edit-endpoints/edit-file-async) endpoint.
-
-If editing is still in progress, you'll receive a response with just the status. Once complete, you'll receive the full edited file information in the response.
+Retrieve a specific evaluation set by ID. This returns an evaluation set object, but does not include the items in the evaluation set. You can use the [List Evaluation Set Items](https://docs.extend.ai/2025-04-21/developers/api-reference/evaluation-set-endpoints/list-evaluation-set-items) endpoint to get the items in an evaluation set.
 
 </dd>
 </dl>
@@ -1699,7 +1696,7 @@ If editing is still in progress, you'll receive a response with just the status.
 <dd>
 
 ```typescript
-await client.edit.get("edit_run_id_here");
+await client.evaluationSet.get("evaluation_set_id_here");
 ```
 
 </dd>
@@ -1717,9 +1714,9 @@ await client.edit.get("edit_run_id_here");
 
 **id:** `string`
 
-The unique identifier for the edit run.
+The ID of the evaluation set to retrieve.
 
-Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
+Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
 
 </dd>
 </dl>
@@ -1727,7 +1724,7 @@ Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-**requestOptions:** `Edit.RequestOptions`
+**requestOptions:** `EvaluationSet.RequestOptions`
 
 </dd>
 </dl>
@@ -1738,7 +1735,9 @@ Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 </dl>
 </details>
 
-<details><summary><code>client.edit.<a href="/src/api/resources/edit/client/Client.ts">delete</a>(id) -> Extend.EditDeleteResponse</code></summary>
+## EvaluationSetItem
+
+<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">list</a>(id, { ...params }) -> Extend.EvaluationSetItemListResponse</code></summary>
 <dl>
 <dd>
 
@@ -1750,9 +1749,9 @@ Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-Delete an edit run and all associated data from Extend. This operation is permanent and cannot be undone.
+List all items in a specific evaluation set. Evaluation set items are the individual files and expected outputs that are used to evaluate the performance of a given processor in Extend.
 
-This endpoint can be used if you'd like to manage data retention on your own rather than relying on automated data retention policies, or to make one-off deletions for your downstream customers.
+This endpoint returns a paginated response. You can use the `nextPageToken` to fetch subsequent results.
 
 </dd>
 </dl>
@@ -1768,7 +1767,12 @@ This endpoint can be used if you'd like to manage data retention on your own rat
 <dd>
 
 ```typescript
-await client.edit.delete("edit_run_id_here");
+await client.evaluationSetItem.list("evaluation_set_id_here", {
+    sortBy: "updatedAt",
+    sortDir: "asc",
+    nextPageToken: "xK9mLPqRtN3vS8wF5hB2cQ==:zWvUxYjM4nKpL7aDgE9HbTcR2mAyX3/Q+CNkfBSw1dZ=",
+    maxPageSize: 1,
+});
 ```
 
 </dd>
@@ -1786,9 +1790,9 @@ await client.edit.delete("edit_run_id_here");
 
 **id:** `string`
 
-The ID of the edit run to delete.
+The ID of the evaluation set to retrieve items for.
 
-Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
+Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
 
 </dd>
 </dl>
@@ -1796,7 +1800,15 @@ Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-**requestOptions:** `Edit.RequestOptions`
+**request:** `Extend.EvaluationSetItemListRequest`
+
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `EvaluationSetItem.RequestOptions`
 
 </dd>
 </dl>
@@ -1807,9 +1819,7 @@ Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 </dl>
 </details>
 
-## File
-
-<details><summary><code>client.file.<a href="/src/api/resources/file/client/Client.ts">list</a>({ ...params }) -> Extend.FileListResponse</code></summary>
+<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">create</a>({ ...params }) -> Extend.EvaluationSetItemCreateResponse</code></summary>
 <dl>
 <dd>
 
@@ -1821,12 +1831,25 @@ Example: `"edit_run_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-List files in your account. Files represent documents that have been uploaded to Extend. This endpoint returns a paginated response. You can use the `nextPageToken` to fetch subsequent results.
+Evaluation set items are the individual files and expected outputs that are used to evaluate the performance of a given processor in Extend. This endpoint will create a new evaluation set item in Extend, which will be used during an evaluation run.
 
-</dd>
-</dl>
-</dd>
-</dl>
+Best Practices for Outputs in Evaluation Sets:
+
+- **Configure First, Output Later**
+    - Always create and finalize your processor configuration before creating evaluation sets
+    - Field IDs in outputs must match those defined in your processor configuration
+- **Type Consistency**
+    - Ensure output types exactly match your processor configuration
+    - For example, if a field is configured as "currency", don't submit a simple number value
+- **Field IDs**
+    - Use the exact field IDs from your processor configuration
+    - Create your own semantic IDs instead in the configs for each field/type instead of using the generated ones
+- **Value**
+    - Remember that all results are inside the value key of a result object, except the values within nested structures.
+      </dd>
+      </dl>
+      </dd>
+      </dl>
 
 #### 🔌 Usage
 
@@ -1837,11 +1860,14 @@ List files in your account. Files represent documents that have been uploaded to
 <dd>
 
 ```typescript
-await client.file.list({
-    nameContains: "nameContains",
-    sortDir: "asc",
-    nextPageToken: "xK9mLPqRtN3vS8wF5hB2cQ==:zWvUxYjM4nKpL7aDgE9HbTcR2mAyX3/Q+CNkfBSw1dZ=",
-    maxPageSize: 1,
+await client.evaluationSetItem.create({
+    evaluationSetId: "evaluation_set_id_here",
+    fileId: "file_id_here",
+    expectedOutput: {
+        value: {
+            key: "value",
+        },
+    },
 });
 ```
 
@@ -1858,7 +1884,7 @@ await client.file.list({
 <dl>
 <dd>
 
-**request:** `Extend.FileListRequest`
+**request:** `Extend.EvaluationSetItemCreateRequest`
 
 </dd>
 </dl>
@@ -1866,7 +1892,7 @@ await client.file.list({
 <dl>
 <dd>
 
-**requestOptions:** `File_.RequestOptions`
+**requestOptions:** `EvaluationSetItem.RequestOptions`
 
 </dd>
 </dl>
@@ -1877,7 +1903,7 @@ await client.file.list({
 </dl>
 </details>
 
-<details><summary><code>client.file.<a href="/src/api/resources/file/client/Client.ts">get</a>(id, { ...params }) -> Extend.FileGetResponse</code></summary>
+<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">update</a>(id, { ...params }) -> Extend.EvaluationSetItemUpdateResponse</code></summary>
 <dl>
 <dd>
 
@@ -1889,7 +1915,7 @@ await client.file.list({
 <dl>
 <dd>
 
-Fetch a file by its ID to obtain additional details and the raw file content.
+If you need to change the expected output for a given evaluation set item, you can use this endpoint to update the item. This can be useful if you need to correct an error in the expected output or if the output of the processor has changed.
 
 </dd>
 </dl>
@@ -1905,10 +1931,12 @@ Fetch a file by its ID to obtain additional details and the raw file content.
 <dd>
 
 ```typescript
-await client.file.get("file_id_here", {
-    rawText: true,
-    markdown: true,
-    html: true,
+await client.evaluationSetItem.update("evaluation_set_item_id_here", {
+    expectedOutput: {
+        value: {
+            key: "value",
+        },
+    },
 });
 ```
 
@@ -1927,9 +1955,9 @@ await client.file.get("file_id_here", {
 
 **id:** `string`
 
-Extend's ID for the file. It will always start with `"file_"`. This ID is returned when creating a new File, or the value on the `fileId` field in a WorkflowRun.
+The ID of the evaluation set item to update.
 
-Example: `"file_Xj8mK2pL9nR4vT7qY5wZ"`
+Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
 
 </dd>
 </dl>
@@ -1937,7 +1965,7 @@ Example: `"file_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**request:** `Extend.FileGetRequest`
+**request:** `Extend.EvaluationSetItemUpdateRequest`
 
 </dd>
 </dl>
@@ -1945,7 +1973,7 @@ Example: `"file_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**requestOptions:** `File_.RequestOptions`
+**requestOptions:** `EvaluationSetItem.RequestOptions`
 
 </dd>
 </dl>
@@ -1956,7 +1984,7 @@ Example: `"file_Xj8mK2pL9nR4vT7qY5wZ"`
 </dl>
 </details>
 
-<details><summary><code>client.file.<a href="/src/api/resources/file/client/Client.ts">delete</a>(id) -> Extend.FileDeleteResponse</code></summary>
+<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">delete</a>(id) -> Extend.EvaluationSetItemDeleteResponse</code></summary>
 <dl>
 <dd>
 
@@ -1968,9 +1996,9 @@ Example: `"file_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-Delete a file and all associated data from Extend. This operation is permanent and cannot be undone.
+Delete an evaluation set item from an evaluation set. This operation is permanent and cannot be undone.
 
-This endpoint can be used if you'd like to manage data retention on your own rather than automated data retention policies. Or make one-off deletions for your downstream customers.
+This endpoint can be used to remove individual items from an evaluation set when they are no longer needed or if they were added in error.
 
 </dd>
 </dl>
@@ -1986,7 +2014,7 @@ This endpoint can be used if you'd like to manage data retention on your own rat
 <dd>
 
 ```typescript
-await client.file.delete("file_id_here");
+await client.evaluationSetItem.delete("evaluation_set_item_id_here");
 ```
 
 </dd>
@@ -2004,9 +2032,9 @@ await client.file.delete("file_id_here");
 
 **id:** `string`
 
-The ID of the file to delete.
+The ID of the evaluation set item to delete.
 
-Example: `"file_xK9mLPqRtN3vS8wF5hB2cQ"`
+Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
 
 </dd>
 </dl>
@@ -2014,7 +2042,7 @@ Example: `"file_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-**requestOptions:** `File_.RequestOptions`
+**requestOptions:** `EvaluationSetItem.RequestOptions`
 
 </dd>
 </dl>
@@ -2025,7 +2053,7 @@ Example: `"file_xK9mLPqRtN3vS8wF5hB2cQ"`
 </dl>
 </details>
 
-<details><summary><code>client.file.<a href="/src/api/resources/file/client/Client.ts">upload</a>(file) -> Extend.FileUploadResponse</code></summary>
+<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">createBatch</a>({ ...params }) -> Extend.EvaluationSetItemCreateBatchResponse</code></summary>
 <dl>
 <dd>
 
@@ -2037,15 +2065,9 @@ Example: `"file_xK9mLPqRtN3vS8wF5hB2cQ"`
 <dl>
 <dd>
 
-Upload and create a new file in Extend.
-
-This endpoint accepts file contents and registers them as a File in Extend, which can be used for [running workflows](https://docs.extend.ai/2025-04-21/developers/api-reference/workflow-endpoints/run-workflow), [creating evaluation set items](https://docs.extend.ai/2025-04-21/developers/api-reference/evaluation-set-endpoints/bulk-create-evaluation-set-items), [parsing](https://docs.extend.ai/2025-04-21/developers/api-reference/parse-endpoints/parse-file), etc.
-
-If an uploaded file is detected as a Word or PowerPoint document, it will be automatically converted to a PDF.
-
-Supported file types can be found [here](/product/general/supported-file-types).
+If you have a large number of files that you need to add to an evaluation set, you can use this endpoint to create multiple evaluation set items at once. This can be useful if you have a large dataset that you need to evaluate the performance of a processor against.
 
-This endpoint requires multipart form encoding. Most HTTP clients will handle this encoding automatically (see the examples).
+Note: you still need to create each File first using the file API.
 
 </dd>
 </dl>
@@ -2061,7 +2083,19 @@ This endpoint requires multipart form encoding. Most HTTP clients will handle th
 <dd>
 
 ```typescript
-await client.file.upload(createReadStream("path/to/file"));
+await client.evaluationSetItem.createBatch({
+    evaluationSetId: "evaluation_set_id_here",
+    items: [
+        {
+            fileId: "file_id_here",
+            expectedOutput: {
+                value: {
+                    key: "value",
+                },
+            },
+        },
+    ],
+});
 ```
 
 </dd>
@@ -2077,7 +2111,7 @@ await client.file.upload(createReadStream("path/to/file"));
 <dl>
 <dd>
 
-**file:** `File | fs.ReadStream | Blob`
+**request:** `Extend.EvaluationSetItemCreateBatchRequest`
 
 </dd>
 </dl>
@@ -2085,7 +2119,7 @@ await client.file.upload(createReadStream("path/to/file"));
 <dl>
 <dd>
 
-**requestOptions:** `File_.RequestOptions`
+**requestOptions:** `EvaluationSetItem.RequestOptions`
 
 </dd>
 </dl>
@@ -2096,9 +2130,9 @@ await client.file.upload(createReadStream("path/to/file"));
 </dl>
 </details>
 
-## EvaluationSet
+## ProcessorRun
 
-<details><summary><code>client.evaluationSet.<a href="/src/api/resources/evaluationSet/client/Client.ts">list</a>({ ...params }) -> Extend.EvaluationSetListResponse</code></summary>
+<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">list</a>({ ...params }) -> Extend.ProcessorRunListResponse</code></summary>
 <dl>
 <dd>
 
@@ -2110,9 +2144,7 @@ await client.file.upload(createReadStream("path/to/file"));
 <dl>
 <dd>
 
-List evaluation sets in your account. You can use the `processorId` parameter to filter evaluation sets by processor.
-
-This endpoint returns a paginated response. You can use the `nextPageToken` to fetch subsequent results.
+List runs of a Processor. A ProcessorRun represents a single execution of a processor against a file.
 
 </dd>
 </dl>
@@ -2128,8 +2160,13 @@ This endpoint returns a paginated response. You can use the `nextPageToken` to f
 <dd>
 
 ```typescript
-await client.evaluationSet.list({
-    processorId: "processor_id_here",
+await client.processorRun.list({
+    status: "PENDING",
+    processorId: "processorId",
+    processorType: "EXTRACT",
+    sourceId: "sourceId",
+    source: "ADMIN",
+    fileNameContains: "fileNameContains",
     sortBy: "updatedAt",
     sortDir: "asc",
     nextPageToken: "xK9mLPqRtN3vS8wF5hB2cQ==:zWvUxYjM4nKpL7aDgE9HbTcR2mAyX3/Q+CNkfBSw1dZ=",
@@ -2150,7 +2187,7 @@ await client.evaluationSet.list({
 <dl>
 <dd>
 
-**request:** `Extend.EvaluationSetListRequest`
+**request:** `Extend.ProcessorRunListRequest`
 
 </dd>
 </dl>
@@ -2158,7 +2195,7 @@ await client.evaluationSet.list({
 <dl>
 <dd>
 
-**requestOptions:** `EvaluationSet.RequestOptions`
+**requestOptions:** `ProcessorRun.RequestOptions`
 
 </dd>
 </dl>
@@ -2169,7 +2206,7 @@ await client.evaluationSet.list({
 </dl>
 </details>
 
-<details><summary><code>client.evaluationSet.<a href="/src/api/resources/evaluationSet/client/Client.ts">create</a>({ ...params }) -> Extend.EvaluationSetCreateResponse</code></summary>
+<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">create</a>({ ...params }) -> Extend.ProcessorRunCreateResponse</code></summary>
 <dl>
 <dd>
 
@@ -2181,14 +2218,21 @@ await client.evaluationSet.list({
 <dl>
 <dd>
 
-Evaluation sets are collections of files and expected outputs that are used to evaluate the performance of a given processor in Extend. This endpoint will create a new evaluation set in Extend, which items can be added to using the [Create Evaluation Set Item](https://docs.extend.ai/2025-04-21/developers/api-reference/evaluation-set-endpoints/create-evaluation-set-item) endpoint.
+Run processors (extraction, classification, splitting, etc.) on a given document.
 
-Note: it is not necessary to create an evaluation set via API. You can also create an evaluation set via the Extend dashboard and take the ID from there.
+**Synchronous vs Asynchronous Processing:**
 
-</dd>
-</dl>
-</dd>
-</dl>
+- **Asynchronous (default)**: Returns immediately with `PROCESSING` status. Use webhooks or polling to get results.
+- **Synchronous**: Set `sync: true` to wait for completion and get final results in the response (5-minute timeout).
+
+**For asynchronous processing:**
+
+- You can [configure webhooks](https://docs.extend.ai/product/webhooks/configuration) to receive notifications when a processor run is complete or failed.
+- Or you can [poll the get endpoint](https://docs.extend.ai/2025-04-21/developers/api-reference/processor-endpoints/get-processor-run) for updates on the status of the processor run.
+  </dd>
+  </dl>
+  </dd>
+  </dl>
 
 #### 🔌 Usage
 
@@ -2199,9 +2243,7 @@ Note: it is not necessary to create an evaluation set via API. You can also crea
 <dd>
 
 ```typescript
-await client.evaluationSet.create({
-    name: "My Evaluation Set",
-    description: "My Evaluation Set Description",
+await client.processorRun.create({
     processorId: "processor_id_here",
 });
 ```
@@ -2219,7 +2261,7 @@ await client.evaluationSet.create({
 <dl>
 <dd>
 
-**request:** `Extend.EvaluationSetCreateRequest`
+**request:** `Extend.ProcessorRunCreateRequest`
 
 </dd>
 </dl>
@@ -2227,7 +2269,7 @@ await client.evaluationSet.create({
 <dl>
 <dd>
 
-**requestOptions:** `EvaluationSet.RequestOptions`
+**requestOptions:** `ProcessorRun.RequestOptions`
 
 </dd>
 </dl>
@@ -2238,7 +2280,7 @@ await client.evaluationSet.create({
 </dl>
 </details>
 
-<details><summary><code>client.evaluationSet.<a href="/src/api/resources/evaluationSet/client/Client.ts">get</a>(id) -> Extend.EvaluationSetGetResponse</code></summary>
+<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">get</a>(id) -> Extend.ProcessorRunGetResponse</code></summary>
 <dl>
 <dd>
 
@@ -2250,7 +2292,9 @@ await client.evaluationSet.create({
 <dl>
 <dd>
 
-Retrieve a specific evaluation set by ID. This returns an evaluation set object, but does not include the items in the evaluation set. You can use the [List Evaluation Set Items](https://docs.extend.ai/2025-04-21/developers/api-reference/evaluation-set-endpoints/list-evaluation-set-items) endpoint to get the items in an evaluation set.
+Retrieve details about a specific processor run, including its status, outputs, and any edits made during review.
+
+A common use case for this endpoint is to poll for the status and final output of an async processor run when using the [Run Processor](https://docs.extend.ai/2025-04-21/developers/api-reference/processor-endpoints/run-processor) endpoint. For instance, if you do not want to not configure webhooks to receive the output via completion/failure events.
 
 </dd>
 </dl>
@@ -2266,7 +2310,7 @@ Retrieve a specific evaluation set by ID. This returns an evaluation set object,
 <dd>
 
 ```typescript
-await client.evaluationSet.get("evaluation_set_id_here");
+await client.processorRun.get("processor_run_id_here");
 ```
 
 </dd>
@@ -2284,9 +2328,9 @@ await client.evaluationSet.get("evaluation_set_id_here");
 
 **id:** `string`
 
-The ID of the evaluation set to retrieve.
+The unique identifier for this processor run.
 
-Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
+Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 
 </dd>
 </dl>
@@ -2294,7 +2338,7 @@ Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
 <dl>
 <dd>
 
-**requestOptions:** `EvaluationSet.RequestOptions`
+**requestOptions:** `ProcessorRun.RequestOptions`
 
 </dd>
 </dl>
@@ -2305,9 +2349,7 @@ Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
 </dl>
 </details>
 
-## EvaluationSetItem
-
-<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">list</a>(id, { ...params }) -> Extend.EvaluationSetItemListResponse</code></summary>
+<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">delete</a>(id) -> Extend.ProcessorRunDeleteResponse</code></summary>
 <dl>
 <dd>
 
@@ -2319,9 +2361,9 @@ Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
 <dl>
 <dd>
 
-List all items in a specific evaluation set. Evaluation set items are the individual files and expected outputs that are used to evaluate the performance of a given processor in Extend.
+Delete a processor run and all associated data from Extend. This operation is permanent and cannot be undone.
 
-This endpoint returns a paginated response. You can use the `nextPageToken` to fetch subsequent results.
+This endpoint can be used if you'd like to manage data retention on your own rather than automated data retention policies. Or make one-off deletions for your downstream customers.
 
 </dd>
 </dl>
@@ -2337,12 +2379,7 @@ This endpoint returns a paginated response. You can use the `nextPageToken` to f
 <dd>
 
 ```typescript
-await client.evaluationSetItem.list("evaluation_set_id_here", {
-    sortBy: "updatedAt",
-    sortDir: "asc",
-    nextPageToken: "xK9mLPqRtN3vS8wF5hB2cQ==:zWvUxYjM4nKpL7aDgE9HbTcR2mAyX3/Q+CNkfBSw1dZ=",
-    maxPageSize: 1,
-});
+await client.processorRun.delete("processor_run_id_here");
 ```
 
 </dd>
@@ -2360,17 +2397,9 @@ await client.evaluationSetItem.list("evaluation_set_id_here", {
 
 **id:** `string`
 
-The ID of the evaluation set to retrieve items for.
-
-Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
-
-</dd>
-</dl>
-
-<dl>
-<dd>
+The ID of the processor run to delete.
 
-**request:** `Extend.EvaluationSetItemListRequest`
+Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 
 </dd>
 </dl>
@@ -2378,7 +2407,7 @@ Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
 <dl>
 <dd>
 
-**requestOptions:** `EvaluationSetItem.RequestOptions`
+**requestOptions:** `ProcessorRun.RequestOptions`
 
 </dd>
 </dl>
@@ -2389,7 +2418,7 @@ Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
 </dl>
 </details>
 
-<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">create</a>({ ...params }) -> Extend.EvaluationSetItemCreateResponse</code></summary>
+<details><summary><code>client.processorRun.<a href="/src/api/resources/processorRun/client/Client.ts">cancel</a>(id) -> Extend.ProcessorRunCancelResponse</code></summary>
 <dl>
 <dd>
 
@@ -2401,25 +2430,14 @@ Example: `"ev_2LcgeY_mp2T5yPaEuq5Lw"`
 <dl>
 <dd>
 
-Evaluation set items are the individual files and expected outputs that are used to evaluate the performance of a given processor in Extend. This endpoint will create a new evaluation set item in Extend, which will be used during an evaluation run.
+Cancel a running processor run by its ID. This endpoint allows you to stop a processor run that is currently in progress.
 
-Best Practices for Outputs in Evaluation Sets:
+Note: Only processor runs with a status of `"PROCESSING"` can be cancelled. Processor runs that have already completed, failed, or been cancelled cannot be cancelled again.
 
-- **Configure First, Output Later**
-    - Always create and finalize your processor configuration before creating evaluation sets
-    - Field IDs in outputs must match those defined in your processor configuration
-- **Type Consistency**
-    - Ensure output types exactly match your processor configuration
-    - For example, if a field is configured as "currency", don't submit a simple number value
-- **Field IDs**
-    - Use the exact field IDs from your processor configuration
-    - Create your own semantic IDs instead in the configs for each field/type instead of using the generated ones
-- **Value**
-    - Remember that all results are inside the value key of a result object, except the values within nested structures.
-      </dd>
-      </dl>
-      </dd>
-      </dl>
+</dd>
+</dl>
+</dd>
+</dl>
 
 #### 🔌 Usage
 
@@ -2430,15 +2448,7 @@ Best Practices for Outputs in Evaluation Sets:
 <dd>
 
 ```typescript
-await client.evaluationSetItem.create({
-    evaluationSetId: "evaluation_set_id_here",
-    fileId: "file_id_here",
-    expectedOutput: {
-        value: {
-            key: "value",
-        },
-    },
-});
+await client.processorRun.cancel("processor_run_id_here");
 ```
 
 </dd>
@@ -2454,7 +2464,11 @@ await client.evaluationSetItem.create({
 <dl>
 <dd>
 
-**request:** `Extend.EvaluationSetItemCreateRequest`
+**id:** `string`
+
+The unique identifier for the processor run to cancel.
+
+Example: `"dpr_Xj8mK2pL9nR4vT7qY5wZ"`
 
 </dd>
 </dl>
@@ -2462,7 +2476,7 @@ await client.evaluationSetItem.create({
 <dl>
 <dd>
 
-**requestOptions:** `EvaluationSetItem.RequestOptions`
+**requestOptions:** `ProcessorRun.RequestOptions`
 
 </dd>
 </dl>
@@ -2473,7 +2487,9 @@ await client.evaluationSetItem.create({
 </dl>
 </details>
 
-<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">update</a>(id, { ...params }) -> Extend.EvaluationSetItemUpdateResponse</code></summary>
+## Processor
+
+<details><summary><code>client.processor.<a href="/src/api/resources/processor/client/Client.ts">list</a>({ ...params }) -> Extend.ListProcessorsResponse</code></summary>
 <dl>
 <dd>
 
@@ -2485,7 +2501,7 @@ await client.evaluationSetItem.create({
 <dl>
 <dd>
 
-If you need to change the expected output for a given evaluation set item, you can use this endpoint to update the item. This can be useful if you need to correct an error in the expected output or if the output of the processor has changed.
+List all processors in your organization
 
 </dd>
 </dl>
@@ -2501,12 +2517,12 @@ If you need to change the expected output for a given evaluation set item, you c
 <dd>
 
 ```typescript
-await client.evaluationSetItem.update("evaluation_set_item_id_here", {
-    expectedOutput: {
-        value: {
-            key: "value",
-        },
-    },
+await client.processor.list({
+    type: "EXTRACT",
+    nextPageToken: "nextPageToken",
+    maxPageSize: 1,
+    sortBy: "createdAt",
+    sortDir: "asc",
 });
 ```
 
@@ -2523,19 +2539,7 @@ await client.evaluationSetItem.update("evaluation_set_item_id_here", {
 <dl>
 <dd>
 
-**id:** `string`
-
-The ID of the evaluation set item to update.
-
-Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
-
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request:** `Extend.EvaluationSetItemUpdateRequest`
+**request:** `Extend.ProcessorListRequest`
 
 </dd>
 </dl>
@@ -2543,7 +2547,7 @@ Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
 <dl>
 <dd>
 
-**requestOptions:** `EvaluationSetItem.RequestOptions`
+**requestOptions:** `Processor.RequestOptions`
 
 </dd>
 </dl>
@@ -2554,7 +2558,7 @@ Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
 </dl>
 </details>
 
-<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">delete</a>(id) -> Extend.EvaluationSetItemDeleteResponse</code></summary>
+<details><summary><code>client.processor.<a href="/src/api/resources/processor/client/Client.ts">create</a>({ ...params }) -> Extend.ProcessorCreateResponse</code></summary>
 <dl>
 <dd>
 
@@ -2566,9 +2570,7 @@ Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
 <dl>
 <dd>
 
-Delete an evaluation set item from an evaluation set. This operation is permanent and cannot be undone.
-
-This endpoint can be used to remove individual items from an evaluation set when they are no longer needed or if they were added in error.
+Create a new processor in Extend, optionally cloning from an existing processor
 
 </dd>
 </dl>
@@ -2584,7 +2586,10 @@ This endpoint can be used to remove individual items from an evaluation set when
 <dd>
 
 ```typescript
-await client.evaluationSetItem.delete("evaluation_set_item_id_here");
+await client.processor.create({
+    name: "My Processor Name",
+    type: "EXTRACT",
+});
 ```
 
 </dd>
@@ -2600,11 +2605,7 @@ await client.evaluationSetItem.delete("evaluation_set_item_id_here");
 <dl>
 <dd>
 
-**id:** `string`
-
-The ID of the evaluation set item to delete.
-
-Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
+**request:** `Extend.ProcessorCreateRequest`
 
 </dd>
 </dl>
@@ -2612,7 +2613,7 @@ Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
 <dl>
 <dd>
 
-**requestOptions:** `EvaluationSetItem.RequestOptions`
+**requestOptions:** `Processor.RequestOptions`
 
 </dd>
 </dl>
@@ -2623,7 +2624,7 @@ Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
 </dl>
 </details>
 
-<details><summary><code>client.evaluationSetItem.<a href="/src/api/resources/evaluationSetItem/client/Client.ts">createBatch</a>({ ...params }) -> Extend.EvaluationSetItemCreateBatchResponse</code></summary>
+<details><summary><code>client.processor.<a href="/src/api/resources/processor/client/Client.ts">update</a>(id, { ...params }) -> Extend.ProcessorUpdateResponse</code></summary>
 <dl>
 <dd>
 
@@ -2635,9 +2636,7 @@ Example: `"evi_kR9mNP12Qw4yTv8BdR3H"`
 <dl>
 <dd>
 
-If you have a large number of files that you need to add to an evaluation set, you can use this endpoint to create multiple evaluation set items at once. This can be useful if you have a large dataset that you need to evaluate the performance of a processor against.
-
-Note: you still need to create each File first using the file API.
+Update an existing processor in Extend
 
 </dd>
 </dl>
@@ -2653,19 +2652,7 @@ Note: you still need to create each File first using the file API.
 <dd>
 
 ```typescript
-await client.evaluationSetItem.createBatch({
-    evaluationSetId: "evaluation_set_id_here",
-    items: [
-        {
-            fileId: "file_id_here",
-            expectedOutput: {
-                value: {
-                    key: "value",
-                },
-            },
-        },
-    ],
-});
+await client.processor.update("processor_id_here");
 ```
 
 </dd>
@@ -2681,7 +2668,11 @@ await client.evaluationSetItem.createBatch({
 <dl>
 <dd>
 
-**request:** `Extend.EvaluationSetItemCreateBatchRequest`
+**id:** `string`
+
+The ID of the processor to update.
+
+Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 
 </dd>
 </dl>
@@ -2689,7 +2680,15 @@ await client.evaluationSetItem.createBatch({
 <dl>
 <dd>
 
-**requestOptions:** `EvaluationSetItem.RequestOptions`
+**request:** `Extend.ProcessorUpdateRequest`
+
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `Processor.RequestOptions`
 
 </dd>
 </dl>
@@ -2700,9 +2699,9 @@ await client.evaluationSetItem.createBatch({
 </dl>
 </details>
 
-## WorkflowRunOutput
+## ProcessorVersion
 
-<details><summary><code>client.workflowRunOutput.<a href="/src/api/resources/workflowRunOutput/client/Client.ts">update</a>(workflowRunId, outputId, { ...params }) -> Extend.WorkflowRunOutputUpdateResponse</code></summary>
+<details><summary><code>client.processorVersion.<a href="/src/api/resources/processorVersion/client/Client.ts">list</a>(id) -> Extend.ProcessorVersionListResponse</code></summary>
 <dl>
 <dd>
 
@@ -2714,11 +2713,10 @@ await client.evaluationSetItem.createBatch({
 <dl>
 <dd>
 
-Use this endpoint to submit corrected outputs for a WorkflowRun for future processor evaluation and tuning in Extend.
-
-If you are using our Human-in-the-loop workflow review, then we already will be collecting your operator submitted corrections. However, if you are receiving data via the API without human review, there could be incorrect outputs that you would like to correct for future usage in evaluation and tuning within the Extend platform. This endpoint allows you to submit corrected outputs for a WorkflowRun, by providing the correct output for a given output ID.
+This endpoint allows you to fetch all versions of a given processor, including the current `draft` version.
 
-The output ID, would be found in a given entry within the outputs arrays of a Workflow Run payload. The ID would look something like `dpr_gwkZZNRrPgkjcq0y-***`.
+Versions are typically returned in descending order of creation (newest first), but this should be confirmed in the actual implementation.
+The `draft` version is the latest unpublished version of the processor, which can be published to create a new version. It might not have any changes from the last published version.
 
 </dd>
 </dl>
@@ -2734,13 +2732,7 @@ The output ID, would be found in a given entry within the outputs arrays of a Wo
 <dd>
 
 ```typescript
-await client.workflowRunOutput.update("workflow_run_id_here", "output_id_here", {
-    reviewedOutput: {
-        value: {
-            key: "value",
-        },
-    },
-});
+await client.processorVersion.list("processor_id_here");
 ```
 
 </dd>
@@ -2756,23 +2748,11 @@ await client.workflowRunOutput.update("workflow_run_id_here", "output_id_here",
 <dl>
 <dd>
 
-**workflowRunId:** `string`
-
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**outputId:** `string`
-
-</dd>
-</dl>
+**id:** `string`
 
-<dl>
-<dd>
+The ID of the processor to retrieve versions for.
 
-**request:** `Extend.WorkflowRunOutputUpdateRequest`
+Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 
 </dd>
 </dl>
@@ -2780,7 +2760,7 @@ await client.workflowRunOutput.update("workflow_run_id_here", "output_id_here",
 <dl>
 <dd>
 
-**requestOptions:** `WorkflowRunOutput.RequestOptions`
+**requestOptions:** `ProcessorVersion.RequestOptions`
 
 </dd>
 </dl>
@@ -2791,9 +2771,7 @@ await client.workflowRunOutput.update("workflow_run_id_here", "output_id_here",
 </dl>
 </details>
 
-## BatchProcessorRun
-
-<details><summary><code>client.batchProcessorRun.<a href="/src/api/resources/batchProcessorRun/client/Client.ts">get</a>(id) -> Extend.BatchProcessorRunGetResponse</code></summary>
+<details><summary><code>client.processorVersion.<a href="/src/api/resources/processorVersion/client/Client.ts">create</a>(id, { ...params }) -> Extend.ProcessorVersionCreateResponse</code></summary>
 <dl>
 <dd>
 
@@ -2805,7 +2783,9 @@ await client.workflowRunOutput.update("workflow_run_id_here", "output_id_here",
 <dl>
 <dd>
 
-Retrieve details about a batch processor run, including evaluation runs
+This endpoint allows you to publish a new version of an existing processor. Publishing a new version creates a snapshot of the processor's current configuration and makes it available for use in workflows.
+
+Publishing a new version does not automatically update existing workflows using this processor. You may need to manually update workflows to use the new version if desired.
 
 </dd>
 </dl>
@@ -2821,7 +2801,9 @@ Retrieve details about a batch processor run, including evaluation runs
 <dd>
 
 ```typescript
-await client.batchProcessorRun.get("batch_processor_run_id_here");
+await client.processorVersion.create("processor_id_here", {
+    releaseType: "major",
+});
 ```
 
 </dd>
@@ -2839,9 +2821,9 @@ await client.batchProcessorRun.get("batch_processor_run_id_here");
 
 **id:** `string`
 
-The unique identifier of the batch processor run to retrieve. The ID will always start with "bpr\_".
+The ID of the processor to publish a new version for.
 
-Example: `"bpr_Xj8mK2pL9nR4vT7qY5wZ"`
+Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 
 </dd>
 </dl>
@@ -2849,7 +2831,15 @@ Example: `"bpr_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-**requestOptions:** `BatchProcessorRun.RequestOptions`
+**request:** `Extend.ProcessorVersionCreateRequest`
+
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `ProcessorVersion.RequestOptions`
 
 </dd>
 </dl>
@@ -2860,9 +2850,7 @@ Example: `"bpr_Xj8mK2pL9nR4vT7qY5wZ"`
 </dl>
 </details>
 
-## Workflow
-
-<details><summary><code>client.workflow.<a href="/src/api/resources/workflow/client/Client.ts">create</a>({ ...params }) -> Extend.WorkflowCreateResponse</code></summary>
+<details><summary><code>client.processorVersion.<a href="/src/api/resources/processorVersion/client/Client.ts">get</a>(processorId, processorVersionId) -> Extend.ProcessorVersionGetResponse</code></summary>
 <dl>
 <dd>
 
@@ -2874,9 +2862,7 @@ Example: `"bpr_Xj8mK2pL9nR4vT7qY5wZ"`
 <dl>
 <dd>
 
-Create a new workflow in Extend. Workflows are sequences of steps that process files and data in a specific order to achieve a desired outcome.
-
-This endpoint will create a new workflow in Extend, which can then be configured and deployed. Typically, workflows are created from our UI, however this endpoint can be used to create workflows programmatically. Configuration of the flow still needs to be done in the dashboard.
+Retrieve a specific version of a processor in Extend
 
 </dd>
 </dl>
@@ -2892,9 +2878,7 @@ This endpoint will create a new workflow in Extend, which can then be configured
 <dd>
 
 ```typescript
-await client.workflow.create({
-    name: "Invoice Processing",
-});
+await client.processorVersion.get("processor_id_here", "processor_version_id_here");
 ```
 
 </dd>
@@ -2910,7 +2894,11 @@ await client.workflow.create({
 <dl>
 <dd>
 
-**request:** `Extend.WorkflowCreateRequest`
+**processorId:** `string`
+
+The ID of the processor.
+
+Example: `"dp_Xj8mK2pL9nR4vT7qY5wZ"`
 
 </dd>
 </dl>
@@ -2918,7 +2906,19 @@ await client.workflow.create({
 <dl>
 <dd>
 
-**requestOptions:** `Workflow.RequestOptions`
+**processorVersionId:** `string`
+
+The ID of the specific processor version to retrieve.
+
+Example: `"dpv_QYk6jgHA_8CsO8rVWhyNC"`
+
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `ProcessorVersion.RequestOptions`
 
 </dd>
 </dl>