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

API Blueprint API

The API Blueprint API is the parsing service operated at api.apiblueprint.org by the API Blueprint project. It parses API Blueprint and Swagger 2.0 documents into the Refract Parse Result Namespace (API Elements) and composes API Blueprint back out of API Elements. The service is open, requires no authentication or API key, and is driven entirely by HTTP content negotiation. Probed live and answering on 2026-09-02 even though every apiaryio GitHub repository was archived on 2024-11-08.

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

This API exposes 1 JSON Schema definition.

Tagged areas include API Design, Parsing, and Specification Language. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and 1 JSON Schema.

This API exposes 5 operations across 5 paths, organized into 5 resource areas, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version 1A.

Requests are made against a single base URL, https://api.apiblueprint.org.

5 operations 5 paths 6 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1A
Base URL
https://api.apiblueprint.org
License
MIT
Resource Areas
5

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 1 GET, 4 POST. They span 5 resource areas: Service Root, Parser, Composer, Validate, Transform. Each is listed below with its method, path, parameters, and response codes.

Service Root 1

Entry point listing the available affordances.

GET
/
List
listAffordances → 200
Parser 1

Parse an API description format into API Elements.

POST
/parser
Parse
parseApiDescription 1 param body → 200406415422
Composer 1

Compose an API description format from API Elements.

POST
/composer
Compose
composeApiDescription 1 param body → 200415
Validate 1

Validate an API description and return its annotations. Advertised by the live service root; absent from the provider's published contract.

POST
/validate
Validate
validateApiDescription body → 200400405415
Transform 1

Convert an API description between formats through a JSON envelope. Advertised by the live service root; absent from the provider's published contract.

POST
/transform
Transform
transformApiDescription body → 200400405406415

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ApiElement (4 properties), TransformRequest (3 properties), TransformResponse (2 properties), Error (1 property). Each schema is shown below with its type and property counts.

ServiceRoot
object
HAL representation of the service root.
1 property 1 required
Error
object
The vnd.error media type as used by this API. Carries a single human readable message.
1 property 1 required
ApiElement
object
A Refract / API Elements element. Structure is defined by the API Elements element schema, saved in this repository at json-schema/api-blueprint-api-elements-e…
4 properties 1 required
ParseResult
A Refract Parse Result element (element: parseResult) whose content carries the parsed API category plus any annotations.
TransformRequest
object
JSON envelope used by /validate and /transform. Field names were established by probe, from the service's own 400/415/406 error messages.
3 properties 2 required
TransformResponse
object
JSON envelope returned by /transform.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

api-blueprint-parsing-service-openapi.yml Raw ↑

Other APIs API Blueprint publishes across the network.

API Blueprint
Where this information came from

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