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

Omni Documents v2 API

A draft-based workflow for creating and editing documents: create a document, patch a draft, then publish. Replaces the one-shot `PUT`/`PATCH` v1 document write endpoints.

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

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

This API exposes 7 operations across 6 paths, and defines 17 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 2 base URLs: https://{instance}.omniapp.co/api, https://{instance}.playground.exploreomni.dev/api.

7 operations 6 paths 17 schemas 2 GET2 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://blobsrus.omniapp.co/api
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Omni Documents v2 API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP bearer tokens (JWT) (orgApiKey). By default, every request must be authenticated.

  • bearerAuth — Can be either an [Organization API Key](/api/authenticationorganization-api-keys) or [Personal Access Token (PAT)](/api/authenticationtoken-types). Include in…
  • orgApiKey — Requires an [Organization API Key](/api/authenticationorganization-api-keys). Personal Access Tokens (PATs) are not supported for this endpoint. Include in the…

Paths & Operations 7

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

Documents v2 7

A draft-based workflow for creating and editing documents: create a document, patch a draft, then publish. Replaces the one-shot PUT/PATCH v1 document write endpoints.

POST
/v2/documents
Create document
documentsV2Create body → 201400401403404405
GET
/v2/documents/{documentId}
Get document state
documentsV2Get 2 params → 200401403404422
PATCH
/v2/documents/{documentId}/draft
Create draft and patch document
documentsV2PatchDraft 1 param body → 200400401403404405409422
POST
/v2/documents/{documentId}/draft/publish
Publish draft
documentsV2PublishDraft 1 param → 200400401403404405409
GET
/v2/documents/{documentId}/draft/{draftId}
Get draft state
documentsV2GetDraft 3 params → 200401403404422
PATCH
/v2/documents/{documentId}/draft/{draftId}
Patch draft
documentsV2PatchDraftByIdentifier 2 params body → 200400401403404405409422
PUT
/v2/documents/{documentId}/identifier
Rename document identifier
documentsV2UpdateIdentifier 1 param body → 200400401403404405409429

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are DocumentsV2QueryPresentation (16 properties), DocumentsV2CreateBody (10 properties), DocumentsV2CreateDraftBody (10 properties), DocumentsV2PatchDraftBody (9 properties). Each schema is shown below with its type and property counts.

DocumentsV2ReadResponse
object
Current document (or draft) state. Round-trippable: submit this verbatim as a draft PATCH body. containers, controls, and settings are dashboard-scoped and omi…
8 properties 3 required
DocumentsV2SettingsRead
object
5 properties 5 required
DocumentsV2Control
object
A dashboard control (filter). The full config grammar — control type, field bindings, filter values, and (for multi-field filters) the recursive composite-filt…
DocumentsV2QueryPresentationsRead
object
2 properties 2 required
DocumentsV2CreateDraftBody
object
The draft-route patch body plus an optional branchId selecting the branch the new draft is attached to.
10 properties
DocumentsV2SettingsPatch
object
Document settings. Shallow-merged with the existing settings.
5 properties
DocumentsV2Containers
array
Container layout array (grid / stack / page / reference containers, recursively nested). On a patch, when present this fully replaces the existing layout. The…
DocumentsV2PatchDraftBody
object
The content/metadata diff applied to a draft. All fields optional — only the sections present are changed.
9 properties
DocumentsV2QueryPresentationsPatch
object
Query presentations (tabs/tiles) keyed by record key.
2 properties
DocumentsV2PublishDraftResponse
object
3 properties 3 required
DocumentsV2CreateBody
object
10 properties 2 required
DocumentsV2ControlsPatch
object
Dashboard filters/controls keyed by control ID.
2 properties
Error
object
2 properties
DocumentsV2CreateResponse
object
3 properties 3 required
DocumentsV2PatchDraftResponse
object
4 properties 4 required
DocumentsV2QueryPresentation
object
A single tab/tile. The server owns internal tile identity — callers never send miniUuid; tiles are addressed by their record key in queryPresentations.data.
16 properties 1 required
DocumentsV2ControlsRead
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

omni-documents-v2-api-openapi.yml Raw ↑

Other APIs Omni publishes across the network.

Omni AI API
Omni AI Credit Controls API
Omni AI Eval API
Omni AI Model Suggestions API
Omni AI Routines API
Omni API Tokens API
Omni Connection environments API
Omni Connections API
Omni Content API
Omni Content migration API
Omni Content validator API
Omni Dashboard downloads API
Where this information came from

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