Skip to main content
This page explains how the Defendis API evolves over time: versioning guarantees, compatibility expectations, and the practices you should follow to keep production integrations stable.

​
Versioning policy

Defendis uses path-based versioning. Current customer API is /api/v1

​
Backward-compatible changes

We may introduce backward-compatible improvements without changing the version, including:

Endpoints

Adding new endpoints.

Parameters

Adding new optional query parameters.

Fields

Adding new fields to existing responses.
For forward compatibility, ignore unknown response fields and avoid strict JSON parsing that fails on additional properties.

​
Breaking changes

Breaking changes will be introduced under a new version prefix /api/v2.