Versioned JSON API
Keep application automation on a documented resource model with stable versioned paths.
Developers
Predictable interfaces for the systems around your content.
Casewelt is designed to integrate through documented HTTP APIs and signed outbound events. The goal is ordinary, dependable infrastructure: stable resource identity, idempotent creates, structured errors and webhook delivery that assumes real networks will retry.
Integration model
Use explicit contracts instead of hidden product shortcuts.
Idempotent creates
Let clients retry safely when a network timeout makes the result uncertain.
Structured errors
Return machine-readable outcomes that distinguish validation, policy and state conflicts.
Signed webhooks
HMAC-SHA256 over the timestamp and body, with a stable event identifier so consumers can deduplicate retries.
At-least-once delivery
Design for reliable retry rather than promising exactly-once behaviour across a distributed boundary.
Separate surfaces
Keep public recipient traffic separate from authenticated organisation automation.
Example
Create once, even when the network makes you ask twice.
A folder-create request can reach the service even if the client never receives the response. An idempotency key lets the caller retry without manufacturing duplicate workspace objects and duplicate audit history.
Read the HTTP examplesPOST /v1/folders
Authorization: Bearer …
Idempotency-Key: 7a1f…
Content-Type: application/json
{
"parent_id": "fld_board",
"name": "Board pack"
}Identity, machines and events
Plug Casewelt into the systems you already run.
Organisation users sign in through OpenID Connect. Automation uses machine principals with enrolled device identity. Outbound events are HMAC-signed, replay-protected and retried for seventy-two hours; administrators can list deliveries and replay a missed event.
The API is versioned REST and JSON, with idempotent creates and problem details that distinguish validation, policy denial and state conflict. Recipient traffic stays on the share surface, separate from organisation automation.
Review the contract
Review the API contract.
Tell us what creates content, what consumes events and which failure modes matter. We can work through the contract with you.