This part describes how to use the REST API bindings to interface with MATRIXX Engine.
The subscription management APIs include the messaging required to operate on the subscriber object, which is a primary object for MATRIXX interactions. The API bindings include the messaging and data elements required to create, modify, and query objects directly related to the subscription. A subscription must have a wallet secondary object, which is created for the subscription at subscription creation time.
Get in-process event aggregations associated with a subscription.
MATRIXX Subscriber Management API provides information about the MATRIXX Engine APIs, including functions, syntax, and result codes, and the MATRIXX Engine REST and Java API implementations.
The following information is an overview of the SubMan APIs and architecture.
The following sections introduce how the various in-memory objects are managed.
The SubMan API reference includes SubMan API and MDC descriptions.
RS Gateway supports the REST API bindings for accessing subscriber data in MATRIXX Engine. RS Gateway consists of an rsgateway application and a set of REST APIs.
The following APIs are deprecated in this release of MATRIXX and support for these APIs will be removed in a future release.
The balance management APIs include the messaging required to operate on a balance, meter, or wallet object. The primitives include the messaging and data elements required to create, modify, associate, and query objects directly related to a balance or meter, including their thresholds.
The catalog APIs return information about pricing catalogs for specified devices, groups, and subscriptions. They return catalog items that the specified object is eligible to purchase.
Use the following MDCs to import data for users, subscriptions, groups, and devices and to import catalog item purchase information for a subscription.
The device management APIs include the methods and functions required to operate on the device primary object. They include the data elements required to create, modify, and query devices, to add and remove a device from a subscription, and to delete a device from the Subscriber database.
This section describes the APIs for querying catalog items based on eligibility. The APIs return catalog items that the specified object is eligible to purchase.
The event APIs include the messaging and elements to return events and notifications in the Event Repository and the event database for subscriptions, groups, and users.
External payment APIs query external payment requests and get a list of external payment request records in a wallet.
The group management APIs include the messaging required to operate on the group object. The APIs include the messaging and data elements required to create, modify, associate, and query objects directly related to the group.
The multi-tenant APIs get tenant information for individual tenants and all tenants.
My MATRIXX supports GET, PUT, and POST REST bindings. The { } notation around text represents a URL parameter.
{ }
Use these APIs to query a list of status life cycles for an offer. You can query specific offer status life cycle using the profile ID.
The integration layer REST APIs manage payment authorization tokens for the payment gateway from the integration layer. These tokens are necessary for the client to communicate directly with the payment gateway to create a payment method in the payment gateway.
The policy APIs allow you to query the Sy policy counters for a specific device.
The pricing management APIs return information about all aspects of pricing, including catalog items, balance templates, product offers, billing cycles, life cycles, notifications and so forth. You can also get status information for the currently-loaded pricing.
The product offer management APIs include the messaging to activate, purchase, cancel, and modify catalog items. You can identify a product offer by its object ID or the external ID assigned during pricing plan creation.
Use the purchase package APIs to manage catalog items in a purchase package, including adding and removing catalog items for subscriptions, groups, and devices, and suspending, resuming, and canceling purchase packages.
The MtxRequestSubscriberEstimateRecurringCharge SubMan API estimates balance impacts from recurring processing of currently failing recurring cycles and upcoming recurring cycles (active purchased items cycles, balance cycles and billing cycles).
The rehoming APIs move a subscription, group, device, or user from one customer sub-domain to a different sub-domain. For a description of the rehoming process, see the discussion about rehoming subscribers, groups, devices, and users in the object management overview.
The extended REST service APIs are implemented only in the RS Gateway. These APIs include REST services that manage subscribers, groups, and devices, including rehoming operations. In addition, you can start and stop rating sessions using the service APIs. Unlike the APIs described in MATRIXX Subscriber Management API, these APIs do not have a Python or Java equivalent. For information about the service API default filters, see the discussion about REST filters.
Use these APIs to query status life cycle information for devices, groups, subscriptions, and users from the engine.
The status modify APIs schedule status changes and delete scheduled status changes. They also suspend and resume purchased items (product offer or bundle) if the current offer status class permits the action.
The Subscriber REST APIs described here are deprecated and will be removed in a future release.
The subscription REST APIs manage subscriptions, including getting subscription authentication data in the database.
This call associates the specified subscription with the specified device. The subscription can be associated with multiple devices, but the device can have only one subscription associated. If the device is already associated with a subscription, an error is returned. When a device is added to a subscription, an MtxSubscriberAddDeviceEvent is generated.
This method is used to retrieve in-process event aggregations associated with a subscriber.
Check a catalog item for cycles that can be aligned to on purchase or modification. One and only one of OfferRequest and OfferResourceId must be provided.
OfferRequest
OfferResourceId
Requests to make a debt payment to a subscription service contract and a subscription's finance contract.
Search for events in the MATRIXX in-memory database and retrieve information on events associated with the subscription.
Request to modify information in an existing subscription. Only those fields with values supplied are modified in the subscription object (MtxSubscriberObject). If the extended objects field, Attr, is supplied, it must be of the same type used to create the subscription.
Attr
The SubscriptionPayment APIs make a payment to a subscriber postpaid balance, add, query, and delete Pay Now payment information for subscriptions.
Use the recharge APIs to request a recharge to a subscription actual currency balance, query the recurring recharge associated with a specified subscription and manage recharge schedules associated with a subscription.
This call removes the association between a specified device and a specified subscription so the device can be added to another subscription. If there are no open sessions on the device and the device status is not inactive, all device-specific offers are deleted (not canceled) and the device is removed from the subscription. When a device is removed from a subscription, an MtxSubscriberRemoveDeviceEvent EDR is generated.
The system REST APIs query the MATRIXX Engine to check if recurring recharge is enabled, return domain and sub-domain information, return tenant IDs, and create Pay Now client tokens.
The tax APIs manage information in the US Tax database.
Use the User REST APIs to add, update, query, and delete users. You can also get and modify user authentication data, associate users with groups and subscriptions, and modify or remove those associations.
This part provides an overview of how to use the Java™ API binding for the SubMan v3 API as an interface to the MATRIXX Engine.
