Business process API design: make long-running work understandable
Model asynchronous runs, business state, versioning, authorization, and outcomes through a clear API contract.
Playbook collection / 2 articles
API Architecture.Make the system explain itself.
Design the contract and the operating environment together. These guides cover asynchronous run resources, authorization, durable state, self-hosted boundaries, and recovery responsibilities. An API should explain what work was accepted; its deployment should preserve enough evidence to finish or repair that work after interruption. Start with the interface design, then use the self-hosting review to identify the people and infrastructure responsible for each promise.
Self-hosted process APIs: plan the operational boundary before deployment
Map data paths, access, queues, recovery, and maintenance before moving a processing workflow onto your own infrastructure.
Make the next step a clear one
Build the process.
Not the guesswork.
Start with a map, explore the reference patterns, or open a playbook for the work in front of you.
Open the reference docs