Route Configuration

Every collection in Minerva exposes five standard API routes: list, view, create, update, and delete.

Rather than writing custom controllers, you configure how data flows through these routes. This configuration is stored directly in the Blueprint under route_metadata.

The Five Routes

1. list: Queries multiple records
2. view: Fetches a single record
3. create: Inserts a new record
4. update: Modifies an existing record
5. delete: Removes a record

Types of Configurations

Validation Config (DOMAIN_VALIDATOR)

Available on create, update, and delete, validation configs enforce business rules before a mutation commits.

Import Config

Available on create and update, import configs define bulk CSV upload templates and transformation logic.

Export Config

Available on list and view, export configs define Excel or CSV templates and optional transformation logic.

Notification Config

Available on mutation routes, notification configs define event-driven communication flows.

See Notifications for details.

Data Flow Pipeline

When a client hits one of these routes, the request flows through:

1. Authentication scope
2. Blueprint redaction
3. Permission checks
4. Locking checks for mutations
5. Validation
6. Execution
7. Field masking on reads

For updates, blocked fields are preserved during sync so omission does not accidentally clear restricted values.