All Downloads are FREE. Search and download functionalities are using the official Maven repository.

com.stripe.model.UsageRecord Maven / Gradle / Ivy

The newest version!
// File generated from our OpenAPI spec
package com.stripe.model;

import com.google.gson.annotations.SerializedName;
import com.stripe.exception.StripeException;
import com.stripe.net.ApiRequest;
import com.stripe.net.ApiRequestParams;
import com.stripe.net.ApiResource;
import com.stripe.net.BaseAddress;
import com.stripe.net.RequestOptions;
import com.stripe.param.UsageRecordCreateOnSubscriptionItemParams;
import java.util.Map;
import lombok.EqualsAndHashCode;
import lombok.Getter;
import lombok.Setter;

/**
 * Usage records allow you to report customer usage and metrics to Stripe for metered billing of
 * subscription prices.
 *
 * 

Related guide: Metered * billing * *

This is our legacy usage-based billing API. See the updated usage-based billing * docs. */ @Getter @Setter @EqualsAndHashCode(callSuper = false) public class UsageRecord extends ApiResource implements HasId { /** Unique identifier for the object. */ @Getter(onMethod_ = {@Override}) @SerializedName("id") String id; /** * Has the value {@code true} if the object exists in live mode or the value {@code false} if the * object exists in test mode. */ @SerializedName("livemode") Boolean livemode; /** * String representing the object's type. Objects of the same type share the same value. * *

Equal to {@code usage_record}. */ @SerializedName("object") String object; /** The usage quantity for the specified date. */ @SerializedName("quantity") Long quantity; /** The ID of the subscription item this usage record contains data for. */ @SerializedName("subscription_item") String subscriptionItem; /** The timestamp when this usage occurred. */ @SerializedName("timestamp") Long timestamp; /** * Creates a usage record for a specified subscription item and date, and fills it with a * quantity. * *

Usage records provide {@code quantity} information that Stripe uses to track how much a * customer is using your service. With usage information and the pricing model set up by the metered billing plan, * Stripe helps you send accurate invoices to your customers. * *

The default calculation for usage is to add up all the {@code quantity} values of the usage * records within a billing period. You can change this default behavior with the billing plan’s * {@code aggregate_usage} parameter. When * there is more than one usage record with the same timestamp, Stripe adds the {@code quantity} * values together. In most cases, this is the desired resolution, however, you can change this * behavior with the {@code action} parameter. * *

The default pricing model for metered billing is per-unit * pricing. For finer granularity, you can configure metered billing to have a tiered pricing model. */ public static UsageRecord createOnSubscriptionItem( String subscriptionItem, Map params) throws StripeException { return createOnSubscriptionItem(subscriptionItem, params, (RequestOptions) null); } /** * Creates a usage record for a specified subscription item and date, and fills it with a * quantity. * *

Usage records provide {@code quantity} information that Stripe uses to track how much a * customer is using your service. With usage information and the pricing model set up by the metered billing plan, * Stripe helps you send accurate invoices to your customers. * *

The default calculation for usage is to add up all the {@code quantity} values of the usage * records within a billing period. You can change this default behavior with the billing plan’s * {@code aggregate_usage} parameter. When * there is more than one usage record with the same timestamp, Stripe adds the {@code quantity} * values together. In most cases, this is the desired resolution, however, you can change this * behavior with the {@code action} parameter. * *

The default pricing model for metered billing is per-unit * pricing. For finer granularity, you can configure metered billing to have a tiered pricing model. */ public static UsageRecord createOnSubscriptionItem( String subscriptionItem, Map params, RequestOptions options) throws StripeException { String path = String.format( "/v1/subscription_items/%s/usage_records", ApiResource.urlEncodeId(subscriptionItem)); ApiRequest request = new ApiRequest(BaseAddress.API, ApiResource.RequestMethod.POST, path, params, options); return getGlobalResponseGetter().request(request, UsageRecord.class); } /** * Creates a usage record for a specified subscription item and date, and fills it with a * quantity. * *

Usage records provide {@code quantity} information that Stripe uses to track how much a * customer is using your service. With usage information and the pricing model set up by the metered billing plan, * Stripe helps you send accurate invoices to your customers. * *

The default calculation for usage is to add up all the {@code quantity} values of the usage * records within a billing period. You can change this default behavior with the billing plan’s * {@code aggregate_usage} parameter. When * there is more than one usage record with the same timestamp, Stripe adds the {@code quantity} * values together. In most cases, this is the desired resolution, however, you can change this * behavior with the {@code action} parameter. * *

The default pricing model for metered billing is per-unit * pricing. For finer granularity, you can configure metered billing to have a tiered pricing model. */ public static UsageRecord createOnSubscriptionItem( String subscriptionItem, UsageRecordCreateOnSubscriptionItemParams params) throws StripeException { return createOnSubscriptionItem(subscriptionItem, params, (RequestOptions) null); } /** * Creates a usage record for a specified subscription item and date, and fills it with a * quantity. * *

Usage records provide {@code quantity} information that Stripe uses to track how much a * customer is using your service. With usage information and the pricing model set up by the metered billing plan, * Stripe helps you send accurate invoices to your customers. * *

The default calculation for usage is to add up all the {@code quantity} values of the usage * records within a billing period. You can change this default behavior with the billing plan’s * {@code aggregate_usage} parameter. When * there is more than one usage record with the same timestamp, Stripe adds the {@code quantity} * values together. In most cases, this is the desired resolution, however, you can change this * behavior with the {@code action} parameter. * *

The default pricing model for metered billing is per-unit * pricing. For finer granularity, you can configure metered billing to have a tiered pricing model. */ public static UsageRecord createOnSubscriptionItem( String subscriptionItem, UsageRecordCreateOnSubscriptionItemParams params, RequestOptions options) throws StripeException { String path = String.format( "/v1/subscription_items/%s/usage_records", ApiResource.urlEncodeId(subscriptionItem)); ApiResource.checkNullTypedParams(path, params); ApiRequest request = new ApiRequest( BaseAddress.API, ApiResource.RequestMethod.POST, path, ApiRequestParams.paramsToMap(params), options); return getGlobalResponseGetter().request(request, UsageRecord.class); } }





© 2015 - 2025 Weber Informatics LLC | Privacy Policy