microsoft/api-guidelines

Microsoft REST API Guidelines

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 53 minutes ago
Added to GitGenius on September 2nd, 2026
Created on July 12th, 2016
Open Issues & Pull Requests: 176 (+0)
GitHub issues: Enabled
Number of forks: 2,689
Total Stargazers: 23,331 (+0)
Total Subscribers: 636 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.9 days
Mean response time: 18.9 days
90th percentile: 51.9 days
Tracked items: 3

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 680 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Microsoft REST API Guidelines is a style guide and reference collection for designing REST APIs.

The guidelines address the problem of inconsistency across API design by establishing a shared set of conventions and best practices. The approach works by documenting patterns, naming conventions, error handling strategies, and structural recommendations that teams can apply when building or modifying REST services. The guidelines are published openly to encourage dialogue within the API community and to inspire other organizations to develop and share their own standards.

Teams building Azure services should reference the Azure REST API Guidelines and Considerations for Service Design documents, which provide guidance tailored specifically to Azure service requirements. Teams working on Microsoft Graph services should consult the Microsoft Graph REST API Guidelines and its associated pattern catalog. The tool suits organizations that want to establish consistency across multiple API teams or that are building services within the Microsoft ecosystem. It is most valuable for teams that need to align with either Azure or Graph service standards, though the general Microsoft REST API Guidelines may inform design decisions more broadly.

The project maintains a repository of documents and related materials supporting the guidelines initiative and welcomes contributions through its established contribution guidelines. The tool is positioned as a reference resource rather than an automated enforcement mechanism, relying on teams to apply the documented patterns during their design and development processes.