# Getting Started

## Prerequisites

- **Knowledge Foundation**: Possess a basic understanding of insurance business logic (e.g., underwriting process, claim settlement links, risk assessment concepts) and be familiar with basic terms (e.g., machine learning models, API interfaces, data annotation).

- **Account & Environment**
  - Obtain a valid account for the {offering} platform and development environment access permissions from the project administrator.
s
  - Ensure you have access to the internal Git repository or the project’s shared custom connector library (if required).

- **Development Preparation**

  - Have an API testing tool ready, such as Postman or cURL, for independently testing the third-party APIs or backend services you will integrate.

  - Obtain relevant API credentials and access keys (e.g., Client ID, Secret, API Keys) for authentication configuration in {offering} connectors.


## Important Notes

- Orchestration Operation: A maximum of 20 atomic APIs can be connected in series in the same orchestration process. Exceeding the number will cause process execution timeout; it is forbidden to set rules for circularly calling its own interface in the orchestration logic to avoid causing infinite loops.

- Process Debugging Operation: Do not call production environment interfaces for API orchestration processes in the debugging phase. You need to use enterprise test environment interfaces for verification to prevent affecting production business data.

- Configuration Export Operation: The exported API process configuration file contains sensitive information such as interface keys. Do not store it on public servers or share it with irrelevant personnel.