18F/api-standards

Issues

• This repo should be converted to 18F Pages

  #54 opened 3 years ago by arowla
  9

• Singluar vs. Plural Nouns

  #65 opened 3 years ago by acurley
  1

• Stacktraces in production

  #46 opened 3 years ago by ajb
  1

• New APIs should require SNI of their users

  #50 opened 3 years ago by konklone
  0

• Data envelopes and format of `results` attribute

  #53 opened 3 years ago by arowla
  3

• What data should go in headers, and what data in the response body

  #45 opened 3 years ago by adelevie
  14

• "Don't use unpredictable keys" (in response JSON)

  #31 opened 3 years ago by arowla
  1

• Possibly include link header in pagination section?

  #37 opened 3 years ago by ajb
  3

• avoid using "entropy"

  #41 opened 3 years ago by sbma44
  0

• expand acceptable input param vehicles to include full URIs

  #43 opened 3 years ago by sbma44
  0

• api key - standards

  #24 opened 3 years ago by gbinal
  3

• Heroku's API standards

  #26 opened 3 years ago by adelevie
  1

• Hypermedia APIs

  #28 opened 3 years ago by konklone
  4

• Standard length of time provided for deprecation, changes?

  #30 opened 3 years ago by kaitlin
  1

• Standards for API documentation

  #19 opened 3 years ago by konklone
  8

• how to handle recc. a terms of service or expectations offered

  #21 opened 3 years ago by gbinal
  1

• encourage use of api.data.gov

  #23 opened 3 years ago by aaronsnow
  2

• Get more feedback

  #4 opened 3 years ago by gbinal
  0

• Removing version numbers

  #5 opened 3 years ago by konklone
  29

• Further sections to add?

  #1 opened 3 years ago by gbinal
  0

• FBOpen links returning a 404

  #72 opened 8 years ago by Ryandaydev
  1

• Justify use of charset parameter in JSON payloads

  #68 opened 9 years ago by toolness
  2

• under_score for JSON keys?

  #40 opened 9 years ago by edsu
  6

• Shouldn't this repo have a LICENSE?

  #55 opened 9 years ago by arowla
  2

• Request to change description to make it clearer for users

  #51 opened 9 years ago by melodykramer
  4

• Specify date format standard

  #38 opened 10 years ago by marks
  5

• for discussion: HTTPS everywhere

  #42 opened 10 years ago by sbma44
  1

• Remove recommendation to use a file extension to indicate format

  #6 opened 10 years ago by konklone
  3

• Removing support for multiple formats

  #7 opened 10 years ago by konklone
  1

• JSON as a default

  #8 opened 10 years ago by konklone
  0

• Generalize the URL recommendations

  #9 opened 10 years ago by konklone
  0

• Generalize the verb descriptions

  #10 opened 10 years ago by konklone
  0

• With JSON, always return an object

  #11 opened 10 years ago by konklone
  0

• Slightly generalize pagination

  #12 opened 10 years ago by konklone
  0

• Mention case standards for formats

  #14 opened 10 years ago by konklone
  0

• Use UTF-8 encoding in mime type

  #15 opened 10 years ago by konklone
  0

• Discuss the use cases you should consider

  #16 opened 10 years ago by konklone
  0

• Be a user of your own API

  #17 opened 10 years ago by konklone
  3

• Mock responses section needs more info

  #18 opened 10 years ago by adelevie
  2

• Document point-of-contact

  #20 opened 10 years ago by adelevie
  0

• Ensure a notification system

  #25 opened 10 years ago by gbinal
  0

• Replace JSONP with CORS

  #13 opened 10 years ago by konklone
  3

• include ssl by default

  #22 opened 10 years ago by gbinal
  0

• Coordinate with 18F team owners

  #29 opened 11 years ago by gbinal
  1

• Review WH API Standards issues

  #3 opened 11 years ago by gbinal
  0