Artifacts
Versioned APIs, events, jobs, workflows, and webhooks in the catalog.
The catalog is the product surface Connect publishes. YAML in git is the seed. Portal and SAPI manage lifecycle after load.
Open OverviewKinds
| Kind | What it is |
|---|---|
| API | Ingress path, methods, auth (jwt · api-key · hmac) |
| Event | Topic, record key, DLT, consumer group |
| Job | Trigger (SCHEDULE · MESSAGE · WEBHOOK · API · MANUAL). Never the outbox publisher |
| Workflow | tasks[] IR (call · listen · wait · switch · fork · end). Optional webhookBind |
| Webhook | Inbound HMAC ingress and/or outbound subscription |
| Stream | Camel Kafka processor with a window |
Unique row: (artifact_id, version). GET without ?version= prefers published, then highest version.
Read vs write
| Action | Where |
|---|---|
| List / get published | Experience GET /api/v1/catalog |
| Create / update / publish | Portal and System APIs |
Kernel ops (/api/v1/ops, /api/v1/system) are not the public developer catalog.
If this fails
| Symptom | Cause |
|---|---|
| Artifact missing after deploy | CONNECT_CATALOG_DIR not mounted, or classpath seed false with empty dir |
| Designer save vanished on restart | File seed overwrote — Portal-saved spec should win; check seed flags |
Next: Publish and lifecycle