Skip to main content

Ingestion Presets

Ingestion Presets

Manage ingestion presets for data intake workflows.

Preset reads and writes are available via: GET /api/v1/ingestion-presets and POST /api/v1/ingestion-presets.

Verify delivery status in endpoint diagnostics.

Loading ingestion presets

Known preset examples

Illustrative schema references — not authoritative backend data.

default-ingestion-profile

Reference

Base ID: app_cohort_2026

Workflow: ingestion

Baseline preset for the standard admissions import path.

scholarship-fast-track

Conflict warning

Base ID: app_scholarship_2026

Workflow: evaluation

Field map overlaps with an older cohort preset and needs backend validation before publish.

Conflict warning

Non-destructive

Potential duplicate preset names or overlapping field maps should remain non-destructive until backend validation exists.

Operations checklist for operational fallbacks.

Malformed payload preview

Use this sample to align validation expectations before the preset API is introduced.

{
  "name": "cohort-intake",
  "baseId": 42,
  "workflow": "ingestion",
  "mapping": "expected-object-not-string"
}

Migration checklist

Steps that remain outside the authoritative preset CRUD surface.

1

Validate preset schema

Keep base, workflow, and config ownership aligned with the V2 API schema.

2

Use authoritative API writes

Write controls must send idempotency keys and refresh the backend list.

POST/PATCH/DELETE /api/v1/ingestion-presets

3

Plan import/export separately

Static import and export examples stay non-authoritative until dedicated endpoints exist.

Track progress in endpoint diagnostics and keep runtime defaults in Runtime preferences until presets ship.