The following status codes may be returned from the Transactional and Reporting APIs. Successful calls to PRiSMPro ConnectivityPro API service methods will return the "Success" response code. Calls that encounter errors will return the response code in the errorCode field of a PRiSMProAPIFault exception. PRiSMProAPIFault exceptions will also include an errorMessage that gives information on what went wrong.
The following list details all the response codes that can be returned by the PRiSMPro API services.
|0||Success||Successful call to the API.|
|1||AccessDenied||You do not have prism API authorization or no authorization to perform that operation.|
|2||InvalidAction||Action is not allowed.
Example: Required data is not provided.
|4||InvalidDeviceNumber||SIM number is not valid, doesn't exist, is not in your account, or is not in the correct state.|
|5||InvalidMSISDN||MSISDN is not valid, doesn't exist, is not in your account, or is not in the correct state.
Example: Active or stock.
|6||InvalidProfile||The combination of features selected for provisioning is not valid.|
|7||InvalidActionForDevice||The request is invalid for the SIM.
Examples: This could occur if the SIM is already activated earlier on the billing period and the EAP specified now would change its current device plan, which is not allowed.
You try to deactivate a SIM to stock but that service type only allows it to be scrapped.
|8||DeviceProvisioningConflict||There is a conflict that prevents provisioning.
Examples: There is another pending request for the specified device.
This error would occur if there was already an activation request in the queue for the same device.
|11||WebserviceError||There is an error in the web service.
Example: The operation is not yet implemented.
|13||InvalidEAPCode||The EAP code specified is not valid, not in the correct state (deactivated), or is associated with a different service type.|
|21||IneligibleAccount||The account is not eligible for the operation specified.
Example: User is not linked to a company.
|22||IneligibleAction||The user or user's account is not eligible to perform the specified action.|
|23||InvalidIMEIFormat||The IMEI is less or greater than 14-16 characters, or an IMEI was not sent for a KORE VZW activateDevice call.|
|34||RegistrationInProgress||There is already a registration or unregistration in progress for one or more SIMs – each SIM can only be in the queue for registration once.|
|43||ProfileInvalidforDeviceType||Some features selected are for a different device type than the device being provisioned.|
|45||InvalidFeatureCode||A specified feature code is not correct, does not exist or you are not eligible to use it.|
An unanticipated error occurred.
|60||FileNotFound||The file with the specified filename does not exist or does not belong to your company.|
|70||EAPDoesNotExist||The EAP code specified does not exist or is not associated with your account.|
|80||DevicePlanDoesNotExist||The specified device plan code does not exist.|
|90||InvalidParameter||A parameter supplied is not valid (see the errorMessage field for details).|
|101||DeviceCurrentStateMismatch||SIM is not in the correct state.
Example: It should be active to be suspended.
|102||DeviceInvalidTransition||Transition is invalid for the device.
Example: Suspend or restore operations are ineligible for the company.
|103||NoAvailableIP||The activation request cannot be processed because the EAP supplied selects a feature that requires IPs, but there are none available. Contact support to add more to your account.|
|104||PlanWithFeatures||This type of plan change is not allowed.|
|105||BarredDevice||MSISDN changes cannot be submitted for barred devices.|
|110||CostCenterNotFound||No cost center found.|