About sequence diagram generator
Write who sends what to whom, one message per line, and get a sequence diagram.
Good for
- Explaining API calls and login flows.
- Reviewing how services interact.
- Documenting a bug's timeline.
A worked example
Write 'Browser -> Server: GET /profile', 'Server -> Database: query user' and 'Database --> Server: user row'. The diagram shows the participants across the top and the messages in order below, which is ideal for explaining who calls whom in an API flow.
Tips
- Use solid arrows for requests and dashed for responses.
- Name participants clearly and keep their number small.
- Add notes for important rules, such as retries.
Loops and alternatives
Sequence diagrams can show loops, alternatives and parallel steps with blocks such as loop, alt and par, which help describe retries and error paths.
Keep it short
A sequence diagram works best with five or fewer participants and one scenario. Draw separate diagrams for the success path and each error path.
