How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Docparser Documents API

Upload and manage documents for parsing

Docparser Documents API is one of 4 APIs that Docparser publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Documents. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against 2 base URLs: https://api.docparser.com/v1, https://api.docparser.com/v2.

3 operations 3 paths 3 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.docparser.com/v1
Authentication
HTTP Basic, API Key, API Key
License
Proprietary
Terms of Service
Resource Areas
1

Authentication & Security 3

Docparser Documents API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as api_key (apiKeyHeader). An API key is passed in the query as api_key (apiKeyQuery). By default, every request must be authenticated.

  • basicAuth — HTTP Basic Authentication. Use your API key as the username and leave the password blank.
  • apiKeyHeader — API key passed as a custom request header.
  • apiKeyQuery — API key passed as a URL query parameter.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

Documents 3

Upload and manage documents for parsing

POST
/document/upload/{parserId}
Upload a document by file
uploadDocument 1 param body → 200400401404
POST
/document/reparse/{parserId}
Reparse documents
reparseDocuments 1 param → 200401404
POST
/document/reintegrate/{parserId}
Reintegrate documents
reintegrateDocuments 1 param → 200401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are DocumentUploadResponse (4 properties), ErrorResponse (2 properties), SuccessResponse (1 property). Each schema is shown below with its type and property counts.

SuccessResponse
object
1 property
ErrorResponse
object
2 properties
DocumentUploadResponse
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

docparser-documents-api-openapi.yml Raw ↑

Other APIs Docparser publishes across the network.

Docparser Parsers API
Docparser Ping API
Docparser Results API
Where this information came from

This is an independent, third-party profile of Docparser Documents API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.