POST conax_web_services/provisioning_requests/add_subscriptions
This method is creating add subscriptions provisioning requests in a pending life cycle state, by specifying the service and the smartcard that should be activated, and the subscription that the service should belong to.
Resource URL
Parameters
Name | Type | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
token | String | The token retrieved from the login method | ||||||||||||
subscription_identifier (mandatory) | Subscription identifier | The subscription that the service to be added belongs to. The available subscription identifier fields are the following:
| ||||||||||||
service_identifier (mandatory) | Product identifier | The service that should be added. Only products classified as services can be specified. The available product identifier fields are the following:
| ||||||||||||
smartcard_identifier (mandatory) | Installed Item identifier | The smartcard that the service should be added on. Only installed items classified as smartcards through the provisioning provider can be specified. The available installed item identifier fields are the following:
| ||||||||||||
process_immediately (optional) | boolean | Defines if the provisioning request will be processed immediately after its creation. If enabled then the provisioning request will be sent through Web API during its creation. If not enabled then the provisioning request will be created and processed later on by the active provisioning request processing run. If not specified then the provisioning request will not be processed immediately | ||||||||||||
start_date (optional) | String | The date that the provisioning request will be appied. If not specified then it is set to the date that the request is submitted | ||||||||||||
priority (optional) | String | The priority of the provisioning request. The supported values are the following:
If not specified then it is set to REGULAR | ||||||||||||
scheduled_date (optional) | Date | The date that the provisioning request is scheduled to be processed. If not specified and process_immediatelly is also set to false, then the provisioning request will be processed immediately. Available from CRM.COM R7.0.0 |
Restrictions
- It is mandatory to specify one of the semi-optional parameters. Only one of those parameters is allowed to be specified.
Response Data
Name | Type | Description |
---|---|---|
id | String | The ID of the retrieved provisioning request |
number | String | The number of the retrieved provisioning request |
type | String | A code that uniquely identifies the type of provisioning request that is performed. The supported options are the following:
|
sequence_number | String | The sequence number of the retrieved provisioning request |
scheduled_date | Date | The date that the provisioning request is scheduled to be send |
executed_date | Date | The date that the provisioning request was actually send |
priority | String | The priority of the provisioning request. The supported values are the following:
|
life_cycle_state | String | The life cycle state of the retrieved provisioning request which can be PENDING, REJECTED or COMPLETED |
request | String | The actual request that was send to Conax |
response | String | The actual response that was received from Conax |
reference_number | String | A reference number provided by Conax after receiving the request |
error_code | String | The error code received by CRM.COM or Conax in case that the provisioning request was rejected |
error_description | String | The error description received by CRM.COM or Conax in case that the provisioning request was rejected |
process_name | String | The name of the process that submitted the provisioning request, which can be one of the following:
|
process_id | String | The ID of the process that submitted the provisioning request |
Log Information Object | The log information related with the retrieved provisioning request | |
parameters_set | Set of Conax Web Services Provisioning Request Item objects | The parameters which will be used to generate the Web Service Calls that will be send to Conax. That information differentiates based on the type of request |
Referred Objects Response Data