SKU object
SKU structure
ID of the SKU.
ID of the parent application.
Customer-facing name of your premium offering.
System-generated URL slug based on the SKU’s name.
SKU example
SKU types
For subscriptions, SKUs have a type of eitherSUBSCRIPTION (type: 5) or SUBSCRIPTION_GROUP (type: 6). For current implementations, use the SKU defined by type: 5. A SUBSCRIPTION_GROUP is automatically created for each SUBSCRIPTION SKU and is not used at this time.
| Type | Value | Description |
|---|---|---|
| DURABLE | 2 | Durable one-time purchase |
| CONSUMABLE | 3 | Consumable one-time purchase |
| SUBSCRIPTION | 5 | Represents a recurring subscription |
| SUBSCRIPTION_GROUP | 6 | System-generated group for each SUBSCRIPTION SKU created |
SKU flags
For subscriptions, there are two types of access levels you can offer:- Guild subscriptions: A subscription purchased by a user and applied to a single server. Everyone in that server gets your premium benefits.
- User subscriptions: A subscription purchased by a user for themselves. They get access to your premium benefits in every server.
flags field with a bitwise & operator to differentiate user and server subscriptions.
| Flag | Value | Description |
|---|---|---|
| AVAILABLE | 1 << 2 | SKU is available for purchase. |
| GUILD_SUBSCRIPTION | 1 << 7 | Recurring SKU that can be purchased by a user and applied to a single server. Grants access to every user in that server. |
| USER_SUBSCRIPTION | 1 << 8 | Recurring SKU purchased by a user for themselves. Grants access to the purchasing user in every server. |
List SKUs
GET /applications/{application.id}/skusBecause of how the SKU and subscription systems work, you will see two SKUs for your subscription offering. For integrating and testing entitlements for subscriptions, use the SKU with
type: 5.