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 Registry Git API

The registry-git API from Scalar — 11 operation(s) for registry-git.

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

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

This API exposes 12 operations across 11 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

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

12 operations 11 paths 19 schemas 5 GET1 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Server
https://api.scalar.com/core
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 12

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

registry-git 12
PATCH
/registry-git/{asset}/{namespace}/{slug}/config
Patch registry git asset namespace slug config
patchRegistryGitAssetNamespaceSlugConfig 3 params body → 200400401403404422500
GET
/registry-git/{asset}/{namespace}/{slug}/history
Get registry git asset namespace slug history
getRegistryGitAssetNamespaceSlugHistory 5 params → 200400401403404422500
GET
/registry-git/{asset}/{namespace}/{slug}/publishes
Get registry git asset namespace slug publishes
getRegistryGitAssetNamespaceSlugPublishes 3 params → 200400401403404422500
GET
/registry-git/{asset}/{namespace}/{slug}/source
Get registry git asset namespace slug source
getRegistryGitAssetNamespaceSlugSource 4 params → 200400401403404422500
GET
/registry-git/{asset}/{namespace}/{slug}/branches
Get registry git asset namespace slug branches
getRegistryGitAssetNamespaceSlugBranches 5 params → 200400401403404422500
POST
/registry-git/{asset}/{namespace}/{slug}/branches
Post registry git asset namespace slug branches
postRegistryGitAssetNamespaceSlugBranches 3 params body → 200400401403404422500
GET
/registry-git/{asset}/{namespace}/{slug}/file
Get registry git asset namespace slug file
getRegistryGitAssetNamespaceSlugFile 4 params → 200400401403404422500
POST
/registry-git/{asset}/{namespace}/{slug}/publish
Post registry git asset namespace slug publish
postRegistryGitAssetNamespaceSlugPublish 3 params body → 200400401403404422500
POST
/registry-git/{asset}/{namespace}/{slug}/provision
Post registry git asset namespace slug provision
postRegistryGitAssetNamespaceSlugProvision 3 params → 200400401403404422500
POST
/registry-git/{asset}/{namespace}/{slug}/link-external
Post registry git asset namespace slug link external
postRegistryGitAssetNamespaceSlugLinkExternal 3 params body → 200400401403404422500
POST
/registry-git/{asset}/{namespace}/{slug}/unlink-external
Post registry git asset namespace slug unlink external
postRegistryGitAssetNamespaceSlugUnlinkExternal 3 params → 200400401403404422500
POST
/registry-git/{asset}/{namespace}/{slug}/propose
Post registry git asset namespace slug propose
postRegistryGitAssetNamespaceSlugPropose 3 params body → 200400401403404422500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are registry-publish (13 properties), registry-git-binding (8 properties), linked-repository (6 properties), 403 (2 properties). Each schema is shown below with its type and property counts.

doc-source
404
object
2 properties 2 required
422
object
2 properties 2 required
registry-asset
string
nanoid
string
slug
string
namespace
string
timestamp
integer
registry-publish
object
13 properties 13 required
version
string
401
object
2 properties 2 required
registry-git-external
registry-git-binding
object
8 properties 8 required
403
object
2 properties 2 required
400
object
2 properties 2 required
linked-repository
object
6 properties 6 required
500
object
2 properties 2 required
registry-publish-source
string
linked-repository-remote

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scalar-registry-git-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 API Docs API
Scalar Auth API
Scalar Docs API
Scalar Docs Projects API
Where this information came from

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