Skip to main content
POST
Get Configuration JSON Schema

Authorizations

Authorization
string
header
required

User-principal OAuth 2.0 Bearer authentication. Send a user-scoped Auth0 access token (audience = the app API audience) as Authorization: Bearer <jwt>. The request resolves to the user's identity and is authorized by their Role on the {companyId} in the path — the same role-based permissions the web app enforces. This is the path the MCP connector uses to act on a user's behalf; endpoints that accept it list both BearerAuth and ApiKeyAuth.

Path Parameters

companyId
string<uuid>
required

Company identifier

Body

application/json

No input is required; the schema is a framework constant. An empty object is accepted.

Response

The JSON Schema for the FMV1 configuration contract

A JSON Schema (Draft 2020-12) document describing the FMV1 configuration body. Treated as an opaque schema document — its top-level keys are the JSON-Schema keywords ($schema, type, properties, …), not config fields.