Developer API Docs - Next Communications

Developer Portal

Every API shown as a proper technical reference, not a marketing summary.

This page follows a developer-dashboard structure: grouped endpoint navigation, auth rules, request and response tables, sample payloads, and endpoint-specific implementation notes.

Primary authBearer Token

Password handlingAES 256

Token expiry15 Minutes

Major workflows9 APIs

Authentication and API Keys

Credential handling should be obvious before any developer sends the first request.

Protected endpoints rely on an authentication sequence: encrypt the password using AES 256, call token generation, then pass the returned value in the Authorization header as a bearer token.

Base host

partners.nextcommunications.nl:43553

Token lifecycle

15-minute expiry window

Password security

AES 256 encryption required

Plan lookup regions

12, 24, 25

Sandbox API Key

Use this key for testing all endpoints before production go-live.

SBX-NEX********************0001

Step 1Encrypt password

Use the shared key provided separately by Next Communications.

Step 2Generate token

Call the GetToken endpoint using LoginId and encrypted Password.

Step 3Call protected APIs

Use Authorization: Bearer [token] for the remaining methods until expiry.

POST

Token Generation

Generate the bearer token required for all protected API calls.

AuthNo bearer token required. Uses LoginId + AES 256 encrypted Password.

/NextComm_Rchrg/api/default/GetToken

Request Parameters

Everything needed to build the request payload correctly.

Parameter	Required	Type	Description
LoginId	Required	string	Login ID created by Next Communications.
Password	Required	string	Password encrypted using AES 256 before sending.

Implementation Notes

Important behavior and document-specific guidance.

The generated token expires in 15 minutes.
Recommended flow: reuse the token until expiry rather than requesting one before every call.
MessageData contains the actual token value.

Response Fields

Returned objects and important fields developers should parse.

Field	Type	Description
Status	string	Returns Success or Failure.
Message	string	Login status message or failure reason.
MessageData	string	Generated bearer token.

Sample Request

{
  "LoginId": "UATUser01",
  "Password": "h1gnPdpWW6u6OnEjlBghIA=="
}

Sample Success Response

{
  "Status": "Success",
  "Message": "Login Successful !!!",
  "MessageData": "[Token]"
}

Sample Error Response

{
  "Status": "Failure",
  "Message": "Invalid User Credentials !!!",
  "MessageData": ""
}

POST

Activation

Activate a SIM or eSIM and return the subscriber provisioning details.

AuthBearer token required. Request body also includes UserID and AES 256 encrypted Password.

/NextComm_Rchrg/api/default/Activation

Request Parameters

Everything needed to build the request payload correctly.

Parameter	Required	Type	Description
UserID	Required	string	User ID created at Next Communications.
Password	Required	string	AES 256 encrypted password for the user ID.
PlanID	Required	number	Selected plan ID from GetActivationPlans.
FirstName	Required	string	Customer first name.
LastName	Required	string	Customer last name.
AltMobNo	Required	string	Alternate mobile number of the customer.
EmailID	Required	string	Customer email ID.
SIMNo	Optional (eSIM)	string	SIM number. Optional only for eSIM activations.
SimSubType	Required	enum	Pass ESim or Physical.
RequestID	Required	string	Unique integrating-side reference ID.
TxnDateTime	Required	datetime	Country-specific transaction timestamp.

Implementation Notes

Important behavior and document-specific guidance.

All fields are mandatory except SIMNo for eSIM activation.
UserSpecificID is shared by Next Communications after onboarding.
TxnDateTime should be passed in the user or country timezone to avoid default IST stamping.

Supporting lookup endpoints

GET

GetActivationPlans

/NextComm_Rchrg/api/default/GetActivationPlans?LoginEntityID=[UserSpecificID]&RegionID=24

Response Fields

Returned objects and important fields developers should parse.

Field	Type	Description
Status	string	Returns Success or Failure.
Message	string	Activation result or validation failure message.
MessageData	string	Customer-facing activation status.
RequestID	string	Echoes the integrating-side request reference.
TransactionID	number	Activation reference generated by Next Communications.
SIMNo	string	Activated SIM number.
ActivationCode	string	eSIM activation code.
SMDP	string	eSIM SMDP value.
QR	string	eSIM QR in Base64 format.
MobileNo	string	Provisioned mobile number.

Sample Request

