Compatibility

API Versioning

ALEFBA uses versioned API paths to protect integration compatibility.

Current version

https://alefba.eu/api/v1

Backward-incompatible changes should be introduced under a new major version path.
Additive fields may be introduced without changing the major version.
Clients should ignore response fields they do not recognize.
Deprecated behavior should be announced before removal whenever operationally possible.
Security fixes may be applied without waiting for a new major version.

GET/api/v1/catalog

GET/api/v1/products

Recommendation: Store the base URL in application configuration rather than repeating it throughout your codebase.