Write more complete API documentation

[ErikBoesen]

I think it would be really cool to have a Swagger docs system like this, where you can test the API in-browser and see what the responses are like. At minimum we should document the filters endpoint and add a list of fields Person has.

[Redorhcs]

Hey Erik - was looking into this (and I think I've mentioned about wanting to pick this up) and had a few ideas at least for a v0 if we can't do something like swagger itself:

• The current pageview has a lot of whitespace on non-mobile clients (where someone is likely to get api info from)

- It might make more sense to give examples beyond what we have already, something like "People" and give an example in JSON / js-yalies / python-yalies, and then dive further into the filters endpoint and fields that get returned

• (continuing from ^ documenting how you can do multiple NetIDs at once would've been awesome to know!)

• For groups, is yaleorgs.com still the endpoint or should we cut that over to yalies.io/api/groups ?

[ErikBoesen]

Agree with all of this. yaleorgs.com is deprecated, we need to fix the endpoint referenced in the docs, that's my mistake

[Redorhcs]

That’s ok! I’ll get started on this and propose a branch by Sunday night.