Browse by Category

+ added · ✎ updated 7d

⚖ Terms of Use

Api_design terms

2 terms of 1444 total

🔌 Contracts between systems that need to trust each other

A well-designed API is a pleasure to integrate; a poorly designed one is a tax on every team that touches it. This category covers REST principles, GraphQL, versioning strategies, authentication patterns, rate limiting, idempotency, error responses, and the design decisions that make APIs intuitive, stable, and a joy to build against.

Sort A → Z Recently Added Recently Updated Difficulty Most Viewed Most Rated Most Shared

Level All Beginner Intermediate Advanced

✕ Clear A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

HTTP Content Negotiation

The HTTP mechanism by which clients declare what formats, languages, and encodings they accept (Accept, Accept-Language, Accept-Encoding) and servers respond with the best match — or 406 Not Acceptable if none fits.

1mo ago api_design intermediate

Hypermedia APIs — HATEOAS

REST APIs that include links in responses — clients discover available actions from the response rather than hardcoding URLs, making APIs self-describing and evolvable.

2mo ago api_design advanced

✓ schema.org compliant