OvationCXM Product Updates logo
Back to Homepage

Product Updates

Subscribe to Updates

Labels

  • All Posts
  • CX Manager
  • Knowledge
  • Bots
  • Journeys
  • Messenger
  • Mobile SDK
  • Dashboards & Reporting
  • Integrations & APIs
  • Settings & Admin

Jump to Month

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
Integrations & APIs
2 years ago

OvationCXM API V3 for Service Provider Organizations

We are excited to announce the latest update to our V3 API suite. This update will allow the service providers orgs to utilize a subset of API endpoints on behalf of one or many standard organizations in their ecosystem. This feature enhances the flexibility and functionality of OvationCXM, enabling service providers to interact with customer data efficiently. Please read below for more details on this update.

The OvationCXM API has been enhanced to provide a subset of endpoints for service provider organizations. While the API was initially designed for standard organizations to interact with their data, this new functionality allows service providers to perform certain actions on behalf of a standard organization.

To take advantage of this use case, the following conditions must be met:

  1. The standard organization, on whose behalf the service provider is acting, must be the rightful owner of the customer data being accessed.
  2. An ecosystem relationship between the service provider organization and the standard organization must be defined within CXMEngine.

New HTTP Header: X-Boomtown-OBO

To utilize the subset API endpoints, service provider organizations are required to include an additional HTTP header in their API calls. The header, X-Boomtown-OBO, should contain the unique ID of the standard organization on whose behalf the API calls are being made. This ensures proper authorization and linkage between the service provider and the associated standard organization.

Please note that the availability of specific endpoints and their functionalities may vary based on the subset API access granted to service provider organizations.

We believe that this feature enhancement will greatly benefit service providers by enabling them to offer more comprehensive and efficient services to their customers. It strengthens the collaboration between service providers and standard organizations, fostering a seamless customer experience.

For more information on how to implement and utilize the subset API access for service providers, please refer to the updated API documentation and guidelines provided by OvationCXM.

If you have any questions or require further assistance, please don't hesitate to reach out to our support team.

Best regards,

The OvationCXM Team


Avatar of authorPrayas Tiwari