Added API

[begedin]

• basic ping endpoint, with unauthenticated and authenticated response
• doorkeeper + clearance for authentication
• basic get /users/:id endpoint, AMS enabled

[christopherstyles]

This is looking great @begedin, nice work! Have we given any thought to API versioning yet?

[joshsmith]

@christopherstyles we actually started talking about API versioning the other day. With Field the Bern, we made no assumptions and just decided to tread kind of recklessly with regards to versioning.

I'd been reading a lot about how Stripe does their versioning using gates and request/response layers with date headers instead of hardcoded URL versions.

We may not (at first) have many consumers beyond our own few clients. So we should balance decisions here with an eye towards understanding resource constraints and longevity. We may have more than three clients at some point. And we may have more than us consuming the API. We also don't have a ton of time to devote to a complex scheme, though understand similarly that we want to be able to iterate in fast feedback cycles, so a date-based approach can make more sense.

Do you have any thoughts here? We should maybe open a separate issue with my comments pasted in.

[christopherstyles]

:+1:

[joshsmith]

@begedin missing a reviewed label but :+1: