User Interfaces Release 9.1 Subscriber Provisioning Reference Manual 400 — if a key is detected to be already in the system for another subscriber or if the representation field list does not contain at least one unique key or if the field name does not exist. MSR4002 should be sent in the case where an unknown subscriber field is specified. 404 — could not find the subscriber by key Example PUT {baseURI}/msr/sub/MSISDN/+33123654862 10404723525 184569547984229 22 DayPassPlus Delete Profile operation Description This operation deletes all profile data (field-value pairs) and opaque data for the subscriber that is identified by the key name and key value.
HTTP(S) operation DELETE {baseURI}/msr/sub/{keyName}/{keyValue} HTTP(S) request content None HTTP(S) response content None Response status codes 204 — successfully deleted - no content body is sent in the response 404 — if subscriber does not exist - no content body is sent in the response Example DELETE {baseURI}/msr/sub/MSISDN/+33123654862 Fetch Field operation Description This operation retrieves the values for the specified field for the subscriber identified by the specified key name and key value. Note that depending upon the field entered, there may be multiple field-value pairs returned by this operation. 51 910-6701-001 Revision A, June 2013