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

Scalar api-docs API

The api-docs API from Scalar — 13 operation(s) for api-docs.

Scalar api-docs API is one of 30 APIs that Scalar publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include api-docs. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 19 operations across 13 paths, and defines 14 schemas. It is described by OpenAPI 3.1.1, at version 1.0.1.

19 operations 13 paths 14 schemas 3 DELETE5 GET2 PATCH9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.1
API Version
1.0.1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Scalar api-docs API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 19

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

api-docs 19
POST
/managed-doc/access-group
Adds an access group to a managed doc
postmanagedDocAccessGroup body → 200400401403404422500
DELETE
/managed-doc/access-group
Removes an access group from a managed doc
deletemanagedDocAccessGroup body → 200400401403404422500
POST
/managed-doc/available
Checks if a registry slug is available
postmanagedDocAvailable body → 200400401403404422500
GET
/managed-doc/{namespace}
Get a list of all documents for the namespace
getmanagedDocNamespace 1 param → 200400401403404422500
POST
/managed-doc/{namespace}
Creates a new api document for the namespace
postmanagedDocNamespace 1 param body → 200400401403404422500
PATCH
/managed-doc/{namespace}/{slug}
Update metadata for a specific managed document
patchmanagedDocNamespaceSlug 2 params body → 200400401403404422500
DELETE
/managed-doc/{namespace}/{slug}
Delete a specific managed document and all of the related versions
deletemanagedDocNamespaceSlug 2 params → 200400401403404422500
GET
/managed-doc/{namespace}/{slug}
Get a specific managed document
getmanagedDocNamespaceSlug 2 params → 200400401403404422500
GET
/managed-doc/{namespace}/{slug}/version/{semver}
Get a specific managed document version stream
getmanagedDocNamespaceSlugVersionSemver 3 params → 200400401403404422500
PATCH
/managed-doc/{namespace}/{slug}/version/{semver}
Update the registry file content for the doc version
patchmanagedDocNamespaceSlugVersionSemver 3 params body → 200400401403404422500
DELETE
/managed-doc/{namespace}/{slug}/version/{semver}
Delete a specific managed document version
deletemanagedDocNamespaceSlugVersionSemver 3 params → 200400401403404422500
GET
/managed-doc/{namespace}/{slug}/version/{semver}/metadata
Get metadata for a specific api document version
getmanagedDocNamespaceSlugVersionSemverMetadata 3 params → 200400401403404422500
POST
/managed-doc/{namespace}/{slug}/version
Create a new api document version
postmanagedDocNamespaceSlugVersion 2 params body → 200400401403404422500
GET
/managed-doc
Get a list of all documents for a team
getmanagedDoc → 200400401403404422500
POST
/pubsub/api-updated
Registry API updated subscription handler
postpubsubApiUpdated body → 200400401403404422500
POST
/pubsub/api-version-deleted
Registry API updated subscription handler
postpubsubApiVersionDeleted body → 200400401403404422500
POST
/pubsub/api-embed-complete
Registry API Vector embedding complete
postpubsubApiEmbedComplete body → 200400401403404422500
POST
/pubsub/api-embed-failed
Registry API Vector embedding failed
postpubsubApiEmbedFailed body → 200400401403404422500
POST
/managed-doc/{namespace}/{slug}/version/{semver}/tools
Update managed docs MCP tools.
postmanagedDocNamespaceSlugVersionSemverTools 3 params body → 200400401403404422500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are managed-doc (22 properties), managed-doc-version (10 properties), 400 (2 properties), 401 (2 properties). Each schema is shown below with its type and property counts.

namespace
string
managed-doc-version
object
10 properties 6 required
method
string
nanoid
string
404
object
2 properties 2 required
401
object
2 properties 2 required
version
string
slug
string
500
object
2 properties 2 required
managed-doc
object
22 properties 18 required
400
object
2 properties 2 required
403
object
2 properties 2 required
timestamp
integer
422
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scalar-api-docs-api-openapi.yml Raw ↑

Other APIs Scalar publishes across the network.

Scalar API References
Scalar API Client
Scalar Docs
Scalar Registry
Scalar SDKs
Scalar CLI
Scalar access-groups API
Scalar analytics API
Scalar auth API
Scalar docs API
Scalar Docs Projects API
Scalar Forgejo API
Where this information came from

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