Skip to main content
POST
Describe Configuration (run-down)

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 — an empty object (or no body) is accepted.

Response

The configuration run-down.

The configuration run-down — a small orientation summary of the company's FMV1 configuration. Lists every top-level entity, custom object, and option set with a count; it does not list individual fields (use the per-entity describe endpoint for those).

revision
string
required

Identifies the exact stored configuration this run-down was built from (a hash over the full config body; the same token the patch optimistic-concurrency check uses as baseRevision).

entities
object[]
required

The fixed top-level entities, each with its field count.

customObjects
object[]
required

The company's custom objects, each with its sub-field count.

optionSets
object[]
required

The company's option sets, each with its option count and lock state.