# Build the whole connection. Bring connectivity into your application through one service model. Connect the catalog to an authorized purchase, follow fulfillment and installation, then help customers manage the service they bought. Keep your customer experience in control of the journey. [Create an account for eSIM](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fesim) [Talk to a connectivity specialist](/demo?product=esim-api) [Explore the eSIM platform](/products/esim) An integration you can follow BIRD ยท CONNECTIVITY One service. Connected records. Discover and select Read coverage, terms, price and eligibility. Purchase and fulfill Follow one accepted order to its outcome. Install and use Resolve private setup and observe first use. Keep the existing identity Find the order that represents the intended purchase. Read the recorded outcome Separate financial, network and device state. Resume the right step Continue setup or the supported recovery operation. Illustrative integration flow. Follow the current API contract for supported operations and recovery behavior. ## Model the service your customer is buying. A profile identifies the eSIM, a package describes an allowance and an order records the purchase. A recurring subscription adds billing periods and continuing service. Connect those identities in your application without collapsing their different states. ### Read before you write Discover the offers and effective capabilities for the intended customer. Use published pricing and current eligibility rather than keeping a separate hardcoded catalog in the app. ### Keep the accepted intent Preserve the selected offer and request identity through the purchase. Follow the existing order after an uncertain response, so recovery does not become an accidental second charge. ## Connect purchase to a working device. Track the order through financial acceptance and provisioning, then provide a private installation path. Report the actual outcome at each boundary instead of labeling the customer connected when checkout finishes. ### Keep credentials private Resolve installation credentials through the authorized customer experience. Exclude them from telemetry, public Markdown, issue reports and general support messages. ### React to observed state Use the supported events and reads for the service. Retain observation times, handle missing information explicitly and let your interface resume from the state it actually receives. ## Make recovery part of the implementation. Test a controlled purchase, installation and first use, then an interrupted or refused operation. Use the same service identities to connect support, financial records and lifecycle changes. ### Work with your coding agent Give the agent the current API description and the relevant task guide. Ask it to map supported operations, implement the authorized flow and show evidence for the completed customer outcome. ### Carry acquisition through the journey Keep campaign identifiers with the acquisition and customer handoff. Join them to the recorded business conversion in your application; passing a query parameter is only one part of attribution. ## Build with the right reference - [eSIM API guide](/docs/guides/esim/api): Follow the setup, requirements and operational checks. - [Get started with eSIM](/products/esim/getting-started): Choose an offer and follow a controlled purchase-to-first-use journey. - [Plans and pricing](/products/esim/pricing): Review coverage, allowance, validity and the published terms. ## eSIM API questions ### Is an eSIM API only an installation-code endpoint? No. A useful integration also covers offer discovery, purchasing, fulfillment, service state and ongoing management. Installation credentials are one private part of that lifecycle. ### Can a coding agent build the integration? An agent can work from the current API description, task guides and your application. Have it inspect the supported operations and demonstrate a controlled complete journey; do not assume a method exists from a marketing example. ### How should we handle an uncertain purchase response? Keep the original request and order identity, then use the documented recovery behavior to establish its outcome. Starting a fresh purchase can create another charge or service. ### What belongs in conversion measurement? Record the business outcome you intend to optimize, such as a completed purchase or verified first use. Preserve acquisition context through the relevant handoff and join it to that outcome without including private installation credentials. ## Connect the complete service - [eSIM installation](/products/esim/installation): Help customers install on their device and get connected with clear guidance. - [Usage and top-ups](/products/esim/usage-and-top-ups): Show allowance and expiry, then offer compatible additional data. - [Connectivity operations](/products/esim/operations): Bring orders, billing, network status and support into one service history. - [eSIM resource library](/products/esim/resources): Browse practical guides, explained answers and technical references. ## Start with a complete integration path. Map the supported catalog, purchase and installation operations to your application. Rehearse recovery with the same order before expanding the integration. [Discuss your integration](/demo?product=esim-api) [Read the integration guide](/docs/guides/esim/api) ## Related resources - [eSIM connectivity guide](/docs/guides/esim/overview) (docs) - [What is an eSIM?](/explained/esim/what-is-an-esim) (answer) [Get an implementation brief](/learn/workspace?topic=esim)