technicaldiagrams.com
← Code & terminals

HTTP exchange

Put a request next to its response.

HTTP exchangeExplain an endpoint with headers, status, and a short payload. All values are illustrative example data.Create a documentHTTP exchange · illustrative payloadRequestResponse1POST /v1/documents2Content-Type: application/json34{5 "title": "Architecture"6}1HTTP/1.1 201 Created2Content-Type: application/json34{5 "id": "doc_42",6 "title": "Architecture"7}
Live SVG · all content is illustrative

Make it yours

Edit labels & content

Change the text directly. Use the scene editor to move or add elements.

Edit individual elements

Choose a shape or text element, then change its properties. Related labels and connectors have separate coordinates.

Edit scene JSON

Change positions, dimensions, paths, and labels. Apply validates the scene before changing the preview. Primitive reference ↗

Review this diagram

These ratings help you compare how an example looks and how much work it takes to change. They are initial assessments of the example, not guarantees of correctness.

Appearance 92/100Ease of changes 95/100Overall 93/100Initial assessment

Your scores and review history stay in this browser. Export reviews to keep a copy. Read the rubric.

    Use this when

    Explain an endpoint with headers, status, and a short payload.

    Choose another form when

    The API needs a full schema or interactive request execution.

    Built from

    PanelText blockLabel

    Two text panels are easy to customize; long payloads should move to reference docs.

    This example uses explicit positions. Check labels and connections after changing its content.

    Give your agent this reference

    Use the example to show your agent the form you want. Describe your system or provide your source material, then ask it to generate an adapted diagram and inspect the result.

    Includes the reference URL, current scene, and settings. Paste it into your own agent.

    Read the agent workflow ↗

    Take the source

    The SVG is self-contained. The JSON preserves editable primitives and your presentation settings. Labels remain text; shapes remain vectors.

    Original scene JSON ↗
    Controls, limits, and embedding ↗