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

Scribe Documents API

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

Scribe Documents API is one of 3 APIs that Scribe 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 and an API reference.

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

Requests are made against a single base URL, https://public-api.scribehow.com.

2 operations 2 paths 6 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://public-api.scribehow.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Scribe Documents API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (APIKey).

  • APIKey — API key authentication. Add your API key as the header value. Example: X-API-Key: sc1234567890abcdefg.hijklmnopqrstuvwx

Paths & Operations 2

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

Documents 2
GET
/v1/documents/
List documents
v1_get_documents 8 params → 200400401403429
GET
/v1/documents/{id}/
Retrieve a document
v1_retrieve_document 1 param → 200400401403429

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are DocumentDetailDB (11 properties), PaginatedDocumentDetailDBList (4 properties), UserDB (3 properties), ActionDB (3 properties). Each schema is shown below with its type and property counts.

DocumentDetailDB
object
A document with its full body — actions for Scribe Documents and structured content for Knowledge Pages.
11 properties 10 required
TypeEnum
string
PaginatedDocumentDetailDBList
object
4 properties 2 required
ActionDB
object
3 properties 3 required
Team
object
A team — used both as the owner of a document and as a filter target.
2 properties 2 required
UserDB
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scribe-documents-api-openapi.yml Raw ↑

Other APIs Scribe publishes across the network.

Scribe Search API
Scribe Teams API
Where this information came from

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