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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Docparser

Docparser Results API

Retrieve parsed data results

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 2 operations across 2 paths, and defines 2 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.

2 operations 2 paths 2 schemas 2 GET

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
Contact
Docparser Support
License
Proprietary
Terms of Service
View terms
Resource Areas
1

Authentication & Security 3

Docparser Results 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 2

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

Results 2

Retrieve parsed data results

GET
/results/{parserId}/{documentId}
Get results for a single document
getResultsByDocument 3 params → 200401404429
GET
/results/{parserId}
Get results for all documents in a parser
getResultsByParser 9 params → 200401429

Schemas 2

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

ParsedResult
object
A parsed document result. The exact fields depend on the parser configuration. Common fields are listed; custom extracted fields are appended dynamically.
7 properties
ErrorResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

docparser-results-api-openapi.yml Raw ↑

Other APIs Docparser publishes across the network.

Docparser Documents API
AE Profile APIs.io
Docparser Parsers API
AE Profile APIs.io
Docparser Ping API
AE Profile APIs.io
#Results
← Back to D APIs
API Details
ID
docparser:docparser-results-api
Base URL
https://api.docparser.com/v1
Docs
https://docparser.com/api/
Provider
Docparser
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=docparser-results-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/docparser-results-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Docparser Results 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.