Skip to content
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.

Issues: WhiteHouse/api-standards

27 Open 4 Closed
27 Open 4 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Email confirmation RESTful api
#56 opened Nov 16, 2018 by hsklia
1
JSONP
#55 opened Oct 1, 2018 by stardust85
Write something about running multiple versions of the API
#52 opened Feb 8, 2017 by syedfaizan
Some questions on the directory structure
#47 opened Mar 31, 2016 by arvalarva
1
Http Code In response Json is useless
#44 opened Nov 18, 2015 by akulubala
3
License for the content
#42 opened Mar 26, 2015 by kyyberi
Add rationale to some guidelines.
#40 opened Dec 11, 2014 by Koded
3
Extending guidelines to include APIs that need authentication and authorization
#39 opened Aug 11, 2014 by stevewilhelm
Thanks and FYI
#38 opened Jul 16, 2014 by gbinal
Consider using the IETF API-Problem specification for error messages
#37 opened Apr 24, 2014 by cpliakas
1
A few CDC Enhancements
#34 opened Oct 29, 2013 by tho1-cdc
Recommend how capitalization is handled
#25 opened May 2, 2013 by philipashlock
Recommend encoding type
#22 opened May 2, 2013 by philipashlock
Clarify file formats and use of Content-Type headers
#21 opened May 2, 2013 by philipashlock
Clarify how JSONP URLs are constructed
#20 opened May 2, 2013 by philipashlock
POST request payload, format, and behavior are not clearly specified
#19 opened May 2, 2013 by philipashlock
POST response format and behavior is not specified
#18 opened May 2, 2013 by philipashlock
Version in Accept Header rather than URL
#17 opened Mar 25, 2013 by joewood
4
CORS?
#14 opened Mar 23, 2013 by inadarei
2
POST is not always "create" and PUT is not always "update".
#13 opened Mar 23, 2013 by inadarei
1
Additional common/important HTTP Response Codes
#12 opened Mar 23, 2013 by inadarei
1
This is not "Truly Restful"
#11 opened Mar 23, 2013 by inadarei
2
Suggestion from Twitter re. HTTP status.
#8 opened Mar 7, 2013 by bryanhirsch
4
Record limits are unclear as to if offset is zero based
#7 opened Mar 5, 2013 by aaronjorbin
Mention this as a nice-to-have
#5 opened Feb 1, 2013 by bryanhirsch
ProTip! Find all open issues with in progress development work with linked:pr.