API Reference

Public entry point for the JsonFabrica JSON-generation platform. All `/v1/*` routes require an API key sent as `Authorization: Bearer <api-key>`. The gateway resolves the key to a tenant/role via svc-auth and forwards the request to the appropriate internal microservice, injecting trusted `X-Tenant-Id`/`X-Role` headers downstream (callers never set those themselves). `/health` is unauthenticated. **Request-path validation.** The gateway validates and normalizes every proxied `/v1/*` request path before forwarding it. Requests with malformed or out-of-scope paths are rejected with `400 VALIDATION_ERROR`. Dots *inside* a path segment (e.g. `person.firstName`) are fully supported.

Base URL

Authentication

All /v1/* routes require an API key sent as an Authorization header, except the public Billing signup/webhook routes noted on their own page:

Authorization: Bearer <api-key>

The gateway resolves the key to a tenant/role via the internal auth service and forwards the request to the appropriate microservice, injecting trusted X-Tenant-Id / X-Role headers downstream — callers never set those headers themselves. GET /health is unauthenticated.

Error envelope

Every error response — across every endpoint — uses the same shape:

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "\"name\" is required",
    "details": { "field": "name" }
  }
}

Standard error codes

Endpoint groups