Creative & technical
API design template
Resources and endpoints with auth, errors, pagination and versioning decisions in one map before writing a spec.
- Best for
- Backend engineers
- Goal
- Design resources, endpoints and conventions
- Layout
- Mind map (right)
- Topics
- 16
How to use it
- One branch per resource.
- Record conventions once under Conventions.
- Export to Markdown as the start of your spec.
- Press Tab to add detail under any topic and Enter for another at the same level.
What’s inside
The full structure as text — the same content you get in the editor.
- API name
- Resource: users
- GET /users
- POST /users
- GET /users/{id}
- Resource: orders
- GET /orders
- POST /orders
- Authentication
- Conventions
- Errors
- Pagination
- Versioning
- Rate limits
- Webhooks
- Open questions
- Resource: users
Last reviewed 2026-10-30. Placeholders are deliberately generic — replace them with your own facts and sources.