zalando/restful-api-guidelines

A model set of guidelines for RESTful APIs and Events, created by Zalando

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 3 hours ago
Added to GitGenius on September 21st, 2026
Created on April 1st, 2016
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 449
Total Stargazers: 3,251 (+0)
Total Subscribers: 76 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.2 days
Mean response time: 20.3 days
90th percentile: 56.0 days
Tracked items: 26

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,445 days
Stale 30+ days: 7
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • guideline-change (11)
  • enhancement (6)
  • discussion (5)
  • editorial (3)
  • question (3)
  • bug (2)
  • help wanted (2)
  • no-zally-change (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Restful-api-guidelines is a comprehensive set of guidelines for designing RESTful APIs and event-driven systems.

The project addresses the challenge of maintaining consistency across APIs developed by different teams. When APIs lack uniform design patterns, adoption becomes difficult and clients struggle to use them correctly. Zalando created these guidelines to establish a shared standard that makes APIs appear as though designed by a single cohesive team. The approach documents best practices and common patterns encountered during RESTful API development, providing concrete answers to recurring design questions rather than abstract principles alone.

Teams building REST APIs should adopt these guidelines when consistency across multiple services matters—particularly in organizations with distributed development teams or public-facing APIs. The guidelines work best for teams willing to challenge their existing API designs against a comprehensive standard. They suit projects where reducing friction between API producers and consumers is a priority. The document is positioned as a living reference rather than a fixed specification, encouraging teams to use it as a starting point for their own API governance while contributing back learnings from their experiences.

The project maintains active development with regular updates reflecting evolving practices and team learnings. Documentation is kept current through automated build processes that validate the guidelines. The maintainers actively refine the content based on real-world application within their organization and community feedback.