> ## Documentation Index
> Fetch the complete documentation index at: https://composio-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Docparser

> Docparser is the most advanced cloud based document parsing and automation tool in the market today.

![Docparser logo](https://mintcdn.com/composio-preview/VNLruGH5mLZqXdPH/images/toolkits/docparser.svg?fit=max\&auto=format\&n=VNLruGH5mLZqXdPH\&q=85\&s=3407b7f2b06f2c92b12c510f1fdb120b)

* **Category:** documents & ocr
* **Auth:** API\_KEY
* **Composio-managed OAuth available?** N/A
* **Tools:** 4
* **Triggers:** 0
* **Slug:** `DOCPARSER`
* **Version:** 20261101\_00

## Tools

> [accordion] Get Multiple Document Results
>
> **Slug:** `DOCPARSER_GET_MULTIPLE_DOCUMENT_RESULTS`
>
> Retrieve parsed data from multiple documents for a specific parser. By default, returns the latest 100 uploaded documents; date-based filtering and other options can change the results, with a maximum of 10,000 documents.
>
> #### Input Parameters
>
> **date** `string`
>
> ISO 8601 or Unix timestamp; required when using 'uploaded\_after' or 'processed\_after' list modes.
>
> **list** `string ("last_uploaded" | "uploaded_after" | "processed_after")`
>
> Filtering mode - 'last\_uploaded', 'uploaded\_after', or 'processed\_after'.
>
> **limit** `integer`
>
> Maximum number of documents to return. Default is 100, maximum is 10000.
>
> **format** `string ("object" | "flat")`
>
> Output format - 'object' for nested JSON or 'flat' for simplified key/value pairs.
>
> **sort\_by** `string ("parsed_at" | "processed_at" | "uploaded_at" | "first_processed_at" | "imported_at" | "integrated_at" | "dispatched_webhook_at" | "preprocessed_at")`
>
> Sort by timestamp field. Options: 'parsed\_at', 'processed\_at', 'uploaded\_at', 'first\_processed\_at', 'imported\_at', 'integrated\_at', 'dispatched\_webhook\_at', or 'preprocessed\_at'.
>
> **parser\_id** `string` *required*
>
> Unique identifier for the document parser. Can be obtained via the List Parsers endpoint or found in parser settings under 'Settings > API'.
>
> **remote\_id** `string`
>
> Returns only documents with matching remote\_id.
>
> **sort\_order** `string ("ASC" | "DESC")`
>
> Sort direction - 'ASC' for ascending or 'DESC' for descending.
>
> **include\_processing\_queue** `boolean`
>
> Include unprocessed documents when set to true.
>
> #### Output
>
> **data** `string` *required*
>
> Data from the action execution
>
> **error** `string`
>
> Error if any occurred during the execution of the action
>
> **successful** `boolean` *required*
>
> Whether or not the action execution was successful or not

> [accordion] Get Parser Models
>
> **Slug:** `DOCPARSER_GET_PARSER_MODELS`
>
> Tool to retrieve all model layouts for a specific parser. Use when you need to list different layout configurations within a parser that help handle document variations.
>
> #### Input Parameters
>
> **parser\_id** `string` *required*
>
> The unique identifier of the parser. Can be obtained from the List Parsers endpoint or found in the Document Parser settings under 'Settings > API' within the Docparser app.
>
> #### Output
>
> **data** `string` *required*
>
> Data from the action execution
>
> **error** `string`
>
> Error if any occurred during the execution of the action
>
> **successful** `boolean` *required*
>
> Whether or not the action execution was successful or not

> [accordion] List Parsers
>
> **Slug:** `DOCPARSER_LIST_PARSERS`
>
> Tool to retrieve all Document Parsers linked to your account. Use when you need to view available parsers or obtain parser IDs for subsequent operations.
>
> #### Output
>
> **data** `string` *required*
>
> Data from the action execution
>
> **error** `string`
>
> Error if any occurred during the execution of the action
>
> **successful** `boolean` *required*
>
> Whether or not the action execution was successful or not

> [accordion] Ping API
>
> **Slug:** `DOCPARSER_PING`
>
> Tool to test API authentication and connection health check for Docparser API. Use when you need to verify that API credentials are valid and the connection is working.
>
> #### Output
>
> **data** `string` *required*
>
> Data from the action execution
>
> **error** `string`
>
> Error if any occurred during the execution of the action
>
> **successful** `boolean` *required*
>
> Whether or not the action execution was successful or not
