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 Page Figures API

The Page Figures API from LlamaParse — 4 operation(s) for page figures.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Page Figures. 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 4 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 4 schemas 3 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 Page Figures 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 — 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Page Figures 4
GET
/api/v1/files/{id}/page-figures
List File Pages Figures
list_file_pages_figures_api_v1_files__id__page_figures_get 4 params → 200422
GET
/api/v1/files/{id}/page-figures/{page_index}
List File Page Figures
list_file_page_figures_api_v1_files__id__page_figures__page_index__get 5 params → 200422
GET
/api/v1/files/{id}/page-figures/{page_index}/{figure_name}
Get File Page Figure
get_file_page_figure_api_v1_files__id__page_figures__page_index___figure_name__get 6 params → 200422
POST
/api/v1/files/{id}/page-figures/{page_index}/{figure_name}/presigned_url
Generate File Page Figure Presigned Url
generate_file_page_figure_presigned_url_api_v1_files__id__page_figures__page_index___figure_name__presigned_url_post 6 params → 200422

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are PageFigureMetadata (7 properties), ValidationError (5 properties), PresignedUrl (3 properties), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
ValidationError
object
5 properties 3 required
PageFigureMetadata
object
7 properties 5 required
PresignedUrl
object
Schema for a presigned URL.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

llamaparse-page-figures-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
#Page Figures
← Back to L APIs
API Details
ID
llamaparse:llamaparse-page-figures-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-page-figures-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/llamaparse-page-figures-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 Page Figures 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.