Home
Invoking mRounds Tasks using APIs
Innovapptive exposes certain APIs that can be consued by applications and create tasks like creating operator rounds, dynamically generate round plans, and so on.
Generating API Keys
This section describes the process for generating API keys

Title and Copyright
Copyright and Terms of Use page for Connected Back Office.
Preface
Understand audience, know related documents and products and conventions followed in this document.
Configuring and Integrating External Systems with mRounds
Integrating mRounds with external systems is essential for seamless maintenance operations and data flow across an organization. This chapter provides a comprehensive guide to establishing and configuring connections between mRounds and various external systems, such as FTP servers, ODBC databases, SMTP email servers, and SAP ERP systems.
Invoking mRounds Tasks using APIs
Innovapptive exposes certain APIs that can be consued by applications and create tasks like creating operator rounds, dynamically generate round plans, and so on.
- Generating API Keys
  This section describes the process for generating API keys
  - Pre-requisites
  - Generate API Keys
    Learn how to generate API keys
- Creating Rounds using APIs
  Learn how to create rounds using APIs
- Dynamically Generating and Partially Executing a Round
  A round plan is a blueprint that outlines the structure and steps of a round. You must first create a round plan and then generate a round from the round plan.
- Understanding Error Codes

Generating API Keys

This section describes the process for generating API keys

The API Key is generated during the tenant onboarding process or whenever a customer requests access to the API programmatically. The CBO admin generates the key for the specific tenant or customer upon receiving a request.

Note: API Key access is restricted to the set of API’s identified as being programmatically accessed by a tenant. It cannot be used by any Innovapptive client application (web or mobile). If any application consumes the same API, they should follow the traditional token-based authentication mechanism.