{
  "UserID": "cp_in_04",
  "Password": "h1gnPdpWW6u6OnEjlBghIA==",
  "PlanId": 332,
  "FirstName": "test",
  "LastName": "testLastName",
  "AltMobNo": "9987654321",
  "EmailID": "test@gmail.com",
  "SIMNo": "",
  "SimSubType": "ESIM",
  "RequestID": "938758748892347",
  "TxnDateTime": "2024-01-01"
}

Sample Success Response

{
  "Status": "Success",
  "Message": "SIM Activation Recorded Successfully!!!",
  "MessageData": "TXN ID : 2907240000015089, SIM Activation Recorded Successfully!!! New Mobile No : 45623426484",
  "RequestID": "9387587488923400",
  "TransactionID": 2907240000015089,
  "SIMNo": "8955585191222959715",
  "ActivationCode": "jsadgjsghdgshgdhgajs",
  "SMDP": "sdgshdgjsghdja",
  "QR": "shgjdsghfhsysdgyghsd",
  "MobileNo": "45623426484"
}

Sample Error Response

{
  "Status": "Failure",
  "Message": "Validation Error !!!",
  "MessageData": "Request Parameter [PlanID] is Mandatory !!!",
  "RequestID": null,
  "TransactionID": null,
  "SIMNo": null,
  "ActivationCode": null,
  "SMDP": null,
  "QR": null,
  "MobileNo": null
}

POST

Recharge Bundle

Attach a non-chargeable bundle to an already provisioned mobile number.

AuthBearer token required. Request body includes UserID and AES 256 encrypted Password.

/NextComm_Rchrg/api/default/Recharge

Request Parameters

Everything needed to build the request payload correctly.

Parameter	Required	Type	Description
UserID	Required	string	User ID created at Next Communications.
Password	Required	string	AES 256 encrypted password.
MobileNo	Required	string	Mobile number to be recharged.
RechargeAmt	Required	number	Recharge amount.
PlanCode	Required	string	Plan code from GetRechargePlans.
PlanName	Optional	string	Selected plan name from GetRechargePlans.
TxnDateTime	Optional	datetime	Country-specific transaction timestamp.
RequestID	Optional	string	Unique integrating-side request reference.

Implementation Notes

Important behavior and document-specific guidance.

PlanCode should be picked from the GetRechargePlans response.
PlanName is optional and may be passed from plan lookup for readability.
If TxnDateTime is omitted, processing defaults to Indian Standard Time.

Supporting lookup endpoints

GET

GetRechargePlans

/NextComm_Rchrg/api/default/GetRechargePlans?LoginEntityID=[UserSpecificID]&RegionID=24

Response Fields

Returned objects and important fields developers should parse.

Field	Type	Description
Status	string	Returns Success or Failure.
Message	string	Recharge status or failure reason.
MessageData	string	User-facing recharge result.
RequestID	string	Echoed request reference when supplied.
TransactionID	number	Reference generated at Next Communications.

Sample Request

{
  "UserID": "UATUser01",
  "Password": "h1gnPdpWW6u6OnEjlBghIA==",
  "MobileNo": "9137788063",
  "RechargeAmt": 49,
  "PlanCode": "26318",
  "PlanName": "",
  "TxnDateTime": "2021-10-06T04:38:18",
  "RequestID": "Test123456789"
}

Sample Success Response

{
  "Status": "Success",
  "Message": "Recharge has been processed Successfully !!!",
  "MessageData": "Recharge has been processed Successfully !!!",
  "RequestID": "Test123456789",
  "TransactionID": 1611210000019871
}

Sample Error Response

{
  "Status": "Failure",
  "Message": "Get Subscriber Info Service Response : The MSISDN 9137788062 is invalid",
  "MessageData": "Get Subscriber Info Service Response : The MSISDN 9137788062 is invalid",
  "RequestID": "Test123456789",
  "TransactionID": 1611210000019871
}

POST

Get SIM Details for Extension

Fetch the current SIM record before modifying expiry or extension status.

AuthNo bearer token described in the document for this enquiry pattern. Uses Action and MobileNo.

/NextComm_Rchrg/api/default/UpdPlanExp

Request Parameters

Everything needed to build the request payload correctly.

Parameter	Required	Type	Description
Action	Required	string	Pass Enquire.
MobileNo	Required	string	Mobile number to inspect.

Implementation Notes

Important behavior and document-specific guidance.

Use Action = Enquire.
MessageData returns a JSON record as a string.
Returned UsrID and Pass are blank placeholders for follow-up update flow.

Response Fields

Returned objects and important fields developers should parse.

Field	Type	Description
Status	string	Returns Success or Failure.
Message	string	API status message.
MessageData	json-string	Contains Action, MobileNo, LastTxnID, PlanExpiryDt, SimStatus, ServiceName, UsrID, Pass.

