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

Opal Rich Text Documents API

## Overview### Client libraries and document formatsRich Text Document endpoints can accept documents in arbitrary formats. The `client_library` attribute identifies the framework or library that generated the document.Currently, the following formats are recognized, though other formats are allowed. When creating or updating documents in these formats, ensure that the `client_library` attribute is consistent with the value provided here:| Format | Client Library ID || --------------------------------------- | ------------------ || [Tiptap 2](https://tiptap.dev) JSON | `tiptap/2.0` |### Document assetsSome documents returned by these endpoints may have an `assets` relationship; these documents will not also have an `asset_references` relationship.

Opal Rich Text Documents API is one of 79 APIs that Opal publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Rich Text Documents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 4 paths. It is described by OpenAPI 3.2.0, at version 3.0.0.

Requests are made against a single base URL, https://login.ouropal.com.

7 operations 4 paths 0 schemas 1 DELETE3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.0
Base URL
https://login.ouropal.com
Authentication
OAuth 2.0, OAuth 2.0, API Key, API Key
Resource Areas
1

Authentication & Security 4

Opal Rich Text Documents API declares 4 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope. It supports OAuth 2.0 (anonymous_oauth) using the clientCredentials flow, exposing 1 scope. An API key is passed in the header as Session-Token (api_key). An API key is passed in the cookie as share_token (presentation_share_cookie).

  • oauth2 — This API uses OAuth 2.0 with the authorization code grant flow. You can find more detailed authentication instructions in the [Authentication Strategies](/api/…
  • anonymous_oauth — The OAuth 2.0 client credentials flow is used for secure server-server requests when Opal does not need to associate a request with a particular Opal user. The…
  • api_key — (Deprecated) This API also supports authentication via an API or session token set in the request headers.
  • presentation_share_cookie — A cookie set and read by the Monolith service that authorizes a non-opal user to view a presentation and the resources within it. Other services can rely on th…

Paths & Operations 7

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

Rich Text Documents 7

Overview Client libraries and document formats Rich Text Document endpoints can accept documents in arbitrary formats. The clientlibrary attribute identifies the framework or libr…

GET
/rich_texts/v3/documents
Get Rich Text Documents available to the authenticated user.
ReadRichTextDocumentsV3 2 params → 200400401422
POST
/rich_texts/v3/documents
Create a new Rich Text Document.
CreateRichTextDocumentV3 body → 201400401404409422
GET
/rich_texts/v3/documents/{rich_text_document_id}
Get a Rich Text Document.
ReadRichTextDocumentV3 2 params → 200400401403404
PATCH
/rich_texts/v3/documents/{rich_text_document_id}
Update an existing Rich Text Document.
UpdateRichTextDocumentV3 2 params body → 200400401404412422
DELETE
/rich_texts/v3/documents/{rich_text_document_id}
Delete a Rich Text Document.
DeleteRichTextDocumentV3 1 param → 204400401422
POST
/rich_texts/v3/documents/{rich_text_document_id}/duplicate
Duplicate a Rich Text Document
DuplicateRichTextDocumentV3 1 param body → 201400401404409422
GET
/rich_texts/v3/get_collaboration_token
Get a JWT for use with the TipTap Collaboration server.
GetCollaborationTokenV3 2 params → 200400401422

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opal-rich-text-documents-api-openapi.yml Raw ↑

Other APIs Opal publishes across the network.

Opal Accounts API
Opal Activities API
Opal Annotations API
Opal Asset Reference Options API
Opal Asset Reference Usage Rights Options API
Opal Asset References API
Opal Assets API
Opal Block Connectors API
Opal Block Custom Field Values API
Opal Block Duplication API
Opal Blocks API
Opal Board Collaborators API
Where this information came from

This is an independent, third-party profile of Opal Rich Text 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.