Versioning and changelog

The API version is in the path. Changes that keep your code working ship within v1. Changes that could break it get a new version.

Versioning

All requests go to https://api.liveleg.dev/v1. Within v1 we make these changes at any time:

• New endpoints and resources
• New optional parameters
• New fields in responses and event data
• New event types
• New values in fields that list options, such as a new amd result or a new blocked rule
• New error codes

Your code should ignore fields and event types it does not know, and handle a value it has not seen before.

These changes need a new version:

• Removing or renaming an endpoint, a parameter or a field
• Changing the type or format of a field
• Making an optional parameter required
• Changing what an existing request does by default

When a new version ships, the old one keeps working for at least 12 months. We email every account before the old version is turned off. You move to the new version one request at a time by changing the path.

Changelog

New endpoints, fields and events in v1, newest first.