POST requests have special headers. See "Webhook delivery headers" for more details. GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub.
Cancellations and downgrades take effect on the first day of the next billing cycle. Events for downgrades and cancellations are sent when the new plan takes effect at the beginning of the next billing cycle. Events for new purchases and upgrades begin immediately. Use the
effective_date in the webhook payload to determine when a change will begin.
Note: If you notice any spammy GitHub Marketplace purchases or other malicious behavior, please complete the report abuse form with more information on the user.
marketplace_purchase webhook payload will have the following information:
|The action performed to generate the webhook. Can be |
|The date the |
|The person who took the |
|The GitHub Marketplace purchase information.|
marketplace_purchase object has the following keys:
|Can be |
|Number of units purchased.|
|The date the free trial will expire.|
|The date that the next billing cycle will start. When the |
|The plan purchased by the |
plan object has the following keys:
|The unique identifier for this plan.|
|The plan's name.|
|This plan's description.|
|The monthly price of this plan in cents (US currency). For example, a listing that costs 10 US dollars per month will be 1000 cents.|
|The yearly price of this plan in cents (US currency). For example, a listing that costs 100 US dollars per month will be 120000 cents.|
|The pricing model for this listing. Can be one of |
|The name of the unit. If the pricing model is not |
|The names of the bullets set in the pricing plan.|
This example provides the
purchased event payload.
Changes in a plan include upgrades and downgrades. This example represents the
pending_change_cancelled event payloads. The action identifies which of these three events has occurred.