Page Summary
-
PlanStatus provides details of all top-level mobile service packages purchased by a user, including plan information, account balance (for prepaid users), and notification types.
-
It includes fields like
name,plans,languageCode,expireTime,updateTime,title,subscriberId,accountInfo,uiCompatibility,notifications, andplanInfoPerClient, providing comprehensive data about the user's mobile service package. -
PlanStatus resources are identified by a unique name in the format
operators/{asn_id}/planStatuses/{userKey}and have a JSON representation for data exchange. -
Mobile operators can create new PlanStatus entries using the
createmethod, allowing them to manage and update user plan information.
Resource: PlanStatus
PlanStatus contains details of all top-level mobile service package a user has purchased.
| JSON representation | |
|---|---|
{ "name" : string , "plans" : [ { object ( |
|
| Fields | |
|---|---|
name
|
The resource name of the PlanStatus in the following format: |
plans[]
|
List of plans owned by this user. |
languageCode
|
Required. The BCP-47 language code, such as "en-US" or "sr-Latn". For more information, see http://www.unicode.org/reports/tr35/#Unicode_locale_identifier . |
expireTime
|
Required. Time when the shared plan group information becomes outdated. PlanStatus will not be served to applications after this time. A timestamp in RFC3339 UTC "Zulu" format, accurate to nanoseconds. Example: |
updateTime
|
Required. Time when the data plan agent (DPA) fetched the plan status information from backend systems. Could be used to determine how recent the plan status information is. A timestamp in RFC3339 UTC "Zulu" format, accurate to nanoseconds. Example: |
title
|
Title of the contract that user has with the operator. This will be shown in the UI header. |
subscriberId
|
Unique stable identifier in carrier system to identify the user. |
accountInfo
|
Required for prepaid users. Information about the user account balance. |
uiCompatibility
|
Determines if the PlanStatus can be shown to the user in a user interface. When set to UI_INCOMPATIBLE, the PlanStatus can be used for sending notifications to the user but will not be used for showing the plan information to user. |
notifications[]
|
The types of notifications that have been sent to the user. |
planInfoPerClient
|
|
Methods |
|
|---|---|
|
Allows a mobile operator (identified by its unique Autonomous System Number (ASN)) to add new PlanStatus entry. |

