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

LlamaParse Split API

The Split API from LlamaParse — 2 operation(s) for split.

LlamaParse Split API is one of 36 APIs that LlamaParse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

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

3 operations 2 paths 11 schemas 2 GET1 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.cloud.llamaindex.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

LlamaParse Split API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 3

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

Split 3
POST
/api/v1/beta/split/jobs
Create Split Job
create_split_job_api_v1_beta_split_jobs_post 3 params body → 201422
GET
/api/v1/beta/split/jobs
List Split Jobs
list_split_jobs_api_v1_beta_split_jobs_get 9 params → 200422
GET
/api/v1/beta/split/jobs/{split_job_id}
Get Split Job
get_split_job_api_v1_beta_split_jobs__split_job_id__get 4 params → 200422

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are SplitJobResponse (11 properties), ValidationError (5 properties), SplitCreateRequest (3 properties), SplitSegmentResponse (3 properties). Each schema is shown below with its type and property counts.

SplitDocumentInput
object
Document input specification for beta API.
2 properties 2 required
SplitJobResponse
object
Beta response — uses nested documentinput object.
11 properties 6 required
SplitCategory
object
Category definition for document splitting.
2 properties 1 required
HTTPValidationError
object
1 property
SplitCreateRequest
object
Beta create request — accepts legacy documentinput and flat formats.
3 properties 1 required
SplitConfiguration
object
Split configuration with categories and splitting strategy.
2 properties 1 required
SplitJobQueryResponse
object
Beta paginated list of split jobs.
3 properties 1 required
ValidationError
object
5 properties 3 required
SplitSegmentResponse
object
A segment of the split document.
3 properties 3 required
SplitResultResponse
object
Result of a completed split job.
1 property 1 required
SplitStrategy
object
Configuration for how to split the document.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

llamaparse-split-api-openapi.yml Raw ↑

Other APIs LlamaParse publishes across the network.

LlamaParse Extract API
LlamaParse Classify API
LlamaCloud Index API
LlamaParse Agent Data API
LlamaParse Batch Processing API
LlamaParse Batches API
LlamaParse Beta API
LlamaParse Chat API
LlamaParse Classifier API
LlamaParse Classify API
LlamaParse Configurations API
LlamaParse Data Sinks API
Where this information came from

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