Versioning

Payless Power employs URL path versioning with distinct endpoints for each major API version (e.g., /v1/, /v2/). Breaking changes trigger new major versions while maintaining previous versions for backwards compatibility.

Version types:

• Major releases: Include breaking changes requiring code updates

• Revision releases: Contain only backwards-compatible changes

Before deprecating any major version, PLP provides:

• Advance notification

• Clear deprecation timeline

• Migration documentation

Best practice: Test new API versions in a QA environment before upgrading production systems. Full version details are available in our API changelog.

Example endpoints:

https://api.paylesspower.com/v1/customers
https://api.paylesspower.com/v2/customers