Skip to main content

API Versioning

The Smartbills API uses versioning to ensure backward compatibility and allow for improvements without breaking existing integrations.

Current Version

The current API version is v1. All API requests should include the version in the URL:

Version Format

API versions are specified in the URL path:
For example:
  • https://api.smartbills.io/v1/receipts
  • https://api.smartbills.io/v1/expenses
  • https://api.smartbills.io/v1/customers

Backward Compatibility

We maintain backward compatibility within a major version. This means:
Safe Changes (Won’t break your integration)
  • Adding new API endpoints
  • Adding new optional request parameters
  • Adding new properties to API responses
  • Adding new webhook event types
  • Adding new error codes
Breaking Changes (Require a new major version)
  • Removing or renaming API endpoints
  • Removing or renaming request parameters
  • Removing or renaming response properties
  • Changing the type of existing fields
  • Changing authentication methods
  • Changing error response formats

Version Lifecycle

Active Support

The current version (v1) receives:
  • New features and enhancements
  • Bug fixes and security updates
  • Full technical support

Deprecation Notice

When a new major version is released:
  1. We provide at least 12 months notice before deprecating the old version
  2. The old version continues to work during the deprecation period
  3. You receive notifications about the upcoming deprecation
  4. Migration guides are provided

End of Life

After the deprecation period:
  • The old version stops receiving updates
  • API requests may return errors
  • You must upgrade to the new version

Checking Your API Version

You can check which version you’re using by looking at your API requests:

Migration Between Versions

When a new version is released, follow these steps to migrate:
  1. Review the Changelog
    • Read the migration guide for the new version
    • Understand what has changed
  2. Test in Pre-Production
    • Update your code to use the new version
    • Test thoroughly in the pre-production environment
  3. Update Your Code
    • Make necessary changes to handle new response formats
    • Update error handling if needed
  4. Deploy to Production
    • Deploy your updated code
    • Monitor for any issues

Best Practices

Always include the version number in your API requests. Don’t rely on default versions.
Your code should ignore unknown fields in API responses to handle new properties added in the future.
Subscribe to our developer newsletter to receive notifications about:
  • New API versions
  • Deprecation notices
  • New features and improvements
Version your own integration code to make it easier to track which API version you’re using.

Version History

v1 (Current)

Released: January 2024 Status: Active Features:
  • Complete REST API for receipts, expenses, and customers
  • OAuth2 authentication
  • Webhook support
  • Comprehensive error handling
  • Multi-language support

Getting Help

If you have questions about API versioning or need help migrating to a new version: