Checks the status of a license or eSIM activation transaction. Use this endpoint to verify if an activation has completed successfully and retrieve the associated license CLI (Customer Line Identifier) needed for subsequent operations.

Purpose

• Verify activation completion status
• Retrieve the license CLI for activated licenses
• Monitor activation progress for async operations
• Troubleshoot failed activations

Request

• Method: POST
• URL: https://api.bnesim.com/v2.0/enterprise/activation-transaction/get-status
• Content-Type: multipart/form-data
• Authentication: Bearer token required

Parameters

• activationTransaction (Required): The transaction ID from activation response
  • Obtained from License Activation or eSIM Activation endpoints
  • Numeric string format (e.g., "1234567")

Response Fields

• success: Boolean indicating if the status check was successful
• activation_status: Current status of the activation
  • "OK" - Activation completed successfully
  • "PENDING" - Activation in progress
  • "FAILED" - Activation failed
• license_cli: The Customer Line Identifier (CLI) for the activated license
  • This is the unique identifier for the license
  • Required for eSIM assignments and other operations
  • Only present when activation_status is "OK"

Workflow Integration

1. After calling License Activation API, receive activationTransaction
2. Use this endpoint to check status (may need to poll if PENDING)
3. Once status is "OK", save the license_cli
4. Use the license_cli for eSIM activation and management

Example cURL

curl --request POST \
     --url https://api.bnesim.com/v2.0/enterprise/activation-transaction/get-status \
     --header "accept: application/json" \
     --header "authorization: Bearer {{bearerToken}}" \
     --header "content-type: multipart/form-data" \
     --form activationTransaction={{activationTransactionId}}

Important Notes

• The license_cli is critical - it's the primary identifier for all subsequent operations
• Activation is usually instant, but may take a few seconds in some cases
• If status is PENDING, wait a few seconds before checking again
• Failed activations may include error details in additional response fields
• Each activation transaction ID can only be used once