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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Scalar

Scalar API Docs API

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

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 6 JSON Schema definitions.

Tagged areas include Api Docs. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

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

Requests are made against a single base URL, https://api.scalar.com/core.

26 operations 20 paths 30 schemas 3 DELETE8 GET2 PATCH13 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Server
https://api.scalar.com/core
Authentication
HTTP Bearer
Contact
Marc from Scalar
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 26

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

api-docs 26
POST
/managed-doc/access-group
Postmanaged doc access group
postmanagedDocAccessGroup body → 200400401403404422500
DELETE
/managed-doc/access-group
Deletemanaged doc access group
deletemanagedDocAccessGroup body → 200400401403404422500
POST
/managed-doc/available
Postmanaged doc available
postmanagedDocAvailable body → 200400401403404422500
GET
/managed-doc/{namespace}
Getmanaged doc namespace
getmanagedDocNamespace 1 param → 200400401403404422500
POST
/managed-doc/{namespace}
Postmanaged doc namespace
postmanagedDocNamespace 1 param body → 200400401403404422500
PATCH
/managed-doc/{namespace}/{slug}
Patchmanaged doc namespace slug
patchmanagedDocNamespaceSlug 2 params body → 200400401403404422500
DELETE
/managed-doc/{namespace}/{slug}
Deletemanaged doc namespace slug
deletemanagedDocNamespaceSlug 2 params → 200400401403404422500
GET
/managed-doc/{namespace}/{slug}
Getmanaged doc namespace slug
getmanagedDocNamespaceSlug 2 params → 200400401403404422500
GET
/managed-doc/{namespace}/{slug}/version/{semver}
Getmanaged doc namespace slug version semver
getmanagedDocNamespaceSlugVersionSemver 3 params → 200400401403404422500
PATCH
/managed-doc/{namespace}/{slug}/version/{semver}
Patchmanaged doc namespace slug version semver
patchmanagedDocNamespaceSlugVersionSemver 3 params body → 200400401403404422500
DELETE
/managed-doc/{namespace}/{slug}/version/{semver}
Deletemanaged doc namespace slug version semver
deletemanagedDocNamespaceSlugVersionSemver 3 params → 200400401403404422500
GET
/managed-doc/{namespace}/{slug}/version/{semver}/metadata
Getmanaged doc namespace slug version semver metadata
getmanagedDocNamespaceSlugVersionSemverMetadata 3 params → 200400401403404422500
POST
/managed-doc/{namespace}/{slug}/version
Postmanaged doc namespace slug version
postmanagedDocNamespaceSlugVersion 2 params body → 200400401403404422500
GET
/managed-doc
Getmanaged doc
getmanagedDoc → 200400401403404422500
POST
/pubsub/api-updated
Postpubsub api updated
postpubsubApiUpdated body → 200400401403404422500
POST
/pubsub/api-version-deleted
Postpubsub api version deleted
postpubsubApiVersionDeleted body → 200400401403404422500
POST
/pubsub/api-embed-complete
Postpubsub api embed complete
postpubsubApiEmbedComplete body → 200400401403404422500
POST
/pubsub/api-embed-failed
Postpubsub api embed failed
postpubsubApiEmbedFailed body → 200400401403404422500
POST
/managed-doc/{namespace}/{slug}/version/{semver}/tools
Postmanaged doc namespace slug version semver tools
postmanagedDocNamespaceSlugVersionSemverTools 3 params body → 200400401403404422500
POST
/managed-doc/lint
Post managed doc lint
postManagedDocLint body → 200400401403404422500
GET
/registry/{asset}/{namespace}/{slug}/instances
Get registry asset namespace slug instances
getRegistryAssetNamespaceSlugInstances 6 params → 200400401403404422500
GET
/registry/{asset}/{namespace}/{slug}/versions
Get registry asset namespace slug versions
getRegistryAssetNamespaceSlugVersions 3 params → 200400401403404422500
GET
/registry/{asset}/{namespace}/{slug}/instances/{jsonSha}/content
Get registry asset namespace slug instances json sha content
getRegistryAssetNamespaceSlugInstancesJsonShaContent 5 params → 200400401403404422500
POST
/registry/{asset}/{namespace}/{slug}/versions/{version}/active
Post registry asset namespace slug versions version active
postRegistryAssetNamespaceSlugVersionsVersionActive 4 params body → 200400401403404422500
POST
/registry/{asset}/{namespace}/{slug}/source/url
Post registry asset namespace slug source url
postRegistryAssetNamespaceSlugSourceUrl 3 params body → 200400401403404422500
POST
/registry/{asset}/{namespace}/{slug}/source/refresh
Post registry asset namespace slug source refresh
postRegistryAssetNamespaceSlugSourceRefresh 3 params body → 200400401403404422500

Schemas 30

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

nanoid
string
namespace
string
timestamp
integer
404
object
2 properties 2 required
slug
string
403
object
2 properties 2 required
method
string
version
string
400
object
2 properties 2 required
401
object
2 properties 2 required
managed-doc
object
22 properties 18 required
422
object
2 properties 2 required
500
object
2 properties 2 required
managed-doc-version
object
10 properties 6 required
nanoid_2
string
namespace_2
string
timestamp_2
integer
404_2
object
2 properties 2 required
slug_2
string
403_2
object
2 properties 2 required
doc-instance
object
14 properties 14 required
method_2
string
version_2
string
400_2
object
2 properties 2 required
401_2
object
2 properties 2 required
422_2
object
2 properties 2 required
doc-instance-origin
doc-instance-source
string
500_2
object
2 properties 2 required
managed-doc-version_2
object
10 properties 7 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
AE Profile APIs.io
Scalar API Client
AE Profile APIs.io
Scalar Docs
AE Profile APIs.io
Scalar Registry
AE Profile APIs.io
Scalar SDKs
AE Profile APIs.io
Scalar CLI
AE Profile APIs.io
Scalar Access Groups API
AE Profile APIs.io
Scalar Analytics API
AE Profile APIs.io
Scalar Auth API
AE Profile APIs.io
Scalar Docs API
AE Profile APIs.io
Scalar Docs Projects API
AE Profile APIs.io
Scalar Forgejo API
AE Profile APIs.io
#Api Docs
← Back to S APIs
API Details
ID
scalar:scalar-api-docs-api
Server
https://api.scalar.com/core
Docs
https://scalar.com/products/api-references/getting-started
Provider
Scalar
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=scalar-api-docs-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/scalar-api-docs-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

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.