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

Jasper Documents API

The Documents API from Jasper — 2 operation(s) for documents.

Jasper Documents API is one of 14 APIs that Jasper publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Documents. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.

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

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

5 operations 2 paths 5 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.jasper.ai/v1
Authentication
API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Jasper Documents API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (X-API-Key). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 2 scopes.

  • X-API-Key — Workspace authentication using API key tokens in the X-API-Key header.
  • oauth2 — User-level authentication using OAuth bearer tokens in the Authorization header.

Paths & Operations 5

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

Documents 5
GET
/v1/documents
Retrieve documents
getAllDocuments 8 params → 200401404500
POST
/v1/documents
Create document
createDocument body → 401404500default
GET
/v1/documents/{documentId}
Retrieve document by ID
getDocumentById 1 param → 200401404500
PATCH
/v1/documents/{documentId}
Update document
updateDocument 1 param body → 200401404500
DELETE
/v1/documents/{documentId}
Delete a document by ID
deleteDocumentById 1 param → 200401404500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are DocumentsData (9 properties), DocumentCreateDto (5 properties), DocumentUpdateDto (5 properties), DocumentResponse (3 properties). Each schema is shown below with its type and property counts.

DocumentUpdateDto
object
5 properties 2 required
DocumentDeleteResponse
object
3 properties 1 required
DocumentCreateDto
object
5 properties 3 required
DocumentsData
object
9 properties 6 required
DocumentResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jasper-documents-api-openapi.yml Raw ↑

Other APIs Jasper publishes across the network.

Jasper Attachments API
Jasper Audiences API
Jasper Command API
Jasper Image Templates API
Jasper Images API
Jasper Knowledge API
Jasper Projects API
Jasper Styles API
Jasper Tasks API
Jasper Templates API
Jasper Usage API
Jasper Users API
Where this information came from

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