Arazzo is a standard for describing the API workflows users must follow, including each step and the relationships among steps. It turns a scattered set of endpoints into an explicit user journey that an API can help enforce. section 6.6 section 6.7
This matters when direct API access lets bots skip UI-guided steps. Enforcing the documented flow and tracking the latency between steps can reduce automated business-flow abuse, such as buying scarce stock before legitimate customers. section 6.6
Checkout workflow
A checkout workflow can require GET /products/{product_id}, POST /carts, POST /carts/{id}/price, POST /carts/{id}/delivery-slot, and POST /carts/{id}/payment. An Arazzo document places these steps in a workflow, gives each step an ID, checks success criteria such as status codes, and passes outputs such as cart_id to later steps. section 6.6
