HTTP sends a request to an endpoint using a method such as GET or POST. The response includes a status code and may include a structured body. GET usually reads a resource; POST commonly submits work. Follow the API contract instead of guessing that two methods are interchangeable.
This simulator only uses endpoints defined in the exercise fixture. It never sends a network request. A configured 4xx or 5xx response is a failed action, and run-after recovery can handle that failure. A 200 response still needs inspection: the body may describe a business status such as Held rather than Ready. Keep transport success separate from the business decision. The hands-on tasks record the request and check the downstream body fields, so a hardcoded success message cannot conceal a changed response.