Skip to main content

API Versioning Strategy

Xerobi uses a date-based versioning system to ensure predictable API behavior and smooth transitions between versions.

Version Format

Versions follow the format YYYY-MM-DD and are specified in the Xerobi-Version header:

Current Version

Latest Version: 2026-01-01This is the recommended version for all new integrations. It includes the latest features, improvements, and security enhancements.

Version Lifecycle

Version States

Deprecation Timeline

When a new version is released:
  1. Active Period: 12 months of full support
  2. Deprecation Notice: 3 months advance warning
  3. Deprecated Period: 6 months of limited support
  4. Sunset: Version retired

Backward Compatibility

What We Guarantee

  • Existing API endpoints remain functional
  • Request/response formats are stable
  • Breaking changes are introduced in new versions only
  • Deprecation notices provided 3+ months in advance
  • Migration guides provided for major changes

What May Change

  • New optional fields added to responses
  • New endpoints added
  • New optional parameters added to requests
  • Performance improvements
  • Bug fixes that don’t change behavior

Version Headers

Required Headers

Version Detection

If no version header is provided, the API will:
  1. Return a 400 Bad Request error
  2. Include a message specifying the required header

Version-Specific Features

Version 2026-01-01 Features

  • Enhanced webhook security with signature verification
  • Improved error messages with detailed field validation
  • New idempotency key support for all endpoints
  • Expanded payment method support
  • Bulk SMS with individual delivery tracking
  • Enhanced sender ID validation
  • Template management system
  • Improved balance reporting
  • Enhanced credential verification
  • New audit logging capabilities
  • Improved badge management
  • Program-based credential organization

Migration Guide

Upgrading to 2026-01-01

1

Review changelog

Check the changelog for all changes in the new version.
2

Test in sandbox

Update your integration to use the new version in sandbox first:
3

Update production

Once testing is complete, update your production code:
4

Monitor for issues

Watch your application logs and dashboard for any issues after deployment.

Version History

Best Practices

Version Management

  • Always specify the version header explicitly
  • Use the latest version for new integrations
  • Test version upgrades in sandbox first
  • Monitor deprecation notices in your dashboard
  • Keep your integration documentation updated

Code Organization

Support and Migration Help

Authentication

Learn about API keys and headers

Best Practices

Version management best practices

Changelog

See all version changes and updates

Support

Get help with version upgrades