Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Taxi - Describe How Your APIs and Data Relate Conversion API

Convert existing specs to Taxi format

This API exposes 1 operation across 1 path, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

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

1 operations 1 paths 3 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Server
https://api.taxilang.org
License
Resource Areas
1

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Conversion 1

Convert existing specs to Taxi format

POST
/convert/openapi
Convert from OpenAPI
convertFromOpenApi body → 200400

Schemas 3

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

ConversionResult
object
4 properties
Error
object
3 properties
ConversionRequest
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

taxi-conversion-api-openapi.yml Raw ↑