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

Landing.ai Extract API

The Extract API from Landing.ai — 3 operation(s) for extract.

Landing.ai Extract API is one of 13 APIs that Landing.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Extract. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

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

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

4 operations 3 paths 4 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.1.0
Base URL
https://api.ade.landing.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Landing.ai Extract API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Basic) (Basic Auth).

  • Basic Auth — Your unique API key for authentication. Get your API key here: https://va.landing.ai/settings/api-key. If using the EU endpoint, get your API key here: https:/…

Paths & Operations 4

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

Extract 4
POST
/v2/extract
ADE Extract
v2-extract_run_sync body → 200422
POST
/v2/extract/jobs
ADE Extract Jobs
v2-extract_create_job body → 202422
GET
/v2/extract/jobs
ADE List Extract Jobs
v2-extract_list_jobs 3 params → 200422
GET
/v2/extract/jobs/{job_id}
ADE Get Extract Jobs
v2-extract_get_job 1 param → 200404422

Schemas 4

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

V2Billing
object
Billing summary: the service tier the request ran in and the credits charged.
2 properties
V2ExtractMetadata
object
Response metadata for a v2 extract call.
9 properties 5 required
V2ExtractOptions
object
Extraction options (docs/extract-v2-proposal.md → Options).
1 property
ErrorResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

landingai-extract-api-openapi.yml Raw ↑

Other APIs Landing.ai publishes across the network.

Landing.ai Classes API
Landing.ai Deployment API
Landing.ai Image API
Landing.ai Metadata API
Landing.ai Metrics API
Landing.ai Model API
Landing.ai Parse API
Landing.ai Project API
Landing.ai Snapshot API
Landing.ai Tags API
Landing.ai Tools API
Landing.ai Training API
Where this information came from

This is an independent, third-party profile of Landing.ai Extract 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.