Sequence diagram examples.
Same tool, four requests. Every drawing below is a real render.
Rather start from a finished drawing? Browse 39 sequence diagram templates →
What a sequence diagram is.
A sequence diagram shows messages exchanged between named participants in time order. Lifelines identify who is involved, while arrows show requests, responses and asynchronous messages.
Use it when the important question is who calls whom and what happens next. Conditional branches, loops and parallel work can be shown directly in the interaction.
- Standard
- OMG UML 2.5.1 §17 (Interactions)
- Engine
- schematex-sequence
- Editable
- Double-click text, drag nodes
- Export
- SVG · PNG · PDF
Who uses sequence diagrams.
API and service interactions that document requests, responses and failure paths.
Cross-service workflows that show parallel work and compensation in an order saga.
ETL exchanges between sources, transformation services and a target store.
How to make a sequence diagram in three steps.
Describe it
One paragraph is enough to start.
See the drawing
Drawn by the right engine.
Say what changes
Every edit keeps a version.
Common questions
What is a sequence diagram?
It is a UML interaction diagram that shows messages between participants in chronological order.
When should I use a sequence diagram?
Use one to document an API call flow, user journey, integration, background job or any behavior where message order matters.
Can it show errors and conditional paths?
Yes. Use alternative branches for success and error outcomes, and optional blocks for behavior that may not occur.
Can it show loops or parallel work?
Yes. A loop shows repeated messages, while a parallel fragment shows interactions that can run concurrently.
Other drawings for the same work.
Create your sequence diagram.
Free account, no card. Describe the participants and the messages between them.
Open the editor