Skip to main content

Main Concepts

In the CELITECH ecosystem, partners and developers will primarily interact with four key entities. Each of these entities represents a core aspect of the services provided by CELITECH, and understanding them is crucial to leverage the full capabilities of the system.

Destinations​

Destinations refer to the locations currently supported by CELITECH. These could be countries or regions where the eSIM service is available. Partners may need to select or reference destinations when purchasing data packages or managing eSIMs.

Packages​

Packages denote the different data packages available from CELITECH. Examples might include various data allowances such as "United States 1GB" or "Europe 5GB." The packages define what data services the user will have access to and may vary in terms of cost, data volume, and valid destinations.

Purchases​

The Purchases entity encompasses a range of functions related to buying and managing eSIMs. The purchase endpoints allow for:

  • Buying an eSIM: Acquiring a new eSIM package.
  • Topping-up an Existing eSIM: Topping-up an existing eSIM with a new package.
  • Listing Existing Purchases: Retrieving information about previous eSIM purchases.
  • Updating Activation Period: Modifying the activation period for future purchases.
  • Checking Consumption and Status: Viewing the usage and connectivity status of a purchased eSIM, among other related functionalities.

eSIM​

The eSIM endpoints provide comprehensive details about eSIMs owned by the partner. This information can include:

  • Device Information: Specifications of the device using the eSIM.
  • eSIM History: Historical data regarding the status of the eSIM.
  • Status: Information about the current state of the eSIM.
  • Activation Code: Codes or methods to activate the eSIM on a device, and more.

Understanding these main concepts and how to interact with them via CELITECH's APIs is vital for successful integration and utilization of the services. For further details and specific instructions, please refer to the full API documentation.