microsoft/api-guidelines

View on GitHub

Microsoft REST API Guidelines

Stars: 23.3k
Forks: 2.7k
Open beginner issues: 0
Indexed issues: 129

Dominant language: No language data
License: No license data
Last GitHub push: Aug 5, 2026
Latest indexed: Sep 19, 2026
Contributing guide: Contributing guide
Code of conduct: Code of conduct
Beginner labels: No beginner labels indexed
PR merge metrics: No merged PRs in 30d

Beginner friendly Everything

Open All

129 open issues indexed

Updated Azure Guidelines: Filtering Open

Azure Guidelines

Difficulty 5/5 Over a week Newbie friendliness 20/100

microsoft/api-guidelines#247 · Opened Jun 18, 2021
Capture rules relative to required fields and how they should be modeled in OpenAPI Open

Azure Guidelines enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 35/100

microsoft/api-guidelines#237 · Opened Jun 2, 2021
Request for additional guidelines for nested/embedded collections Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#230 · Opened May 11, 2021
Documenting OData $Filter in Open API Specification Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#228 · Opened Mar 29, 2021
Error details for stepwise long-running operations Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#222 · 1 comment · Opened Nov 27, 2020
Proposal: Enable retries for non-idempotent operations using client provided "logical request" tokens. Open

Difficulty 5/5 Over a week Newbie friendliness 35/100

microsoft/api-guidelines#209 · 8 comments · Opened Jul 9, 2020
Which one to choose for error response RFC7807 specifications or Json API specifications or Microsoft's custom specifications Open

Difficulty 5/5 Over a week Newbie friendliness 20/100

microsoft/api-guidelines#206 · 1 comment · 4 reactions · Opened Jun 11, 2020
PII used in example of good URL Open

Difficulty 1/5 Under an hour Newbie friendliness 55/100

microsoft/api-guidelines#190 · 1 reaction · Opened Feb 19, 2020
Inconsistent details example Open

Difficulty 1/5 Under an hour Newbie friendliness 45/100

microsoft/api-guidelines#182 · 1 comment · Opened Jul 18, 2019
Turn into a GitHub Pages website Open

Difficulty 2/5 1-3 hours Newbie friendliness 35/100

microsoft/api-guidelines#178 · 2 comments · 2 reactions · Opened Apr 10, 2019
Naming convention for bulk operations? Open

Difficulty 5/5 Over a week Newbie friendliness 20/100

microsoft/api-guidelines#171 · 1 reaction · Opened Jan 29, 2019
Filters: "in" operator Open

Difficulty 5/5 Over a week Newbie friendliness 35/100

microsoft/api-guidelines#168 · Opened Dec 18, 2018
Align error responses with ProblemDetails specification (RFC 7807) ? Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#167 · 22 reactions · Opened Dec 17, 2018
Question: request pattern for non CRUD operations Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#110 · 2 comments · Opened Jun 8, 2018
Handling canonical dictionaries in resources Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#106 · Opened Apr 17, 2018
@nextLink vs. nextLink Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#99 · Opened Nov 13, 2017
Difference between branches master and vNext Open

Difficulty 3/5 1-2 days Newbie friendliness 20/100

microsoft/api-guidelines#97 · 4 comments · 3 reactions · Opened Sep 25, 2017
Questions: Are there any existing query string parser for suggested filter operations in section 9.7.1 ? Open

Difficulty 3/5 1-2 days Newbie friendliness 25/100

microsoft/api-guidelines#96 · 5 comments · 6 reactions · Opened Sep 18, 2017
Question: Validation tool / Compliance tests Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#89 · 1 reaction · Opened Jun 23, 2017
Feature request: clearer (semantic?) versioning; version tags Open

Difficulty 2/5 1-3 hours Newbie friendliness 35/100

microsoft/api-guidelines#78 · 3 comments · 1 reaction · Opened Jan 23, 2017
[Question] Long running operations on 200 with a Retry-After VS other standards (e.g. w3.org) Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#76 · 2 comments · Opened Nov 23, 2016
When creating a resource that returns an empty body, should 201 or 204 win? Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#71 · 6 comments · Opened Sep 27, 2016
Response code 409 instead of 404 when PATCHing against nonexisting resource? Open

Difficulty 2/5 1-3 hours Newbie friendliness 48/100

microsoft/api-guidelines#69 · 4 comments · Opened Sep 16, 2016
URL path camelCase vs underscore vs dash etc. Open

Difficulty 5/5 Over a week Newbie friendliness 30/100

microsoft/api-guidelines#67 · 9 comments · 14 reactions · Opened Sep 14, 2016
Partial URLs in 201 Created Location header? Open

Difficulty 3/5 1-2 days Newbie friendliness 35/100

microsoft/api-guidelines#51 · 4 comments · Opened Jul 24, 2016
Feedback on Dates and Times in Section 11 Open

Difficulty 4/5 3-5 days Newbie friendliness 35/100

microsoft/api-guidelines#22 · 4 comments · 5 reactions · Opened Jul 20, 2016
GET urls often fail to meet the relevant spec standards Open

Difficulty 4/5 3-5 days Newbie friendliness 30/100

microsoft/api-guidelines#14 · 12 comments · Opened Jul 19, 2016
how to identify canonical URIs (section 7.3) Open

Difficulty 1/5 Under an hour Newbie friendliness 38/100

microsoft/api-guidelines#13 · 2 comments · 1 reaction · Opened Jul 19, 2016
Potential alternative to the new "Operation-Location" header Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

microsoft/api-guidelines#10 · 5 comments · 23 reactions · Opened Jul 19, 2016

microsoft/api-guidelines

Get new issues in your inbox