Update Subscriber

The CRM / Ordering system updates a Subscriber in the OCS.io via the RESTful API. The request body contains updated Subscriber details like External ID, Custom Name, etc. The OCS.io updates the instance of the Subscriber, then returns Business Transaction containing updated Subscriber as a payload of the response. Other systems may be notified about the Business Transaction via the Streaming Platform.

Update Subscriber’s External ID

The Update Subscriber’s External ID use-case allows the CRM or ordering system to update the external ID of a subscriber. This operation is not versioned, meaning the new external ID takes effect immediately and the old external ID can no longer be used.

Update Subscriber’s Custom Name

The Update Subscriber’s Custom Name use-case allows the CRM or ordering system to update the custom name of a subscriber. This attribute is not versioned, and the new value takes effect immediately.

Update Subscriber’s Custom Attributes

The Update Subscriber’s Custom Attributes use-case allows the CRM or ordering system to update the custom attributes of a subscriber. Custom attributes are implemented as key-value pairs, and the system must provide the full set of key-value pairs in the request.

Update Subscriber’s Segment

The Update Subscriber’s Segment use-case allows the CRM or ordering system to update the segment of a subscriber. While a history is maintained for this attribute, the new value takes effect immediately and is used in subsequent processes.