Product
API v2 is live: webhooks, richer events, and a public OpenAPI spec
API v2 expands Fauward's integration surface with richer event payloads, documented webhook delivery, and a public OpenAPI description that makes implementation materially easier for engineering teams.
What changed in v2
The release adds more explicit event structures, better tenant webhook control, and cleaner idempotency expectations around write operations.
That combination matters for engineering teams integrating Fauward into ERPs, finance stacks, customer apps, or carrier workflows where retries and event consistency are not optional.
- Structured webhook payloads for shipment and invoice lifecycle events
- Improved idempotency for safer retry behaviour
- A public OpenAPI contract for faster implementation and review
Why this reduces integration risk
Operational integrations often fail because teams reverse-engineer behaviour from partial examples. A versioned schema and clearer event model cut that ambiguity down.
The result is less time spent building adapters around guesswork and more time spent shipping the workflows that actually matter to the business.
What teams can build with it
Engineering teams can now wire shipment creation, invoice handling, notifications, and reporting pipelines into Fauward with less custom glue.
For scaling tenants, that means a cleaner path from initial setup to production-grade automation across operations and finance.