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

Chunkr Tasks API

Create, poll, list, cancel, and delete parse and extract tasks.

Chunkr Tasks API is one of 3 APIs that Chunkr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 8 operations across 7 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.chunkr.ai, https://localhost:8000.

8 operations 7 paths 4 schemas 1 DELETE4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.chunkr.ai
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Chunkr Tasks API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKey). By default, every request must be authenticated.

  • apiKey — API key issued from the Chunkr dashboard, sent as the raw value of the Authorization header (e.g. "Authorization: lu...").

Paths & Operations 8

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

Tasks 8

Create, poll, list, cancel, and delete parse and extract tasks.

POST
/tasks/parse
Create a parse task
createParseTask body → 200401
POST
/tasks/extract
Create an extract task
createExtractTask body → 200401
GET
/tasks
List tasks
listTasks 3 params → 200
GET
/tasks/{task_id}
Get a task
getTask 3 params → 200404
DELETE
/tasks/{task_id}
Delete a task
deleteTask 1 param → 200404
GET
/tasks/{task_id}/parse
Get a parse task
getParseTask 1 param → 200
GET
/tasks/{task_id}/extract
Get an extract task
getExtractTask 1 param → 200
POST
/tasks/{task_id}/cancel
Cancel a task
cancelTask 1 param → 200404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are TaskResponse (14 properties), CreateParseTaskRequest (8 properties), CreateExtractTaskRequest (6 properties), ChunkProcessing (2 properties). Each schema is shown below with its type and property counts.

CreateExtractTaskRequest
object
6 properties 2 required
ChunkProcessing
object
2 properties
CreateParseTaskRequest
object
8 properties 1 required
TaskResponse
object
14 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chunkr-ai-tasks-api-openapi.yml Raw ↑

Other APIs Chunkr publishes across the network.

Chunkr Files API
Chunkr Health API
Where this information came from

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