Home
MATRIXX Subscriber Management API
SubMan API Reference
The SubMan API reference includes SubMan API and MDC descriptions.
Rehoming MDCs
The rehoming APIs move a _glossary/subscription.html, group, or device from one customer sub-domain to a different sub-domain. For a description of the rehoming process, see the discussion about rehoming subscribers, groups, and devices in the object management overview.

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.
  - Application MDCs
    The application MDCs include information for each Rx application session in a response for device sessions.
  - Balance, Meter, Wallet MDCs
    This section includes balance-related MDCs.
  - Barclay MDCs
    This section describes the Barclay MDCs.
  - Bundle MDCs
    This section includes the bundle MDCs.
  - Billing MDCs
    This section includes billing-related MDCs.
  - Braintree MDCs
    This section includes the Braintree-specific SubMan APIs.
  - Catalog MDCs
    The catalog APIs return information about pricing catalogs for specified devices, groups, and subscriptions.
  - Catalog Item MDCs
    The catalog item APIs return information about eligible catalog items for specified devices, groups, and subscriptions.
  - Charge-Related MDCs
    This section describes the charge-related MDCs for MATRIXX API calls.
  - Contract MDCs
    Contract data is returned in the product offer API responses in the MtxPurchasedOfferInfo MDC.
  - Datatrans MDCs
    The Datatrans MDCs include information for the Datatrans Payment Gateway.
  - 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 MDCs
    This section lists the device-related MDCs.
  - Diameter MDCs
    This section includes the Diameter-related APIs.
  - Eligibility Rules MDCs
    This section describes the SubMan eligibility rules APIs.
  - Event MDCs
    This section includes the event-related APIs.
  - Evertec MDCs
    This section includes the Evertec-specific SubMan APIs.
  - External Payment MDCs
    External payment APIs query external payment requests and get a list of external payment request records in a wallet.
  - Group MDCs
    This section lists the group-related APIs.
  - Mastercard MDCs
    This section includes the Mastercard-specific SubMan APIs.
  - mPAY MDCs
    This section describes the mPAY MDCs.
  - Multi-Tenant MDCs
    The multi-tenant APIs return tenant information for individual tenants and all tenants.
  - Notification MDCs
    This section includes the notification MDCs.
  - Parameter MDCs
    This section includes the parameter MDCs.
  - Pay Now Payment MDCs
    The Pay Now payment SubMan APIs query payment information and add or remove payment method tokens for subscribers and groups.
  - Policy MDCs
    This section lists the MATRIXX Policy application APIs.
  - Pricing MDCs
    This section describes the pricing-related APIs.
  - Product Offer MDCs
    This section describes the product offer-related APIs.
  - Purchase Package MDCs
    Use the purchase package MDCs 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.
  - Purchased Item MDCs
    This section lists the purchased item APIs.
  - Recharge MDCs
    This section describes the recharge MDC fields.
  - Rehoming MDCs
    The rehoming APIs move a _glossary/subscription.html, group, or device from one customer sub-domain to a different sub-domain. For a description of the rehoming process, see the discussion about rehoming subscribers, groups, and devices in the object management overview.
    - MtxRequestDatabaseRehome
      Request to rehome an object from another system into the current one.
    - MtxRequestDatabaseRehomeCommit
      Request to confirm the successful rehoming of an object on the original system.
    - MtxRequestDatabaseRehomeRollback
      Request to rollback the failed rehoming of an object on the original system.
    - MtxRequestDeviceRehomePrepare
      Request to prepare a rehoming of the specified device from the current system.
    - MtxRequestGroupRehomePrepare
      Request to prepare a rehoming of the specified group from the current system.
    - MtxRequestSubscriberRehomePrepare
      Request to prepare a rehoming of the specified subscriber from the current system.
    - MtxRequestUserRehomePrepare
      Request to prepare a rehoming of the specified user from the current system.
    - MtxResponseRehome
      Response to preparing a rehoming which returns the relevant object headers and data.
    - MtxRehomeBalanceSetData
      Data for BalanceSets being rehomed.
    - MtxRehomeContext
      Metadata about objects being rehomed.
    - MtxRehomeData
      Data for objects being rehomed.
    - MtxRehomeObjectData
      Data for descendants of MtxObject being rehomed.
    - MtxRehomePrepareInfo
      Information in response to rehome prepare operations that is copied to the input of the rehome operation.
  - Related Objects
    This section describes the common structures for related objects, related subscription objects, and related user objects.
  - Request/Response MDCs
    This section includes request and response APIs.
  - Roaming MDCs
    This section describes the roaming MDCs.
  - Romcard V2 MDCs
    This section describes the Romcard V2 MDCs.
  - Security MDCs
    The ApiEventSecurityInfo MDC records client security information.
  - Status MDCs
    The status APIs change the status of existing subscriptions, groups, and devices. They cancel any scheduled status change for a purchased item (offer or bundle) from subscriptions, groups, and devices. They cancel any scheduled status change for subscriptions, groups, and devices.
  - Subscriber MDCs
    This section lists the subscriber-related APIs.
  - Subscription MDCs
    The subscription APIs create, delete, modify, and query subscription objects.
  - Subscription/Group Membership MDCs
    This section describes the subscription/group membership MDC.
  - Tax MDCs
    This section lists the tax APIs.
  - Tenant MDCs
    This section lists the tenant APIs.
  - User MDCs
    This section describes the user object APIs.
  - MtxOpMsg
    MDC container for request/response handling.
- 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.
- 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

Rehoming MDCs

The rehoming APIs move a subscription, group, or device from one customer sub-domain to a different sub-domain. For a description of the rehoming process, see the discussion about rehoming subscribers, groups, and devices in the object management overview.

Note: MATRIXX Support recommends using the REST rehoming APIs because the REST services manage the rehoming process whereas the Java rehoming process requires multiple steps.