CP19 · Implemented

Versioned HTTP API

Plain HTTP is Trestle's product boundary. OpenAPI and reference clients describe that boundary; they do not create privileged SDK-only capabilities.

GET /api/v1/openapi.json
GET /api/v1/capabilities
GET /admin/v1/api/schema

Capabilities return the API version, implemented feature identifiers and machine-readable limits. Authenticated schema inspection returns collection fields without record data or credentials.

Curl first

curl "$TRESTLE_URL/api/v1/collections/issues/records?limit=25" \
  -H "Authorization: Bearer $TRESTLE_TOKEN"

Every structured error can carry the response's X-Request-ID for correlation. Clients must branch on error codes, not prose.

OpenAPI boundary

The downloadable OpenAPI 3.1 document covers the stable public route families and security schemes. Tutorial prose remains separate because operational decisions cannot be generated from schemas alone.