Sample Request

{
  "Action": "Enquire",
  "MobileNo": "32165489754"
}

Sample Success Response

{
  "Status": "Success",
  "Message": "UpdatePlanExp Details Fetched/Updated Successfully !!!",
  "MessageData": "{"Action":"Enquire","MobileNo":"32165489754","LastTxnID":"2403230000008772","PlanExpiryDt":"2023-07-31T13:50:00","SimStatus":"Active","ServiceName":"India_USA_100mins_4GB","UsrID":"","Pass":""}"
}

Sample Error Response

{
  "Status": "Failure",
  "Message": "Record Not Available !!! Kindly retry...",
  "MessageData": null
}

POST

Extend SIM Status Update

Update plan expiry date and extend SIM status using Modify action.

AuthUses UsrID and AES 256 encrypted Pass in the request body.

/NextComm_Rchrg/api/default/UpdPlanExp

Request Parameters

Everything needed to build the request payload correctly.

Parameter	Required	Type	Description
Action	Required	string	Pass Modify.
MobileNo	Required	string	Mobile number whose expiry should be changed.
PlanExpiryDt	Required	date	New expiry date for the SIM status update.
UsrID	Required	string	User ID created at NextCom.
Pass	Required	string	AES 256 encrypted password.

Implementation Notes

Important behavior and document-specific guidance.

Use Action = Modify.
PlanExpiryDt is the new target expiry date.
MessageData returns the updated record as a JSON string.

Response Fields

Returned objects and important fields developers should parse.

Field	Type	Description
Status	string	Returns Success or Failure.
Message	string	Update result or failure reason.
MessageData	json-string	Updated Action, MobileNo, LastTxnID, PlanExpiryDt, SimStatus and ServiceName.

Sample Request

{
  "Action": "Modify",
  "MobileNo": "32165489754",
  "PlanExpiryDt": "2023-07-31",
  "UsrID": "UATUser02",
  "Pass": "h1gnPdpWW6u6OnEjlBghIA=="
}

Sample Success Response

{
  "Status": "Success",
  "Message": "UpdatePlanExp Details Fetched/Updated Successfully !!!",
  "MessageData": "{"Action":"Modify","MobileNo":"32165489754","LastTxnID":"2403230000008772","PlanExpiryDt":"2023-07-31T00:00:00","SimStatus":"Active","ServiceName":"India_USA_100mins_4GB","UsrID":"","Pass":""}"
}

Sample Error Response

{
  "Status": "Failure",
  "Message": "Invalid User Credentials !!!",
  "MessageData": null
}

POST

Get Subscriber Info

Retrieve subscriber profile, balances, add-ons, subscription state, and facility details.

AuthBearer token required. Request body includes UserID and AES 256 encrypted Password.

/NextComm_Rchrg/api/default/GetSubscriberInfo

Request Parameters

Everything needed to build the request payload correctly.

Parameter	Required	Type	Description
UserID	Required	string	User ID created at NextCom.
Password	Required	string	AES 256 encrypted password.
MobileNo	Required	string	Mobile number to inspect.
SimNo	Optional	string	Use when mobile number is not available.

Implementation Notes

Important behavior and document-specific guidance.

This is the richest response in the document and returns nested collections.
balances contains balanceName, outstandingAmount, unitType, expirationDate, creationDate, source, and more.
subscriberFacilityDetails returns roaming, voice, SMS, GPRS, ringBack, and other service flags.

Response Fields

Returned objects and important fields developers should parse.

Field	Type	Description
Status	string	Returns Success or Failure.
Message	string	API status message.
MessageData.MobileNo	string	Subscriber mobile number.
MessageData.SimNo	string	Mapped SIM number.
MessageData.SubscriptionID	string	Subscription reference.
MessageData.SubscriberName	string	Subscriber name.
MessageData.ActPlanName	string	Activated plan name.
MessageData.SimStatus	string	Current SIM status.
MessageData.SimExpDate	datetime	SIM expiry as per Next Cellular records.
MessageData.balances	list	Available balances and units.
MessageData.addOns	list	Subscribed add-ons and allowances.
MessageData.subscriptionDetails	object	Subscription state, IMSI, active products.
MessageData.subscriberFacilityDetails	object	Outgoing, incoming, voice, roaming, SMS and data capability flags.

Sample Request

{
  "UserID": "UATUser02",
  "Password": "h1gnPdpWW6u6OnEjlBghIA==",
  "MobileNo": "27827551133"
}

