Menu

Expand
Rate this page:

BillingPeriod Subresource

BETA

Billing Periods for Super SIM is currently in Public Beta. Some features are not yet implemented and others may be changed before the product is declared Generally Available. Beta products are not covered by a Twilio SLA. Learn more about beta product support.

To avoid ambiguity throughout this page, Sim (initial cap) refers to the Sim API resource. SIM (all caps) refers to the physical Subscriber Identity Module (that is, a SIM card) associated with a Sim resource.

A BillingPeriod instance represents a period of time and belongs to a Sim instance. Depending on the type of the BillingPeriod, billing events such as charging a SIM’s monthly subscription fee or resetting the amount applied towards a SIM’s data limit may occur at the start or the end of a BillingPeriod.

https://supersim.twilio.com/v1/Sims/{sid}/BillingPeriods

A Sim whose status is new will not have any BillingPeriods. A Sim’s first BillingPeriod will be created when its status is updated to ready or active and will begin at the time denoted by the BillingPeriod’s start_time. Events set to occur at the start of the BillingPeriod will take place. When a BillingPeriod expires — i.e., the current time is after the BillingPeriod's end_time — any events set to occur at the end of the BillingPeriod will take place. Unless the Sim’s status is inactive, when its BillingPeriod expires a new one will be created. This process will be repeated for as long as the Sim’s status continues to be active.

Currently, only a Sim’s current or most recent BillingPeriod will be returned when reading a Sim’s BillingPeriods. It will be returned as a single result in an array. In a future release, we will add the ability to view previous BillingPeriods as a paginated list.

BillingPeriod properties

Resource Properties in REST API format
sid
sid<HB> Not PII

The SID of the Billing Period.

account_sid
sid<AC> Not PII

The SID of the Account the Super SIM belongs to.

sim_sid
sid<HS> Not PII

The SID of the Super SIM the Billing Period belongs to.

start_time
date_time<iso8601> Not PII

The start time of the Billing Period specified in ISO 8601 format.

end_time
date_time<iso8601> Not PII

The end time of the Billing Period specified in ISO 8601 format.

period_type
enum:bp_type Not PII

The type of Billing Period. Can be ready or active.

date_created
date_time<iso8601> Not PII

The date and time in GMT when the resource was created specified in ISO 8601 format.

date_updated
date_time<iso8601> Not PII

The date and time in GMT when the resource was last updated specified in ISO 8601 format.

BillingPeriod types

This section describes the behavior of each type of BillingPeriod as indicated by the BillingPeriod’s period_type.

Ready BillingPeriods

A Sim resource’s status can only be updated to ready from new. When this change occurs, a ready BillingPeriod resource will be created starting at that time. The ready BillingPeriod’s end_time indicates when the Sim resource’s status will automatically transition from ready to active if no other transition criteria are met. When a Sim’s status is ready, the SIM it represents may connect to the cellular networks without incurring a monthly subscription fee until either the ready BillingPeriod expires, or some amount of data/SMS Command usage occurs, whichever comes first. Learn more about each Sim resource status.

Active BillingPeriods

A new active BillingPeriod will be created in either of these cases:

  • A Sim’s status is updated to active and there is not already an unexpired active BillingPeriod for that Sim.
  • An active BillingPeriod expires and the status of the Sim to which it belongs is still active.

When an active BillingPeriod is created, the monthly active SIM subscription fee will be charged. If a Sim’s status is updated to inactive before the current active BillingPeriod expires, no new BillingPeriod will be created. If Sim’s status is later changed back to active, a new active BillingPeriod will be created starting at that time.

Each SIM has a data limit dictated by the Fleet to which its Sim resource has been assigned. Data usage is counted during the Sim’s current active BillingPeriod and compared to the Sim’s data limit. If the count reaches the limit, the SIM will be blocked from using any more data until the active BillingPeriod expires. When an active BillingPeriod expires, the data usage counter is reset to zero. If a SIM has been blocked from using data because it exceeded its data limit, it will be able to resume using data at this point.

Read multiple BillingPeriod resources

get
https://supersim.twilio.com/v1/Sims/{SimSid}/BillingPeriods

As noted above, currently only a Sim’s current or most recent BillingPeriod will be returned in the results.

Parameters
Parameters in REST API format
sim_sid
Path
get sid_like<HS> Not PII

The SID of the Super SIM to list Billing Periods for.

Example 1
        
        
        

        How to check if a SIM has hit its data limit

        As indicated above, the Sim’s current active BillingPeriod is used to determine whether a SIM has exceeded its data limit. A SIM will be blocked if it has used more data between the BillingPeriod's start_time and end_time than permitted by the Sim’s Fleet. To determine what percentage of a SIM’s data limit has been used, follow these steps:

        1. Fetch the Sim’s Fleet using the value from the Sim’s fleet_sid.
        2. Extract the data_limit value.
        3. Fetch the Sim’s current active BillingPeriod.
        4. Use the current active BillingPeriod’s start_time and end_time values along with the Sim’s SID to query the UsageRecords resource. If you didn’t provide a value for the Granularity query parameter, you will only receive one record in the results. This represents the aggregated usage over the request period.
        5. Extract the data_total value.
        6. Divide data_total by the Fleet’s data_limit to determine what percentage of the SIM’s data limit has been used.

        The workflow described above works well if you are building a task applied to a single SIM or to a small number of SIMs that can be easily iterated over, such as rendering an internal dashboard showing SIM details. However, if you are building a task that will continuously check whether each SIM in your fleet of devices has exceeded its data limit, consider using Super SIM Connection Events. The data_modifier property in Data Session Started, Data Session Updated, and Data Session Ended events will be populated with blocked if a SIM has exceeded its data limit and is being blocked.

        Rate this page:

        Need some help?

        We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Community Forums or browsing the Twilio tag on Stack Overflow.

              
              
              

              Thank you for your feedback!

              We are always striving to improve our documentation quality, and your feedback is valuable to us. Please select the reason(s) for your feedback or provide additional information about how we can improve:

              Sending your feedback...
              🎉 Thank you for your feedback!
              Something went wrong. Please try again.

              Thanks for your feedback!

              Refer us and get $10 in 3 simple steps!

              Step 1

              Get link

              Get a free personal referral link here

              Step 2

              Give $10

              Your user signs up and upgrade using link

              Step 3

              Get $10

              1,250 free SMSes
              OR 1,000 free voice mins
              OR 12,000 chats
              OR more