That is intentionally left out of this diagram for two reasons

(1) - That detail is covered by API specs like Swagger (2) - Two endpoints that return the same resource (of the back of two different operations on the same resource) may return a slightly different format/field. This is up to the developer of the API and best captured in API spces.

Thank you for the answer.

By the sounds of it, you'd use this as an overview and use something like Swagger for the actual details of each endpoint.

(For that matter, if you output the diagram in a format that supports hyperlinks like SVG or PDF, you could link from the diagram directly into Swagger.)

That's exactly the point of this diagram - make audience familiar with the API's domain before throwing them into useful detail of specs like Swagger.

You brought another very good point about being able to hyperlink directly into Swagger, something we have been talking about a lot recently. Unfortunately, we have not come across a tool that does this satisfactorily.