Sample Success Response

{
  "Status": "Success",
  "Message": "Subscriber Details Fetched Successfully !!!",
  "MessageData": "{"MobileNo":"27827551133","SimNo":"8927076191410073003","SubscriptionID":"5ab53c08-812a-ed11-a2e7-005056a676ca","SubscriberName":"NJ","ActPlanName":"5GB Combo","SimStatus":"Active","balances":[...],"addOns":[...],"subscriptionDetails":{...},"subscriberFacilityDetails":{...}}"
}

Sample Error Response

{
  "Status": "Failure",
  "Message": "Invalid User Credentials !!!",
  "MessageData": null
}

POST

Get SIMs for Activation

Fetch available SIM inventory for physical SIM or eSIM activation.

AuthBearer token required. Request body includes UserID and AES 256 encrypted Password.

/NextComm_Rchrg/api/default/GetSIMsForActivation

Request Parameters

Everything needed to build the request payload correctly.

Parameter	Required	Type	Description
UserID	Required	string	User ID created at NextComm.
Password	Required	string	AES 256 encrypted password.
SimSubType	Required	enum	Pass Physical or eSIM.
SimNo	Optional	string	SIM number used for validation when required.

Implementation Notes

Important behavior and document-specific guidance.

SimSubType accepts Physical or eSIM.
MessageData returns a list of SIMs fetched for allocation.
Response may include both Base64 QR and QRCode values.

Response Fields

Returned objects and important fields developers should parse.

Field	Type	Description
Status	string	Returns Success or Failure.
Message	string	API status message.
MessageData	list	Array of fetched SIM records with SimNo, QR and QRCode.
RequestID	string	Usually null in the sample response.
TransactionID	string	Usually null in the sample response.

Sample Request

{
  "UserID": "Dist01",
  "Password": "h1gnPdpWW6u6OnEjlBghIA==",
  "SimSubType": "Physical",
  "SimNo": ""
}

Sample Success Response

{
  "Status": "Success",
  "Message": "Sim(s) Fetch Request Processed Successfully !!!",
  "MessageData": "[{"SimNo":"8927000009543737479","QR":"data:image/jpeg;base64,...","QRCode":"dp-plus-par02-01.oasis-smartsim.com$3PO7N-7894G-WERT-A31H7"}]",
  "RequestID": null,
  "TransactionID": null
}

Sample Error Response

{
  "Status": "Failure",
  "Message": "Invalid User Credentials !!!",
  "MessageData": null
}

POST

Bulk Activation

Submit a list of activation requests for scheduled bulk processing.

AuthBearer token required. Request body includes UserID and AES 256 encrypted Password.

/NextComm_Rchrg/api/default/DoBulkActivation

Request Parameters

Everything needed to build the request payload correctly.

Parameter	Required	Type	Description
UserID	Required	string	User ID created at Next Communications.
Password	Required	string	AES 256 encrypted password.
ActLst[].ProfileId	Required	number	Selected profile ID from GetActivationPlans.
ActLst[].Profile	Required	string	Selected profile name.
ActLst[].ServiceTypeId	Required	number	Selected service type ID.
ActLst[].ServiceType	Required	string	Selected service type name.
ActLst[].ServiceId	Required	number	Selected service or plan ID.
ActLst[].Service	Required	string	Selected service name.
ActLst[].Price	Required	number	Selected plan amount.
ActLst[].SIMType	Required	string	Pass Others.
ActLst[].SIMNo	Required	string	SIM number to activate.
ActLst[].TravelDate	Required	datetime	Travel date in yyyy-MM-dd HH:mm:ss format.
ActLst[].EmailID	Required	string	Customer email ID.
ActLst[].ValidityDays	Required	number	Plan validity days.
ActLst[].OtherBenefits	Required	string	Other benefits from plan response.
ActLst[].AdditionalBenefit	Required	string	Additional benefit details.
ActLst[].ConnectionType	Required	string	Individual, Corporate, Test Cards, Friends, Family.
ActLst[].TxnDateTime	Optional	datetime	Country-specific transaction timestamp.
ActLst[].RequestID	Optional	string	Unique integrating-side request reference.
ActLst[].RefCode	Optional	string	Promotional code if available.

Implementation Notes

Important behavior and document-specific guidance.

ActLst is a list payload. Each object is processed independently.
TravelDate must be formatted as yyyy-MM-dd HH:mm:ss in 24-hour format.
ConnectionType supports Individual, Corporate, Test Cards, Friends, Family.

