Get Configuration Metadata
Returns lightweight metadata about the company’s FMV1 configuration — the
latest stored snapshot’s version + contentHash plus
last-modified and last-imported timestamps — without the full
configuration body. Use it for cheap staleness checks and compare-and-set
workflows: compare the contentHash against a previously seen value to
decide whether the configuration CONTENT has changed before pulling the
full export payload. Every configuration write stores a new snapshot,
so any configuration change is reflected here.
The metadata reads the configuration state from the database (resolved from the API key’s tenant), so the request needs no body — POST an empty object.
Required permission: company.configuration:export
This endpoint requires an API key created with the FMV1_CONFIGURATION_MANAGER role. See Authentication for how to create API keys with specific roles.
Authorizations
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
Company identifier
Body
No input is required; the metadata is read from the database. An empty object is accepted.
Response
Configuration metadata returned successfully
Lightweight FMV1 configuration metadata for staleness checks — version identity and timestamps, WITHOUT the full configuration blob.
The monotonic version of the latest stored configuration snapshot (starts at 1; a new snapshot is stored on every configuration import). null when no snapshot has been stored for the company yet. Pair it with contentHash to identify exactly which configuration state you observed.
7
sha256 (lowercase hex) of the canonical serialized configuration for the latest stored snapshot. Content-stable — two equal hashes mean the configuration CONTENT is identical, so this is the token to use for compare-and-set workflows (re-importing identical content stores a new version but the SAME contentHash). null when no snapshot has been stored for the company yet. Every configuration write stores a new snapshot, so any configuration change is reflected here.
"5bdcf0bb62622f29da8ed6d7ed2c0300ff1b934f5b865874b4022541e102721f"
ISO 8601 timestamp of the last configuration change — the latest stored snapshot's creation time — or null when the company has no configuration yet.
"2026-06-25T18:32:10.114Z"
ISO 8601 timestamp of the most recent onboarding configuration import, or null when the company has never imported a configuration.
"2026-06-20T09:15:00.000Z"
