1. 8
  1.  

  2. 3

    This is something we’ve considered at Twilio and might yet still implement. As you suggest the OPTIONS method could have a lot of potential as a foundation of self-documenting HTTP APIs. The other way (and arguably the right way) is to use a real hypermedia type that is capable of self-description for your resource representations. Something like atom or even just html is much more expressive than json.