PARSER GUIDES

Overview

Complete API documentation for developers

PARSER provides a REST API for processing documents and managing the same parser, classifier, field, document, folder, review, export, and webhook resources available in the app.

Getting Started

Authentication

All API requests require authentication using API keys.

Learn more about authentication ->

MCP for AI agents

Use the remote PARSER MCP server when you want an AI assistant to manage parsers and classifiers, process documents, search extracted data, review documents, or export data through natural language.

Set up the MCP server ->

Base URL

https://api.PARSER.com

All endpoints are under /api/v1/, for example GET /api/v1/parsers, GET /api/v1/classifiers, or POST /api/v1/process/files.

API Groups

• Document Processing: upload files or URLs to a parser or classifier, retrieve extracted data from parsers, and use legacy-compatible parser processing endpoints.
• Parser Management: discover, create, update, and duplicate parsers.
• Document Classifiers: create classifier routing rules, upload mixed document batches, and inspect routed, skipped, or failed classifier documents.
• Fields: manage parser fields and table fields.
• Documents: list, search, inspect, rename, move, update extracted data, delete, and reprocess documents.
• Folders: create, update, list, and delete parser folders.
• Reviews & Approvals: list reviewers, manage review stages, assign documents, and approve or reject documents.
• Exports: export extracted data as JSON, XML, CSV, or XLSX.
• Webhooks: manage parser webhook endpoints.

• MCP Server: connect AI agents to PARSER using OAuth.

Open the API reference ->

Rate Limits

• 100 requests per minute per API key
• 10,000 requests per day per API key

Webhooks

Receive real-time notifications about document processing.

Learn about webhooks ->

MCP Server

Connect AI agents to PARSER with the remote MCP server at https://mcp.PARSER.com/mcp. MCP uses OAuth and is scoped to the team selected during consent.

Set up MCP ->

Documents

Use document endpoints to search by name or external ID, filter by folder or status, retrieve extracted data, update customer-managed fields, move documents between folders, and delete documents.

Document Classifiers

Use classifier endpoints when a mixed batch should be sorted before extraction. Classifiers do not have fields, extracted-data exports, reviews, or webhooks. Routed documents are extracted by the target parsers, and target parser exports/webhooks run after extraction.

Fields

Use field endpoints to manage both scalar fields and table fields. Tables are represented as fields with type: "table" and a columns list.

Exports

Use export endpoints to download extracted data for selected documents or filtered document sets.

Reviews & Approvals

Use review endpoints to configure parser review stages, find eligible reviewers, assign documents with assigneeId, and approve, reject, or reset documents from your own systems. Approval actions require a reviewerId so PARSER can enforce the same assigned-reviewer rule used in the app.

SDKs

Official SDKs coming soon. For now, use the REST API directly.