Go to Production
Before moving to Production, make sure your integration is operationally ready for real customer traffic.
Production integrations must be able to handle asynchronous provisioning, lifecycle updates, retries, failures, and webhook-driven state changes reliably.
Production Readiness Checklist
Before requesting Production access, validate the following areas.
API Integration
- Authentication is implemented correctly
- API versioning is handled explicitly
Correlation-Idis sent on all requestsIdempotency-Keyis used on supported write operations- Retry handling is implemented safely, respecting rate limits
Webhooks
Webhooks are required for production integrations. See the Webhooks reference for the full setup, signature verification, and retry behaviour.
Your integration should:
- Expose a public HTTPS webhook endpoint
- Handle asynchronous lifecycle events
- Process duplicate webhook deliveries safely
- Acknowledge webhook requests quickly
- Persist webhook payloads for troubleshooting
Critical events include:
Order lifecycle — reflect order outcome in your system
order.completed
order.failed
order.canceled
order.on_holdSIM/eSIM provisioning — drive the end-user activation flow
subscription.sim_profile.ready_for_installation
subscription.sim_profile.installed
subscription.sim_profile.deletedSubscription lifecycle — keep your view of the customer's service state in sync
subscription.active
subscription.grace
subscription.deactivated
subscription.canceledBalance & product state — surface usage limits and service disruptions to end users
balance.threshold.exceeded
product.depleted
product.throttling.applied
product.throttling.lifted
product.terminatedBilling — if your integration performs financial reconciliation
invoice.open
invoice.paid
credit_note.issuedPorting — if your integration offers number portability, treat the full set of porting events as critical. Each state transition reflects a decision point from the donor operator or the customer that your integration must track.
porting.draft
porting.pending
porting.agreed
porting.scheduled
porting.processing
porting.completed
porting.rejected
porting.cancelation_requested
porting.canceled
porting.reschedule_requestedLifecycle & Provisioning Handling
Production systems must correctly handle asynchronous provisioning flows.
Your integration should:
- Treat Orders as asynchronous operations
- Wait for webhook confirmation before updating customer state
- Handle delayed provisioning scenarios gracefully
- Support retry and recovery workflows
- Surface provisioning failures to support teams and end users
Connectivity & Customer Experience Validation
Before launch, validate:
- eSIM installation flows
- QR and LPA delivery
- Connectivity activation
- Mobile data usage
- Device compatibility
- Error handling and recovery scenarios
Partners should test the complete end-user experience from purchase to connectivity activation.
Observability & Support
Production integrations should include operational monitoring and support processes.
Recommended practices:
- Log all request and webhook correlation identifiers
- Store lifecycle resource IDs
- Monitor webhook failures and retries
- Monitor provisioning failures
- Maintain customer support escalation procedures
Production Access
Production access is configured by 1GLOBAL after onboarding and validation are completed.
Once approved, you will receive:
- Production API credentials
- Production environment configuration
- Production Product Offering access
- Production webhook configuration
Recommended Final Validation
Before going live, complete a final end-to-end validation:
- Create an Order
- Receive provisioning webhooks
- Install the eSIM
- Validate connectivity
- Validate lifecycle tracking
- Validate support and recovery flows