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 themes API

The themes API from Scalar — 4 operation(s) for themes.

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

Tagged areas include Themes. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 8 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 3.1.1, at version 1.0.1.

8 operations 4 paths 9 schemas 1 DELETE2 GET1 PATCH3 POST1 PUT

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 themes API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 8

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

themes 8
GET
/themes/{slug}
Get a theme document by slug
getthemesSlug 1 param → 200400401403404422500
PATCH
/themes/{slug}
Update themes metadata
patchthemesSlug 1 param body → 200400401403404422500
PUT
/themes/{slug}
Update themes document
putthemesSlug 1 param body → 200400401403404422500
DELETE
/themes/{slug}
Delete a specific themes
deletethemesSlug 1 param → 200400401403404422500
GET
/themes
Get a list of all themes for the team
getthemes → 200400401403404422500
POST
/themes
Create a new theme for the team
postthemes body → 200400401403404422500
POST
/pubsub/theme-updated
PubSub theme updated route
postpubsubThemeUpdated body → 200400401403404422500
POST
/pubsub/theme-deleted
PubSub theme deleted route
postpubsubThemeDeleted body → 200400401403404422500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are theme (5 properties), 404 (2 properties), 422 (2 properties), 403 (2 properties). Each schema is shown below with its type and property counts.

theme
object
5 properties 5 required
nanoid
string
404
object
2 properties 2 required
401
object
2 properties 2 required
slug
string
500
object
2 properties 2 required
400
object
2 properties 2 required
403
object
2 properties 2 required
422
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scalar-themes-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 themes 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.