RESTful API DesignJuly 3rd, 2020
I have implemented many APIs integrations. The story usually goes: some CURL CRUD under the hood and wrapped in a library that has various degrees of being documented well.
In 2017, I outlined what is good/bad about API Implementations on my API Integration skill page.
Writing an API for third parties to connect to, should have all the right
API Endpoint Design
- Customer Facing Endpoint conventions, no spelling mistakes (second set of eyes with good literary skills is useful here)
- Clear intuitive endpoints, following any well established Tesla best practices that work well on other projects
- Return JSON
Software Developer always striving to be better. Learn from others' mistakes, learn by doing, fail fast, maximize productivity, and really think hard about good defaults. Computer developers have the power to add an entire infinite dimension with a single Int (or maybe BigInt). The least we can do with that power is be creative.
- Top Safety
- Lower Fuel Costs
- Mobile Service
- Full Self Driving Beta
- Climate Controls
- Sentry Mode
- Dog Mode
- Great Handling
- Great looking cars
- Video Games
- Super Charger Network