coopr

QuitCarbon is a free, San Francisco-local service that helps homeowners replace gas appliances with clean electric alternatives like heat pumps and induction stoves.

We are looking to add the first software person to our team of quitters. Maybe it'll be you, or someone you know?

Learn more at https://quitcarbon.notion.site/QuitCarbon-Job-Board-e662ca71de0d4061ae9b61232cfcf730

Are there any existing APIs you like that I could use for inspiration?

Are there any you hate that you hope I avoid emulating?!

(I'm not interested in the technical implementation - I'm more interested in the UI, the documentation, etc)

By "fine grained permissions for API keys", I mean that a user could create an API key with a certain set of permissions (eg CREATE resource type X, READ (but not modify) resource type Y, prohibit access to endpoints A and B, etc), then create another key with other permissions, etc. Admins would need to see what keys were created by whom, what permissions those keys have, usage on a per-key basis, do key regeneration, etc.