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

Doctly Extractors API

Manage and run custom structured-data extractors.

Doctly Extractors API is one of 2 APIs that Doctly publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://api.doctly.ai/api/v1.

5 operations 3 paths 10 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.doctly.ai/api/v1
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Doctly Extractors API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer API key, sent as Authorization: Bearer YOURAPIKEY.

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Extractors 5

Manage and run custom structured-data extractors.

GET
/e
List extractors
listExtractors 2 params → 200401
POST
/e/{slug}
Run an extractor
runExtractor 1 param body → 200404
GET
/e/{extractor_id}
Get an extractor
getExtractor 1 param → 200404
PUT
/e/{extractor_id}
Update an extractor
updateExtractor 1 param body → 200404
DELETE
/e/{extractor_id}
Delete an extractor
deleteExtractor 1 param → 200404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are DocumentCreateResponse (8 properties), ExtractorPublic (6 properties), RunExtractorRequest (3 properties), ExtractorsPublic (2 properties). Each schema is shown below with its type and property counts.

DocumentCreateResponse
object
8 properties
DocumentStatus
string
Lifecycle status of a document processing job.
RunExtractorRequest
object
3 properties
ExtractorUpdate
object
2 properties
CostType
string
How an extractor's credits are charged.
DocumentCreateExtractionResponse
AccuracyLevel
string
Conversion accuracy. lite is faster (default); ultra generates multiple versions per page and selects the most accurate, but takes longer.
Message
object
1 property
ExtractorsPublic
object
2 properties
ExtractorPublic
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

doctly-ai-extractors-api-openapi.yml Raw ↑

Other APIs Doctly publishes across the network.

Doctly Documents API
Where this information came from

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