Skip to content
LangParse

Overview

LangParse API 1.0.0

Section titled “LangParse API 1.0.0”

Parse documents into structured, validated JSON — and configure your account headlessly. Authenticate with an API key (Authorization: Bearer <key> or X-Api-Key).

Key scopes — a key carries one or more:

  • parse — submit documents + read results (the Parse endpoints under /api/v1).
  • manage — create/edit models, routers, sources, destinations (the Management endpoints under /api).
  • admin — manage + API keys, members, billing.

New keys default to parse only. Management endpoints also accept a logged-in user session.

Uploading a file — two ways:

  1. Inline base64 — POST /v1/models/{modelId}/parse with JSON { fileBase64, fileName } (one request, up to ~12 MB).
  2. Presigned (recommended, no size limit) — POST /v1/models/{modelId}/uploads to get a one-time S3 URL, PUT the raw file to it, then POST /v1/models/{modelId}/parse with { sourceKey }.

Then poll GET /v1/documents/{documentId} for the structured result.

Information

  • OpenAPI version: 3.1.0

Operations

Section titled “Operations”
POST
/api/v1/extract
POST
/api/v1/models/{modelId}/parse
POST
/api/v1/models/{modelId}/uploads
GET
/api/v1/documents/{documentId}
GET
/api/v1/folders
GET
/api/v1/folders/{folderId}/documents
GET
/api/v1/files/{fileId}
GET
/api/models
POST
/api/models
GET
/api/models/{modelId}
PUT
/api/models/{modelId}
GET
/api/routers
POST
/api/routers
POST
/api/sources/policy
GET
/api/sources
POST
/api/sources
GET
/api/destinations
POST
/api/destinations
POST
/api/apikeys

Authentication

Section titled “Authentication”

apiKey

Section titled “apiKey”

Security scheme type: apiKey

Header parameter name: X-Api-Key

bearerAuth

Section titled “bearerAuth”

Security scheme type: http