Supporting lookup endpoints

GET

SA Tourist Plans

/NextComm_Rchrg/api/default/GetActivationPlans?LoginEntityID=[UserSpecificID]&RegionID=12

GET

Voice/Data/SMS Plans

/NextComm_Rchrg/api/default/GetActivationPlans?LoginEntityID=[UserSpecificID]&RegionID=24

GET

Data SIM Plans

/NextComm_Rchrg/api/default/GetActivationPlans?LoginEntityID=[UserSpecificID]&RegionID=25

Response Fields

Returned objects and important fields developers should parse.

Field	Type	Description
[].SimNo	string	Identifies the processed SIM.
[].Status	string	Returns Success or Failure for that SIM.
[].Remarks	string	Per-row result or failure reason.

Sample Request

{
  "UserID": "UATUser02",
  "Password": "h1gnPdpWW6u6OnEjlBghIA==",
  "ActLst": [
    {
      "profileId": 1,
      "profile": "SA Local",
      "serviceTypeId": 4,
      "serviceType": "Activation Plan",
      "serviceId": 1,
      "service": "Nextcomm – Data 1 GB",
      "price": 49,
      "simType": "Others",
      "simNo": "321654987654654321",
      "travelDate": "2021-05-11 15:25:55",
      "emailID": "Test@gmail.com",
      "validityDays": 30,
      "otherBenefits": "...",
      "additionalBenefit": "...",
      "connectionType": "Individual",
      "TxnDateTime": "2021-10-06T04:38:18",
      "RequestID": "Test123456789",
      "RefCode": "Ref321654"
    }
  ]
}

Sample Success Response

[
  {
    "SimNo": "321654987654654321",
    "Status": "Success",
    "Remarks": "TxnID : 20231027321331, SIM Activation Recorded Successfully !!! New Mobile No : 447852145236"
  }
]

Sample Error Response

[
  {
    "SimNo": "321654987654654321",
    "Status": "Failure",
    "Remarks": "Sim Already Active with other User !!!"
  }
]

POST

Upload Documents

Upload visa and passport documentation in bulk using Base64 content.

AuthBearer token required. Request body includes UserID and AES 256 encrypted Password.

/NextComm_Rchrg/api/default/DoDocUpld

Request Parameters

Everything needed to build the request payload correctly.

Parameter	Required	Type	Description
UserID	Required	string	User ID created at NextComm.
Password	Required	string	AES 256 encrypted password.
DocLst[].SimNo	Required	string	SIM number to validate and map documents against.
DocLst[].POI	Required	base64	Visa image or PDF converted to Base64.
DocLst[].POA	Required	base64	Passport front/back in a single Base64 file.

Implementation Notes

Important behavior and document-specific guidance.

POI should contain the Visa image or PDF converted to Base64.
POA should contain Passport front and back in a single file converted to Base64.
The service returns row-level status per SIM.

Response Fields

Returned objects and important fields developers should parse.

Field	Type	Description
[].SimNo	string	Identifies the processed SIM.
[].Status	string	Returns Success or Failure for that SIM.
[].Remarks	string	Per-row upload result or error reason.

Sample Request

{
  "UserID": "UATUser02",
  "Password": "h1gnPdpWW6u6OnEjlBghIA==",
  "DocLst": [
    {
      "SimNo": "321654987654654321",
      "POI": "data-or-base64-string",
      "POA": "data-or-base64-string"
    }
  ]
}

Sample Success Response

[
  {
    "SimNo": "321654987654654321",
    "Status": "Success",
    "Remarks": "Document Upload Processed Successfully !!!"
  }
]

Sample Error Response

[
  {
    "SimNo": "321654987654654321",
    "Status": "Failure",
    "Remarks": "Invalid document payload or validation failed"
  }
]

Changelog

API History

Current baseline is the Live Global Recharge API document dated 29-01-2026.

If request parameters, auth requirements, response payloads, or support endpoint mappings change, update this page at the same time so developers are not forced to reverse-engineer behavior from integration failures.

Date	Version	Endpoints	Change Summary
2026-01-29	v1.4	Activation, Recharge, GetSubscriberInfo	Aligned mandatory request fields and clarified response mapping for integration teams.
2025-11-15	v1.3	GetSIMsForActivation, DoBulkActivation, DoDocUpld	Updated bulk payload guidance and added stronger notes for SIM subtype and document payload handling.
2025-07-04	v1.2	GetToken, UpdPlanExp	Documented token expiry behavior and clarified Enquire vs Modify action usage for extension workflow.