> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Docparser

The Docparser connector lets your AI agent act in each user's Docparser account. Each user connects their own Docparser API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 10 tools.

**Authentication:** API Key
**Categories:** Files & Documents, Automation
**Tools:** 10: 6 read, 4 write, 0 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=DOCPARSER)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Docparser connection

   In **AgentKit > Connections**, create a Docparser connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'docparser_document_result_get',
  toolInput: {
    document_id: '<document_id>',
    parser_id: '<parser_id>',
  },
  connector: 'docparser',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="docparser_document_result_get",
    tool_input={
        "document_id": "<document_id>",
        "parser_id": "<parser_id>",
    },
    connection_name="docparser",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `docparser_document_result_get`

Get Parsed Data For Document · Read-only

Get the parsed data of one document.
Returns an array with one object holding document_id, remote_id, file_name, media links, page_count, uploaded_at, processed_at and every field the parser extracted.
Use docparser_document_result_get when you know the document_id. Use docparser_results_list to get the data of many documents in a parser. Limited to 60 calls per minute.
Requires a parser_id and a document_id from an import tool or docparser_results_list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): ID of the document, as returned by docparser_document_fetch_url or docparser_document_upload_base64 (document_id or id) or by the document_id field of docparser_results_list. Example: 1d35639d4b53b59e77f737c93cd1d3d7
- `parser_id` (`string`, required): ID of the Document Parser, from docparser_parsers_list (the id field) or from Settings > API of the parser in the Docparser app. Example: mwekrupomwekrupo
- `format` (`string`, optional): Shape of the parsed data. object (default) returns nested JSON objects; flat returns simple key/value pairs instead of nested objects. Example: flat. One of: `object`, `flat`.
- `include_children` (`boolean`, optional): Set true to also return the parsed data of child documents created during preprocessing, for example when a document was split. Example: true

Example input: `{"document_id":"<document_id>","parser_id":"<parser_id>"}`

### `docparser_document_status_get`

Get Document Status · Read-only

Get the processing state of one imported document.
Returns file name, page count, in-progress flags for importing, processing and webhook dispatch, Unix timestamps for each stage (uploaded_at, imported_at, processed_at, etc.) and a failed_jobs list.
Use docparser_document_status_get to check whether a document has finished parsing. Use docparser_document_result_get to read the parsed data once it has.
Requires a parser_id and a document_id from an import tool.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `document_id` (`string`, required): ID of the document, as returned by docparser_document_fetch_url or docparser_document_upload_base64 (document_id or id) or by the document_id field of docparser_results_list. Example: 1d35639d4b53b59e77f737c93cd1d3d7
- `parser_id` (`string`, required): ID of the Document Parser, from docparser_parsers_list (the id field) or from Settings > API of the parser in the Docparser app. Example: mwekrupomwekrupo

Example input: `{"document_id":"<document_id>","parser_id":"<parser_id>"}`

### `docparser_parser_models_list`

List Parser Model Layouts · Read-only

List the model layouts configured in one Document Parser.
Returns an array of layouts, each with id and label.
Use docparser_parser_models_list to see which document layouts a parser recognises. Use docparser_parsers_list to list the parsers themselves.
Requires a parser_id from docparser_parsers_list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `parser_id` (`string`, required): ID of the Document Parser, from docparser_parsers_list (the id field) or from Settings > API of the parser in the Docparser app. Example: mwekrupomwekrupo

Example input: `{"parser_id":"<parser_id>"}`

### `docparser_parsers_list`

List Parsers · Read-only

List every Document Parser in the Docparser account.
Returns an array of parsers, each with id and label.
Use docparser_parsers_list to find the parser_id that every other Docparser tool needs. Use docparser_parser_models_list for the layouts inside one parser.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `docparser_ping`

Ping · Read-only

Check that the Docparser API key on this connection is valid.
Returns {"msg": "pong"} when authentication succeeds.
Use docparser_ping to test the connection. Use docparser_parsers_list to see what the account contains.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `docparser_results_list`

List Parsed Data · Read-only

List the parsed data of documents in one Document Parser, newest upload first by default, with filters by date, remote_id and sort order.
Returns an array of parsed-data objects, each with document_id, remote_id, file_name, media links, page_count, uploaded_at, processed_at and the extracted fields. Up to 100 documents by default.
Use docparser_results_list to browse or filter results across a parser. Use docparser_document_result_get for a single known document. Limited to 30 calls per minute.
Requires a parser_id from docparser_parsers_list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `parser_id` (`string`, required): ID of the Document Parser, from docparser_parsers_list (the id field) or from Settings > API of the parser in the Docparser app. Example: mwekrupomwekrupo
- `date` (`string`, optional): Cut-off date, required when list is uploaded_after or processed_after. An ISO 8601 date-time or a Unix timestamp. Example: 2024-02-12T15:19:21+00:00
- `format` (`string`, optional): Shape of the parsed data. object (default) returns nested JSON objects; flat returns simple key/value pairs instead of nested objects. Example: flat. One of: `object`, `flat`.
- `include_processing_queue` (`boolean`, optional): Set true to also include documents that are not fully processed yet (still importing, preprocessing or parsing). By default only fully processed documents are returned. Example: true
- `limit` (`integer`, optional): How many documents to return when list is last_uploaded. Defaults to 100; at most 10000. Example: 50
- `list` (`string`, optional): Which documents to return. last_uploaded (default) returns the most recent uploads, newest first, paged with limit and offset. uploaded_after returns documents imported after date; processed_after returns documents parsed after date (both need date). Example: uploaded_after. One of: `last_uploaded`, `uploaded_after`, `processed_after`.
- `offset` (`integer`, optional): Number of documents to skip, for paging together with limit. Defaults to 0. Example: an offset of 20 with a limit of 10 starts at the 21st document: 20
- `remote_id` (`string`, optional): Return only documents imported with this remote_id (the ID from your own system set at import). Example: invoice-2024-0042
- `sort_by` (`string`, optional): Field to sort by. By default results follow upload order. Example: processed_at. One of: `parsed_at`, `processed_at`, `uploaded_at`, `first_processed_at`, `imported_at`, `integrated_at`, `dispatched_webhook_at`, `preprocessed_at`.
- `sort_order` (`string`, optional): Sort direction: DESC (default, newest first) or ASC. Example: ASC. One of: `ASC`, `DESC`.

