Keep your customer relationship.
Your app handles customer sign-in, checkout and any payment you collect from the customer. Your organization wallet funds the Bird purchase. Link those payment and order records so support can resolve either side.
Travel data. Inside your app.
Add mobile data to the customer journey you already own. Use the Bird API to show offers, purchase packages and send private installation links. Customers return to your app to check their packages, buy compatible top-ups and reach support.
A trip in your app.
A service they can return to.
Retain the same customer, order and profile after the original checkout session ends.
Customer account
Alex’s Lisbon trip
Your app connects the traveler’s account to the selected offer.
- Customer
- Alex Morgan
- Itinerary
- Spain + Portugal
- Offer
- Accepted coverage and terms
Record the purchase
Retain the existing order reference.
Deliver private setup
Send a hosted installation link by email or SMS.
Keep the return route
Let the customer reopen the service from their account.
Account · Connectivity
Resume the existing plan
Order 1048 and profile 042 remain attached to Alex’s trip and support path.
Same service after returnWhat does my app need to build?
Use the public eSIM API from your server. Your app authenticates customers and handles customer checkout and payment collection. Bird handles package orders and hosted installation links. Your organization wallet pays for Bird purchases.
Your checkout and account.
Bird’s connectivity and setup.
Connect your customer experience to eSIM purchases without building an installation page.
Send a ready-to-use installation page.
Create a hosted installation link or send it by email or SMS after the order completes. The recipient can open device-specific instructions without a Bird workspace login. Track delivery, see when the link expires and revoke it if needed.
Give customers a place to return.
Keep each customer’s order, eSIM and packages in their account. Show reported usage with its update time, offer compatible top-ups and resume an interrupted purchase from its existing order.
Embedded connectivity questions
Can we use our own checkout and app?
Yes. Your server uses the eSIM API while your app handles customer authentication, checkout and any payment you collect. The Bird purchase is funded by your organization wallet. Track customer payments separately from Bird wallet charges, and link both to the same customer order.
Do we need to build an eSIM installation page?
Bird provides hosted installation links with device-specific instructions. Create a link for your own delivery flow or send it by email or SMS. Recipients can open it without a workspace login. Anyone with the link can access the installation details until it expires or is revoked.
Who handles customer identification requirements?
Bird publishes the selected offer’s identification requirements. Your own authorized process collects and validates the required information; Bird does not collect, verify or store those answers. Assigning a contact to an eSIM does not perform an identification check.
Can customers add data after their first purchase?
Yes, when compatible top-ups are available for their eSIM. Show the eligible offers and accepted terms in their account, then track the delivery status of their new package order. The top-up uses the installed profile, so the customer does not need to install another eSIM.
Scale without
losing control.
Organize teams in workspaces, control API access, and trace changes through audit logs.
HarborOrganizationWorkspacesProductionSandbox
Delivery agent
API key · Customer operations teamALAlex Lee AdminPermissions updated
Audit log
Production- Workspace
- Production
- Resource
- Delivery agent
- Read accessRead & write
Team Customer operationsActor role AdminOutcome SucceededTime 22 Sep, 09:42:18 UTC
Succeeded