A unique identifier for this specific event. This ensures that each event can be
tracked and processed individually.
Describes the type of event. In this case, it signifies that a subscription has
entered the trialing state.
The timestamp when the event was generated, typically in milliseconds since the
Unix epoch (January 1, 1970). This value can be used to track when the event occurred.
A unique identifier for the specific subscription that transitioned to the active
state.
A timestamp indicating the date and time of the next scheduled payment, expressed
in milliseconds since the Unix epoch.
The number of billing cycles remaining for the subscription. For example, if the
total cycle count is 6 and 1 cycle has been completed, the remaining cycle count
will be
5
.A collection of key-value pairs that were provided when the object was
created. These metadata values are echoed back in the response, allowing you
to store and retrieve custom information such as context-specific attributes,
references, or tags. This can be useful for correlating records in your system
or attaching meaningful context to transactions.