How Leafy Energy handles API versions (demo)
In the demo we use API versions to show how changes can be introduced without breaking existing integrations immediately.
Version in the path
- The version is part of the URL, such as
/v1/or/v2/. - Breaking changes are only introduced in new major versions.
Example
GET /v1/pricing/day-ahead
GET /v2/pricing/day-aheadIn v2 an additional field might be added, such as hourly CO2 intensity.
Migration strategy
- Use client-side feature toggles to migrate gradually.
- Monitor error codes and performance per version.
In the demo, you can show a dashboard calling two versions side by side and highlighting the differences.
Comments
0 comments
Please sign in to leave a comment.