zalando/restful-api-guidelines

Issues

• Specify detailed scope in title for rule 192

  #819 opened a month ago by Retro64
  0

• Add rule copy link buttons

  #732 opened 3 years ago by SmilyOrg
  2

• Update change log (and document how to do it)

  #782 opened a year ago by SmilyOrg
  4

• Cursor-based pagination with custom sorting capabilities

  #814 opened 6 months ago by vadimturkov
  1

• Grammar and syntax edits for the style guide

  #813 opened 3 months ago by Kenneth-Stanfield
  10

• /info/version incorrectly interpreted.

  #817 opened 4 months ago by dehora
  0

• Hints on tooling to implement 'partial responses via filtering'

  #806 opened 5 months ago by sareykaj
  3

• missing section on quality of service and rate limits ?

  #809 opened 7 months ago by julienlau
  2

• Guildeline vs Zally: MUST vs SHOULD

  #790 opened 6 months ago by dp1218
  4

• Small fixes to be done by accidental review

  #795 opened 7 months ago by SmilyOrg
  2

• How to implement intervals?

  #805 opened 8 months ago by ePaul
  1

• Clarify when to use `date` vs `datetime`

  #797 opened 7 months ago by SmilyOrg
  2

• Best Practices for implementing APIs (on both client and server side)

  #792 opened 8 months ago by ePaul
  3

• Make rule 111 consistent to 109

  #765 opened 10 months ago by ePaul
  2

• Improvements for Problem guideline (176)

  #763 opened 2 years ago by ePaul
  7

• Guide return code usage for (robust) create

  #685 opened a year ago by tfrauenstein
  1

• Unclear scope of recommendation against total count remark

  #731 opened a year ago by scop
  3

• Re-review the status codes

  #742 opened a year ago by ePaul
  2

• make all fails on Apple Mac

  #780 opened a year ago by Nkalakatha
  7

• Rule 225: Include exception for Partner-IAM

  #767 opened a year ago by ePaul
  0

• Examples of reliable simple query languages

  #770 opened a year ago by nmoreaud
  3

• Add guideline for common request/response schemas

  #764 opened a year ago by tkrop
  0

• Editorial: Uniform Layout and Naming of Hints, Remarks, Exceptions etc.

  #660 opened 4 years ago by tfrauenstein
  11

• Warn about downstream failures of JSON `\u0000` encoding

  #734 opened 2 years ago by tkrop
  0

• Remove PDF + epub version

  #753 opened 2 years ago by ePaul
  0

• How to get API key activated again

  #754 opened 2 years ago by ButcherFromHell
  1

• some formatting can't be converted to PDF

  #709 opened 2 years ago by ePaul
  5

• Update note about GraphQL

  #747 opened 2 years ago by 130n
  1

• Dead Link on: MUST support pagination [159]

  #745 opened 2 years ago by kolbeck
  1

• Update guidance for time-interval definition

  #641 opened 2 years ago by tfrauenstein
  0

• http 302 is missing in the list of [Success codes, Redirection codes, Client side error codes or Server side error codes]

  #655 opened 3 years ago by lflzrk
  14

• Examples for event names are incorrect

  #648 opened 3 years ago by tkrop
  2

• Identify resources by multiple ids/keys

  #691 opened 3 years ago by bigunyak
  2

• Optimize the Event Guidelines for its usage with Nakadi

  #716 opened 3 years ago by tfrauenstein
  0

• Appendix is not rendered properly

  #703 opened 3 years ago by jvyang
  1

• Error when creating issues in Zally with Github Actions

  #667 opened 3 years ago by vadeg
  3

• Restructuring the Guideline Sections

  #674 opened 3 years ago by tfrauenstein
  2

• Suggestion: Mention kebab-case in rule 129 for consistance

  #688 opened 3 years ago by Retro64
  1

• Open Source Api Portal

  #687 opened 3 years ago by cemo
  1

• Update for OpenAPI 3.1

  #679 opened 3 years ago by scop
  3

• Fix build badge in README

  #669 opened 3 years ago by vadeg
  1

• MUST use standard data formats

  #642 opened 3 years ago by tfrauenstein
  2

• Change proprietary headers format in the hint for Rule 183

  #651 opened 3 years ago by vadeg
  4

• External references to header resources are incorrect

  #638 opened 3 years ago by tkrop
  1

• Consistently use `OpenAPI` (instead of `Open API`)

  #656 opened 4 years ago by tfrauenstein
  0

• Rule 203 (provide means for event ordering) is a must for data change events

  #629 opened 4 years ago by tfrauenstein
  1

• Changelog is out of date

  #640 opened 4 years ago by aaronkorver
  4

• Robustness: clients should not break/crash when the server returns a non problem/json answer

  #624 opened 4 years ago by ePaul
  2

• Remote reference rule is outdated

  #631 opened 4 years ago by tkrop
  0

• Rule 183: Adding email to the range of values of the X-Frontend-Type header

  #634 opened 4 years ago by waleed-madanat
  0