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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
LlamaParse

LlamaParse Retrieval API

The Retrieval API from LlamaParse — 4 operation(s) for retrieval.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Retrieval. 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 4 paths, and defines 24 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.

4 operations 4 paths 24 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.cloud.llamaindex.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

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.

Retrieval 4
POST
/api/v1/retrieval/retrieve
Retrieve
retrieve_api_v1_retrieval_retrieve_post 3 params body → 200422
POST
/api/v1/retrieval/files/find
Find Files
find_files_api_v1_retrieval_files_find_post 3 params body → 200422
POST
/api/v1/retrieval/files/grep
Grep File
grep_file_api_v1_retrieval_files_grep_post 3 params body → 200422
POST
/api/v1/retrieval/files/read
Read File
read_file_api_v1_retrieval_files_read_post 3 params body → 200422

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are RetrieveParams (10 properties), StaticFields (8 properties), FileGrepParams (6 properties), RetrievalResult (5 properties). Each schema is shown below with its type and property counts.

FileGrepParams
object
Grep within a specific file's parsed content.
6 properties 3 required
FileReadResult
object
File read result.
1 property 1 required
MongoStaticFilters
object
1 property
FileFindResult
object
Paginated file find results.
3 properties 1 required
MetadataDict
object
FilterType_str_
object
2 properties 2 required
FileGrepResult
object
Paginated grep results for a file.
3 properties 1 required
FileGrepMatch
object
A single grep match within a file.
3 properties 3 required
FileFindParams
object
Search for files by name.
5 properties 1 required
FilterType_Union_str__int__bool__float__
object
2 properties 2 required
RetrievalResult
object
A single retrieval result.
5 properties 1 required
RerankConfig
object
Reranking configuration to apply after hybrid search.
2 properties
FilterType_Union_int__float__
object
2 properties 2 required
MetadataValue
RetrieveResult
object
Response containing retrieval results.
1 property 1 required
StaticFields
object
Built-in fields stored for every exported chunk.
8 properties
HTTPValidationError
object
1 property
RetrieveParams
object
Hybrid retrieval request combining vector and full-text search.
10 properties 2 required
FileFindEntry
object
A file returned by find.
2 properties 2 required
FileReadParams
object
Read parsed content of a specific file.
4 properties 2 required
MetadataScalarValue
MetadataListValue
array
AttachmentRef
object
Reference to a file attachment, retrievable via GET /api/v1/beta/attachments/{attachmentname}?sourceid=....
3 properties 3 required
ValidationError
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

llamaparse-retrieval-api-openapi.yml Raw ↑

Other APIs LlamaParse publishes across the network.

LlamaParse Extract API
AE Profile APIs.io
LlamaParse Classify API
AE Profile APIs.io
LlamaCloud Index API
AE Profile APIs.io
LlamaParse Agent Data API
AE Profile APIs.io
LlamaParse Batch Processing API
AE Profile APIs.io
LlamaParse Batches API
AE Profile APIs.io
LlamaParse Beta API
AE Profile APIs.io
LlamaParse Chat API
AE Profile APIs.io
LlamaParse Classifier API
AE Profile APIs.io
LlamaParse Classify API
AE Profile APIs.io
LlamaParse Configurations API
AE Profile APIs.io
LlamaParse Data Sinks API
AE Profile APIs.io
#Retrieval
← Back to L APIs
API Details
ID
llamaparse:llamaparse-retrieval-api
Base URL
https://api.cloud.llamaindex.ai
Docs
https://developers.llamaindex.ai/llamaparse/parse/
Provider
LlamaParse
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=llamaparse-retrieval-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/llamaparse-retrieval-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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