Example input: `{"parser_id":"<parser_id>"}`

### `docparser_document_fetch_url`

Import Document From URL · Write

Import a document into a Document Parser by giving Docparser a publicly accessible URL to fetch it from.
Returns document_id, parser_id, remote_id and a message with the status URL; the document is fetched and parsed a few minutes later.
Use docparser_document_fetch_url when the file is online. Use docparser_document_upload_base64 when you have the file content. Then poll docparser_document_status_get and read results with docparser_document_result_get.
Requires a parser_id from docparser_parsers_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `parser_id` (`string`, required): ID of the Document Parser, from docparser_parsers_list (the id field) or from Settings > API of the parser in the Docparser app. Example: mwekrupomwekrupo
- `url` (`string`, required): Publicly accessible URL of the document (PDF, image, Word, etc.) for Docparser to download. It must be reachable without login. Example: https://www.example.com/invoices/inv-0042.pdf
- `remote_id` (`string`, optional): Optional ID from your own system to store with the document. Docparser keeps it through processing and returns it as remote_id in the parsed data, so you can match results to your records. Example: invoice-2024-0042

Example input: `{"parser_id":"<parser_id>","url":"<url>"}`

### `docparser_document_upload_base64`

Import Document From Base64 · Write

Import a document into a Document Parser by sending its content as a base64 string.
Returns the new document id, file_size and account quota usage (quota_used, quota_left, quota_refill).
Use docparser_document_upload_base64 when you have the file bytes. Use docparser_document_fetch_url when the file is at a public URL. Then poll docparser_document_status_get and read results with docparser_document_result_get.
Requires a parser_id from docparser_parsers_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `file_content` (`string`, required): The whole file encoded as standard base64, without a data: URL prefix. Example: JVBERi0xLjQKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIFI+PgpzdHJlYW0K
- `parser_id` (`string`, required): ID of the Document Parser, from docparser_parsers_list (the id field) or from Settings > API of the parser in the Docparser app. Example: mwekrupomwekrupo
- `file_name` (`string`, optional): File name to store for the document, including its extension. If left empty, Docparser names the file after the upload time. Example: invoice-0042.pdf
- `remote_id` (`string`, optional): Optional ID from your own system to store with the document. Docparser keeps it through processing and returns it as remote_id in the parsed data, so you can match results to your records. Example: invoice-2024-0042

Example input: `{"file_content":"<file_content>","parser_id":"<parser_id>"}`

### `docparser_documents_reintegrate`

Re-Integrate Documents · Write

Queue documents in a Document Parser to send their parsed data to the parser's integrations (webhooks, cloud storage, etc.) again.
Returns total_reintegrate (how many documents were queued) and msg.
Use docparser_documents_reintegrate to redeliver data an integration missed. Use docparser_documents_reparse to parse documents again first.
Requires a parser_id and document IDs from docparser_results_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `document_ids` (`array`, required): Non-empty list of document IDs to re-integrate. Take them from the document_id field of docparser_results_list or from the import response. Example: ["1d35639d4b53b59e77f737c93cd1d3d7", "b07b080b357334510e10f5b41567000c"]
- `parser_id` (`string`, required): ID of the Document Parser, from docparser_parsers_list (the id field) or from Settings > API of the parser in the Docparser app. Example: mwekrupomwekrupo

Example input: `{"document_ids":["1d35639d4b53b59e77f737c93cd1d3d7","b07b080b357334510e10f5b41567000c"],"parser_id":"<parser_id>"}`

### `docparser_documents_reparse`

Re-Parse Documents · Write

Schedule documents in a Document Parser to be parsed again with the parser's current rules.
Returns total_reparsed (how many documents were queued) and msg.
Use docparser_documents_reparse after changing parsing rules. Use docparser_documents_reintegrate to resend existing parsed data to integrations without parsing again.
Requires a parser_id and document IDs from docparser_results_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `document_ids` (`array`, required): Non-empty list of document IDs to re-parse. Take them from the document_id field of docparser_results_list or from the import response. Example: ["1d35639d4b53b59e77f737c93cd1d3d7", "b07b080b357334510e10f5b41567000c"]
- `parser_id` (`string`, required): ID of the Document Parser, from docparser_parsers_list (the id field) or from Settings > API of the parser in the Docparser app. Example: mwekrupomwekrupo

Example input: `{"document_ids":["1d35639d4b53b59e77f737c93cd1d3d7","b07b080b357334510e10f5b41567000c"],"parser_id":"<parser_id>"}`

## Related

Other Files & Documents connectors ([all 76](/agentkit/connectors/?category=files-documents)):

- [Notion](/agentkit/connectors/notion/): Scalekit connector, OAuth, 51 tools
- [Google Sheets](/agentkit/connectors/googlesheets/): Scalekit connector, OAuth, 48 tools
- [Google Drive](/agentkit/connectors/googledrive/): Scalekit connector, OAuth, 47 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
