List Seed Options
Lists the seed selection surface: the valid starterSheet variants accepted
by the seed and seed/generate endpoints — each with a human-readable
description and a marker for the one applied when starterSheet is omitted —
AND the full starter-module catalog (#3428) for the explicit modules
selection on seed. Each module carries its axis group, whether it is in
the default selection, and whether it is always on.
Both lists are sourced from a single in-code registry/catalog, so this
discovery surface can never drift from the names and module ids the seed
endpoints actually accept. Use it to discover the valid values before calling
seed or seed/generate, instead of probing with a bogus name and reading
the 400.
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
Response
The valid starter variants and the default
The valid starterSheet variants — each with a description and a default marker — the default name applied when starterSheet is omitted, AND the full starter-module catalog for the explicit modules selection. All sourced from a single in-code registry/catalog, so they cannot drift from what the seed endpoints accept.
The variant name applied when starterSheet is omitted.
The valid starter variants, in registry order.
The selectable starter modules (checkbox granularity, #3428) a caller can pass in the modules array on POST /configuration/seed, in catalog order.
