Home
MATRIXX Subscriber Management API
REST API Reference
This part describes how to use the REST API bindings to interface with MATRIXX Engine.
Device REST APIs
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.
Create a Device
Request that a new device is created in the subscriber database and is initialized with the information provided. A unique device OID is created and returned. If supplied, the ExternalId must be unique within the subscriber database. The type of device created depends on the MDC type of the Attr field supplied. A specific type of device must be specified. After it is created, the type of the device cannot be changed.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
- About Subscriber Management API
  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.
- Subscriber Management
  The following information is an overview of the SubMan APIs and architecture.
- Object Management
  The following sections introduce how the various in-memory objects are managed.
- SubMan API Reference
  The SubMan API reference includes SubMan API and MDC descriptions.
- REST API Management
  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.
- REST API Reference
  This part describes how to use the REST API bindings to interface with MATRIXX Engine.
  - Deprecated APIs
    The following APIs are deprecated in this release of MATRIXX and support for these APIs will be removed in a future release.
  - Balance, Meter, and Wallet REST APIs
    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.
  - Catalog REST APIs
    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.
  - Data Migration MDCs
    Use the following MDCs to import data for users, subscriptions, groups, and devices and to import catalog item purchase information for a subscription.
  - Device REST APIs
    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.
    - Check Purchased Item Cycle Alignment
      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.
    - Create a Device
      Request that a new device is created in the subscriber database and is initialized with the information provided. A unique device OID is created and returned. If supplied, the ExternalId must be unique within the subscriber database. The type of device created depends on the MDC type of the Attr field supplied. A specific type of device must be specified. After it is created, the type of the device cannot be changed.
      - POST /device
        Create a device. Reads an MtxRequestDeviceCreate message from post data and submits it to the engine.
    - Delete a Device
      Request that a device is deleted from the subscriber database.
    - Delete a Session
      Delete a device session by specifying the device object ID. Supported request parameters are sessionId and sessionType. Multiple sessionId parameters can be passed.
    - Modify a Device
      Request to modify information in an existing device. If the request XML includes the extended objects field Attr, it must be of the same type used to create the device.
    - Query a Device
      Queries the subscriber database for a device based on External ID, Device ID, Imsi, or Access Number.
    - Validate a Session
      Validate a device session by specifying the device object ID. Supported request parameters are sessionId and sessionType.
  - Eligibility Rules REST APIs
    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.
  - Event REST APIs
    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 REST APIs
    External payment APIs query external payment requests and get a list of external payment request records in a wallet.
  - Gateway REST APIs
  - Group REST APIs
    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.
  - Multi-Tenant REST APIs
    The multi-tenant APIs get tenant information for individual tenants and all tenants.
  - My MATRIXX REST APIs
    My MATRIXX supports GET, PUT, and POST REST bindings. The { } notation around text represents a URL parameter.
  - Offer Life Cycle REST APIs
    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.
  - Pay Now REST APIs
    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.
  - Policy REST APIs
    The policy APIs allow you to query the Sy policy counters for a specific device.
  - Pricing REST APIs
    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.
  - Product Offer REST APIs
    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.
  - Purchase Package REST APIs
    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.
  - Recurring Charge
    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).
  - Rehoming REST APIs
    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.
  - Service APIs
    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.
  - Status Life Cycle REST APIs
    Use these APIs to query status life cycle information for devices, groups, subscriptions, and users from the engine.
  - Status Modify APIs
    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.
  - Subscriber REST APIs
    The Subscriber REST APIs described here are deprecated and will be removed in a future release.
  - Subscription REST APIs
    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.
  - System REST APIs
    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.
  - Tax REST APIs
    The tax APIs manage information in the US Tax database.
  - User REST APIs
    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.
- Java API
  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.
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Create a Device

Request that a new device is created in the subscriber database and is initialized with the information provided. A unique device OID is created and returned. If supplied, the ExternalId must be unique within the subscriber database. The type of device created depends on the MDC type of the Attr field supplied. A specific type of device must be specified. After it is created, the type of the device cannot be changed.

REST Example

In this example, a custom MDC (TrainingDeviceObjectExtension) which extends the MtxMobileDeviceExtension MDC, includes a custom field, TAC_Code.

URL

POST http://host:port/rsgateway/data/v3/device

Request XML

<MtxRequestDeviceCreate>
      <ExternalId>1234567890</ExternalId>
      <DeviceType>0</DeviceType>
      <Attr>
        <TrainingDeviceObjectExtension>
          <TAC_Code>PM123</TAC_Code>
          <Imsi>1234567890</Imsi>
          <AccessNumberArray>
            <value>1234567890</value>
          </AccessNumberArray>
        </TrainingDeviceObjectExtension>
      </Attr>
</MtxRequestDeviceCreate>

Response

<MtxResponseCreate>
    <ObjectId>0-2-5-1</ObjectId>
    <RouteId>1</RouteId>
    <Result>0</Result>
    <ResultText>OK</ResultText>
</MtxResponseCreate>