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

Tensorlake Structured Extraction API

Schema-guided extraction, classification, read/OCR, and edit.

Tensorlake Structured Extraction API is one of 5 APIs that Tensorlake publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

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

4 operations 4 paths 6 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.tensorlake.ai
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — Tensorlake API key created in the Tensorlake Cloud dashboard (cloud.tensorlake.ai). Keys are prefixed tlapiKey and are passed as Authorization: Bearer .

Paths & Operations 4

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

Structured Extraction 4

Schema-guided extraction, classification, read/OCR, and edit.

POST
/documents/v2/extract
Extract structured data from a document
post_extract body → 200401422
POST
/documents/v2/classify
Classify a document
post_classify body → 200401422
POST
/documents/v2/read
Read / OCR a document
post_read body → 200401422
POST
/documents/v2/edit
Edit a document
post_edit body → 200401422

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ExtractRequest (4 properties), ReadRequest (3 properties), ClassifyRequest (3 properties), ParseJobCreated (2 properties). Each schema is shown below with its type and property counts.

Error
object
1 property
EditRequest
object
MODELED edit request.
2 properties
ParseJobCreated
object
Response returned when an async job is accepted. MODELED.
2 properties
ClassifyRequest
object
MODELED classification request.
3 properties
ExtractRequest
object
MODELED structured extraction request.
4 properties
ReadRequest
object
MODELED read / OCR request.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tensorlake-structured-extraction-api-openapi.yml Raw ↑

Other APIs Tensorlake publishes across the network.

Tensorlake Datasets API
Tensorlake Files API
Tensorlake Parse API
Tensorlake Sandboxes API
Where this information came from

This is an independent, third-party profile of Tensorlake Structured Extraction 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.