Subscribe API

Product Information contained within this document, including technical information and functional specifications, is subject to change without notice. Naviga reserves the right to make any changes to the information in this document at any time without notice. Naviga makes no warranty, representation, or guarantee regarding the suitability of its products and services for any particular purpose.

If you are upgrading to Subscribe Version 3.17.0 and calling the subscribe APIs externally, this migration is mandatory.

Introduction

Welcome to the Subscribe API documentation! This guide is intended to assist developers, system administrators, and API integration stakeholders to understand, mitigate, and effectively adapt to the breaking changes in application programming interfaces (APIs). Breaking changes are modifications that can interrupt the normal functioning of dependent systems, causing compatibility issues.

This guide explains how to migrate from the older to the newer APIs that have been listed below.

1. Migration from old Billing API endpoints to the new Payment API

2. Migration from old UserAPI endpoints to the new UsersOrchestrator API

3. Migration from Entitlements endpoints to the new EntitlementsOrchestrator API