chargebee 2.28.0 → 2.30.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (54) hide show
  1. package/.github/ISSUE_TEMPLATE/bug_report.yml +81 -0
  2. package/.github/ISSUE_TEMPLATE/config.yml +6 -0
  3. package/.github/ISSUE_TEMPLATE/feature_request.yml +34 -0
  4. package/.github/PULL_REQUEST_TEMPLATE.md +8 -0
  5. package/.github/workflows/greeting.yml +47 -0
  6. package/CHANGELOG.md +59 -0
  7. package/SECURITY.md +8 -0
  8. package/lib/chargebee.js +1 -1
  9. package/lib/resources/api_endpoints.js +0 -14
  10. package/package.json +1 -1
  11. package/types/core.d.ts +4 -4
  12. package/types/resources/AttachedItem.d.ts +88 -88
  13. package/types/resources/Card.d.ts +68 -68
  14. package/types/resources/Comment.d.ts +50 -44
  15. package/types/resources/Coupon.d.ts +242 -207
  16. package/types/resources/CouponSet.d.ts +72 -68
  17. package/types/resources/CreditNote.d.ts +612 -236
  18. package/types/resources/Customer.d.ts +655 -513
  19. package/types/resources/DifferentialPrice.d.ts +99 -74
  20. package/types/resources/EntitlementOverride.d.ts +27 -12
  21. package/types/resources/Estimate.d.ts +450 -450
  22. package/types/resources/Event.d.ts +30 -12
  23. package/types/resources/Export.d.ts +200 -200
  24. package/types/resources/Feature.d.ts +66 -35
  25. package/types/resources/Gift.d.ts +54 -44
  26. package/types/resources/HostedPage.d.ts +381 -381
  27. package/types/resources/InAppSubscription.d.ts +94 -90
  28. package/types/resources/Invoice.d.ts +1242 -660
  29. package/types/resources/Item.d.ts +148 -142
  30. package/types/resources/ItemEntitlement.d.ts +36 -36
  31. package/types/resources/ItemFamily.d.ts +45 -45
  32. package/types/resources/ItemPrice.d.ts +317 -273
  33. package/types/resources/PaymentIntent.d.ts +60 -60
  34. package/types/resources/PaymentReferenceNumber.d.ts +1 -1
  35. package/types/resources/PaymentVoucher.d.ts +74 -59
  36. package/types/resources/PortalSession.d.ts +45 -20
  37. package/types/resources/PromotionalCredit.d.ts +68 -68
  38. package/types/resources/Purchase.d.ts +3 -3
  39. package/types/resources/Quote.d.ts +655 -366
  40. package/types/resources/QuoteLineGroup.d.ts +245 -0
  41. package/types/resources/QuotedCharge.d.ts +170 -0
  42. package/types/resources/QuotedSubscription.d.ts +219 -0
  43. package/types/resources/SiteMigrationDetail.d.ts +7 -7
  44. package/types/resources/Subscription.d.ts +1219 -932
  45. package/types/resources/SubscriptionEntitlement.d.ts +33 -12
  46. package/types/resources/ThirdPartyPaymentMethod.d.ts +1 -1
  47. package/types/resources/TimeMachine.d.ts +15 -15
  48. package/types/resources/Token.d.ts +0 -116
  49. package/types/resources/Transaction.d.ts +229 -112
  50. package/types/resources/UnbilledCharge.d.ts +112 -67
  51. package/types/resources/Usage.d.ts +46 -47
  52. package/types/resources/VirtualBankAccount.d.ts +66 -66
  53. package/types/resources/Media.d.ts +0 -33
  54. package/types/resources/NonSubscription.d.ts +0 -65
@@ -40,23 +40,80 @@ declare module 'chargebee' {
40
40
  export namespace InAppSubscription {
41
41
  export class InAppSubscriptionResource {
42
42
  /**
43
- * @description This API verifies the application id `{in_app_subscription_app_id}` and `receipt` then returns the subscription details associated with the purchase.
43
+ * @description Verifies an in-app purchase made by your customer and creates a subscription in Chargebee.
44
+ **Tip**
44
45
 
45
- #### Path Parameter
46
+ The recommended approach is to call this endpoint from the client-side app directly. However, if you are using this API to replace an existing direct integration with Apple or Google, then you may choose to call this API from the server-side.
47
+ **Note:**
46
48
 
47
- in_app_subscription_app_id
48
- required, string
49
+ if App Store or Play Store products have not been imported to Chargebee and this API is invoked, Chargebee will automatically create plans that correspond to the store product IDs. However, if historical subscriptions are to be imported using the [import receipt](https://apidocs.chargebee.com/docs/api/in_app_subscriptions#import_receipt) API, importing products is mandatory. [Learn more](https://www.chargebee.com/docs/mobile_subscriptions.html).
49
50
 
50
- The handle is created by Chargebee for your Apple App Store or Google Play Store app. It can be obtained from the Chargebee web app.
51
+ Apple App Store {#app_store}
52
+ ----------------------------
53
+
54
+ This section provides details of the Process Purchase Command operation when performed for the Apple App Store. This API processes only the latest in-app transaction on the receipt. Sync historical subscriptions into Chargebee using [bulk import](https://www.chargebee.com/docs/2.0/mobile-app-store-product-iap.html#import-in-app-purchase-receipts) of In-App Purchase receipts.
55
+ **Important**
56
+
57
+ * [Integrate Chargebee](https://www.chargebee.com/docs/mobile-app-store-connect.html#connnect-with-your-chargebee-site) with your Apple App Store account using your shared secret from Apple.
58
+ * It is strongly recommended to use this endpoint to notify Chargebee of **new** purchases only.
59
+ * For updates to existing subscriptions, we recommend that you configure Apple App Store to send server notifications to Chargebee.
60
+
61
+ Chargebee validates the `receipt` with Apple App Store and does the following once validation succeeds:
62
+
63
+ 1. Look for [item_family.id](/docs/api/item_families?prod_cat_ver=2#item_family_id) that matches the value Apple-App-Store, and create such a product family if not found.
64
+ 2. Look for [item.id](/docs/api/items?prod_cat_ver=2#item_id) that matches `product[id]` and if not found, create such a plan-item under the item family described in the previous step.
65
+ 3. Look for [item_price.id](/docs/api/item_prices?prod_cat_ver=2#item_price_id) that matches the concatenation of `product[id]` and `product[currency_code]`, and if not found, create such an item price under the item described in the previous step.
66
+ 4. Create/update a subscription:
67
+ * If the receipt is for a new purchase, a new subscription is created for the plan-item price described in the previous step. The subscription has the following details:
68
+ * `id` set to [original_transaction_id](https://developer.apple.com/documentation/appstorereceipts/original_transaction_id?language=objc)
69
+ * `start_date` set to [responseBody.Latest_receipt_info.purchase_date_ms](https://developer.apple.com/documentation/appstorereceipts/responsebody/latest_receipt_info?language=objc)
70
+ * `current_term_end` set to `responseBody.Latest_receipt_info.expires_date_ms`
71
+ * Instead, if the receipt belongs to an existing subscription in Chargebee, it is updated to reflect the current state of the subscription at Apple.
72
+ 5. The payment is recorded against the subscription invoice. The associated transaction is updated with the following details:
73
+ * The [transaction.reference_number](/docs/api/transactions?prod_cat_ver=2#transaction_reference_number) is set to the [transaction_id](https://developer.apple.com/documentation/appstorereceipts/transaction_id?language=objc) of the payment.
74
+ * The [transaction.payment_method](/docs/api/transactions#transaction_payment_method) is set to `apple_pay`.
75
+
76
+ Google Play Store {#app_store}
77
+ ------------------------------
78
+
79
+ This section provides details of the Process Purchase Command operation when performed for the Google Play Store. This API processes only the latest in-app transaction using the purchase token.
80
+ **Important**
81
+
82
+ * [Integrate Chargebee](https://www.chargebee.com/docs/2.0/mobile-playstore-connect.html#chargebee-configuration) with your Google Play Store account using the service account credentials JSON.
83
+ * It is strongly recommended to use this endpoint to notify Chargebee of **new** purchases only.
84
+ * For updates to existing subscriptions, we recommend that you configure Chargebee to receive Google's server notifications through pub/sub topic. [Learn more](https://developer.android.com/google/play/billing/getting-ready#setup-pubsub).
85
+
86
+ Chargebee validates the purchase **token** with Google Play Store and does the following once validation succeeds:
87
+
88
+ 1. Look for [item_family.id](/docs/api/item_families?prod_cat_ver=2#item_family_id) that matches the value `Google-Play-Store`, and create such a product family if not found.
89
+ 2. Look for [item.id](/docs/api/items?prod_cat_ver=2#item_id) that matches `product[id]` and if not found, create such a [plan-item](/docs/api/items?prod_cat_ver=2#item_type) under the item family described in the previous step.
90
+ 3. Look for [item_price.id](/docs/api/item_prices?prod_cat_ver=2#item_price_id) that matches the concatenation of `product[id]` and [priceCurrencyCode](https://developers.google.com/android-publisher/api-ref/rest/v3/purchases.subscriptions?hl=en#SubscriptionPurchase.FIELDS.price_currency_code), and if not found, create such an item price under the item described in the previous step.
91
+ 4. Create/update a subscription:
92
+ * If this token is for a new purchase, a new subscription is created for the plan-item price described in the previous step. The subscription has the following details:
93
+ * `id` set to unique identifier generated by Chargebee and mapped to **token** of the [SubscriptionPurchase](https://developers.google.com/android-publisher/api-ref/rest/v3/purchases.subscriptions?hl=en) object from Google response.
94
+ * `start_date` set to `SubscriptionPurchase.startTimeMillis`.
95
+ * `current_term_end` set to `SubscriptionPurchase.expiryTimeMillis`.
96
+ * Instead, if the token belongs to an existing subscription in Chargebee, it is updated to reflect the current state of the subscription at Google.
97
+ 5. The payment is recorded against the subscription invoice. The associated transaction is updated with the following details:
98
+ * The [transaction.reference_number](/docs/api/transactions?prod_cat_ver=2#transaction_reference_number) is set to the [orderId](https://developers.google.com/android-publisher/api-ref/rest/v3/purchases.subscriptions?hl=en#SubscriptionPurchase.FIELDS.order_id) of the payment.
99
+ * The [transaction.payment_method](/docs/api/transactions#transaction_payment_method) is set to `play_store`.
100
+
101
+ Path Parameter {#path_param_pcv2}
102
+ ---------------------------------
103
+
104
+ `{in_app_subscription_app_id}`: The handle created by Chargebee for your Apple App Store or Google Play Store app. It can be obtained from the Chargebee web app.
51
105
 
52
106
  The following are instructions to obtain the value of the path parameter for the Apple App Store and Google Play Store.
53
107
 
54
108
  * **Apple App Store** : To obtain the value for `{in_app_subscription_app_id}`, click **View Keys** within the **Sync Overview** page of the web app and use the value of generated **App ID** for this parameter. See detailed steps [here](https://www.chargebee.com/docs/1.0/mobile-app-store-product-iap.html#resource-id).
55
109
  * **Google Play Store** : To obtain the value for `{in_app_subscription_app_id}`, click **Set up notifications** within the **Sync Overview** page of the web app and use the value of generated **App ID** for this parameter. See detailed steps [here](https://www.chargebee.com/docs/1.0/mobile-playstore-notifications.html#app-id).
56
110
 
111
+
112
+
113
+
57
114
  */
58
115
 
59
- retrieve_store_subs(in_app_subscription_app_id:string, input:RetrieveStoreSubsInputParam):ChargebeeRequest<RetrieveStoreSubsResponse>;
116
+ process_receipt(in_app_subscription_app_id:string, input:ProcessReceiptInputParam):ChargebeeRequest<ProcessReceiptResponse>;
60
117
 
61
118
  /**
62
119
  * @description Verifies an Apple App Store or Google Play Store in-app purchase [receipt](https://developer.apple.com/documentation/storekit/original_api_for_in-app_purchase/validating_receipts_with_the_app_store?language&#x3D;objc#overview) and imports [subscriptions](/docs/api/subscriptions) for all historical purchases made by the customer.
@@ -64,6 +121,7 @@ The following are instructions to obtain the value of the path parameter for the
64
121
  An &#x60;in_app_subscription&#x60; is created for every unique &#x60;original_transaction_id&#x60;. Apple creates &#x60;original_transaction_id&#x60; for every create, upgrade, or downgrade of the subscription. A receipt hardly contains more than 100 &#x60;original_transaction_id&#x60;s. If a receipt contains more than 100 &#x60;original_transaction_id&#x60;s, Chargebee creates all subscription records but this endpoint returns the first 100 records in the response.
65
122
 
66
123
  CSV upload has a file size [limitation](https://www.chargebee.com/docs/mobile-app-store-product-iap.html#upload-in-app-receipts) that increases the processing time and the number of receipts. This API removes such limitations and allows you to import historical in-app subscription receipts.
124
+ **Note** : This API verifies receipt or token through Apple or Google and then processes them via Chargebee. For bulk imports, limit API calls to **6** per minute (**10** seconds apart) to ensure successful subscription imports.
67
125
 
68
126
  Apple App Store {#app_store}
69
127
  ----------------------------
@@ -175,7 +233,10 @@ The following are instructions to obtain the value of the path parameter for the
175
233
  * @description The Import Subscriptions endpoint is a Chargebee API that allows you to import historic In-App Subscriptions without using a valid Apple App Store receipt. This endpoint is useful if you do not have access to the receipt data which is required for the [Import Receipt](https://apidocs.chargebee.com/docs/api/in_app_subscriptions#import_receipt) API.
176
234
 
177
235
  With this API, you can import subscriptions and corresponding invoices for historic In-App purchases. The API returns the [in-app-subscriptions object](https://apidocs.chargebee.com/docs/api/in_app_subscriptions#in_app_subscription_attributes) once the historic subscription is successfully imported into Chargebee.
178
- **Note**: Subscription cannot be imported from Google Play Store without a receipt or token. Therefore; Chargebee does not allow you to use this API for Google Play Store.
236
+ **Note** :
237
+
238
+ * Subscriptions cannot be imported from the Google Play Store without a receipt or token. Therefore; Chargebee does not allow you to use this API for the Google Play Store.
239
+ * Enable V1 notifications in the Apple App Store for subscriptions created without receipts. Chargebee depends on receipt data to update subscription statuses. Apple&#x27;s V2 notifications do not have receipt information; therefore, Chargebee cannot process V2 notifications for subscriptions imported without receipts. Learn more about [++app store notifications++](https://apidocs.chargebee.com/docs/api/in_app_purchase_events?prod_cat_ver&#x3D;2#app_store_notifications) and [++notification URL configuration++](https://www.chargebee.com/docs/mobile-app-store-product-iap.html#connection-keys_notification-url).
179
240
 
180
241
  ### Apple App Store
181
242
 
@@ -239,85 +300,28 @@ To obtain the value of &#x60;in_app_subscription_app_id &#x60;for the Apple App
239
300
  import_subscription(in_app_subscription_app_id:string, input?:ImportSubscriptionInputParam):ChargebeeRequest<ImportSubscriptionResponse>;
240
301
 
241
302
  /**
242
- * @description Verifies an in-app purchase made by your customer and creates a subscription in Chargebee.
243
- **Tip**
244
-
245
- The recommended approach is to call this endpoint from the client-side app directly. However, if you are using this API to replace an existing direct integration with Apple or Google, then you may choose to call this API from the server-side.
246
- **Note:**
247
-
248
- if App Store or Play Store products have not been imported to Chargebee and this API is invoked, Chargebee will automatically create plans that correspond to the store product IDs. However, if historical subscriptions are to be imported using the [import receipt](https://apidocs.chargebee.com/docs/api/in_app_subscriptions#import_receipt) API, importing products is mandatory. [Learn more](https://www.chargebee.com/docs/mobile_subscriptions.html).
249
-
250
- Apple App Store {#app_store}
251
- ----------------------------
252
-
253
- This section provides details of the Process Purchase Command operation when performed for the Apple App Store. This API processes only the latest in-app transaction on the receipt. Sync historical subscriptions into Chargebee using [bulk import](https://www.chargebee.com/docs/2.0/mobile-app-store-product-iap.html#import-in-app-purchase-receipts) of In-App Purchase receipts.
254
- **Important**
255
-
256
- * [Integrate Chargebee](https://www.chargebee.com/docs/mobile-app-store-connect.html#connnect-with-your-chargebee-site) with your Apple App Store account using your shared secret from Apple.
257
- * It is strongly recommended to use this endpoint to notify Chargebee of **new** purchases only.
258
- * For updates to existing subscriptions, we recommend that you configure Apple App Store to send server notifications to Chargebee.
259
-
260
- Chargebee validates the &#x60;receipt&#x60; with Apple App Store and does the following once validation succeeds:
261
-
262
- 1. Look for [item_family.id](/docs/api/item_families?prod_cat_ver&#x3D;2#item_family_id) that matches the value Apple-App-Store, and create such a product family if not found.
263
- 2. Look for [item.id](/docs/api/items?prod_cat_ver&#x3D;2#item_id) that matches &#x60;product[id]&#x60; and if not found, create such a plan-item under the item family described in the previous step.
264
- 3. Look for [item_price.id](/docs/api/item_prices?prod_cat_ver&#x3D;2#item_price_id) that matches the concatenation of &#x60;product[id]&#x60; and &#x60;product[currency_code]&#x60;, and if not found, create such an item price under the item described in the previous step.
265
- 4. Create/update a subscription:
266
- * If the receipt is for a new purchase, a new subscription is created for the plan-item price described in the previous step. The subscription has the following details:
267
- * &#x60;id&#x60; set to [original_transaction_id](https://developer.apple.com/documentation/appstorereceipts/original_transaction_id?language&#x3D;objc)
268
- * &#x60;start_date&#x60; set to [responseBody.Latest_receipt_info.purchase_date_ms](https://developer.apple.com/documentation/appstorereceipts/responsebody/latest_receipt_info?language&#x3D;objc)
269
- * &#x60;current_term_end&#x60; set to &#x60;responseBody.Latest_receipt_info.expires_date_ms&#x60;
270
- * Instead, if the receipt belongs to an existing subscription in Chargebee, it is updated to reflect the current state of the subscription at Apple.
271
- 5. The payment is recorded against the subscription invoice. The associated transaction is updated with the following details:
272
- * The [transaction.reference_number](/docs/api/transactions?prod_cat_ver&#x3D;2#transaction_reference_number) is set to the [transaction_id](https://developer.apple.com/documentation/appstorereceipts/transaction_id?language&#x3D;objc) of the payment.
273
- * The [transaction.payment_method](/docs/api/transactions#transaction_payment_method) is set to &#x60;apple_pay&#x60;.
274
-
275
- Google Play Store {#app_store}
276
- ------------------------------
277
-
278
- This section provides details of the Process Purchase Command operation when performed for the Google Play Store. This API processes only the latest in-app transaction using the purchase token.
279
- **Important**
280
-
281
- * [Integrate Chargebee](https://www.chargebee.com/docs/2.0/mobile-playstore-connect.html#chargebee-configuration) with your Google Play Store account using the service account credentials JSON.
282
- * It is strongly recommended to use this endpoint to notify Chargebee of **new** purchases only.
283
- * For updates to existing subscriptions, we recommend that you configure Chargebee to receive Google&#x27;s server notifications through pub/sub topic. [Learn more](https://developer.android.com/google/play/billing/getting-ready#setup-pubsub).
284
-
285
- Chargebee validates the purchase **token** with Google Play Store and does the following once validation succeeds:
303
+ * @description This API verifies the application id &#x60;{in_app_subscription_app_id}&#x60; and &#x60;receipt&#x60; then returns the subscription details associated with the purchase.
286
304
 
287
- 1. Look for [item_family.id](/docs/api/item_families?prod_cat_ver&#x3D;2#item_family_id) that matches the value &#x60;Google-Play-Store&#x60;, and create such a product family if not found.
288
- 2. Look for [item.id](/docs/api/items?prod_cat_ver&#x3D;2#item_id) that matches &#x60;product[id]&#x60; and if not found, create such a [plan-item](/docs/api/items?prod_cat_ver&#x3D;2#item_type) under the item family described in the previous step.
289
- 3. Look for [item_price.id](/docs/api/item_prices?prod_cat_ver&#x3D;2#item_price_id) that matches the concatenation of &#x60;product[id]&#x60; and [priceCurrencyCode](https://developers.google.com/android-publisher/api-ref/rest/v3/purchases.subscriptions?hl&#x3D;en#SubscriptionPurchase.FIELDS.price_currency_code), and if not found, create such an item price under the item described in the previous step.
290
- 4. Create/update a subscription:
291
- * If this token is for a new purchase, a new subscription is created for the plan-item price described in the previous step. The subscription has the following details:
292
- * &#x60;id&#x60; set to unique identifier generated by Chargebee and mapped to **token** of the [SubscriptionPurchase](https://developers.google.com/android-publisher/api-ref/rest/v3/purchases.subscriptions?hl&#x3D;en) object from Google response.
293
- * &#x60;start_date&#x60; set to &#x60;SubscriptionPurchase.startTimeMillis&#x60;.
294
- * &#x60;current_term_end&#x60; set to &#x60;SubscriptionPurchase.expiryTimeMillis&#x60;.
295
- * Instead, if the token belongs to an existing subscription in Chargebee, it is updated to reflect the current state of the subscription at Google.
296
- 5. The payment is recorded against the subscription invoice. The associated transaction is updated with the following details:
297
- * The [transaction.reference_number](/docs/api/transactions?prod_cat_ver&#x3D;2#transaction_reference_number) is set to the [orderId](https://developers.google.com/android-publisher/api-ref/rest/v3/purchases.subscriptions?hl&#x3D;en#SubscriptionPurchase.FIELDS.order_id) of the payment.
298
- * The [transaction.payment_method](/docs/api/transactions#transaction_payment_method) is set to &#x60;play_store&#x60;.
305
+ #### Path Parameter
299
306
 
300
- Path Parameter {#path_param_pcv2}
301
- ---------------------------------
307
+ in_app_subscription_app_id
308
+ required, string
302
309
 
303
- &#x60;{in_app_subscription_app_id}&#x60;: The handle created by Chargebee for your Apple App Store or Google Play Store app. It can be obtained from the Chargebee web app.
310
+ The handle is created by Chargebee for your Apple App Store or Google Play Store app. It can be obtained from the Chargebee web app.
304
311
 
305
312
  The following are instructions to obtain the value of the path parameter for the Apple App Store and Google Play Store.
306
313
 
307
314
  * **Apple App Store** : To obtain the value for &#x60;{in_app_subscription_app_id}&#x60;, click **View Keys** within the **Sync Overview** page of the web app and use the value of generated **App ID** for this parameter. See detailed steps [here](https://www.chargebee.com/docs/1.0/mobile-app-store-product-iap.html#resource-id).
308
315
  * **Google Play Store** : To obtain the value for &#x60;{in_app_subscription_app_id}&#x60;, click **Set up notifications** within the **Sync Overview** page of the web app and use the value of generated **App ID** for this parameter. See detailed steps [here](https://www.chargebee.com/docs/1.0/mobile-playstore-notifications.html#app-id).
309
316
 
310
-
311
-
312
-
313
317
  */
314
318
 
315
- process_receipt(in_app_subscription_app_id:string, input:ProcessReceiptInputParam):ChargebeeRequest<ProcessReceiptResponse>;
319
+ retrieve_store_subs(in_app_subscription_app_id:string, input:RetrieveStoreSubsInputParam):ChargebeeRequest<RetrieveStoreSubsResponse>;
316
320
  }
317
- export interface RetrieveStoreSubsResponse {
318
- in_app_subscriptions:InAppSubscription[];
321
+ export interface ProcessReceiptResponse {
322
+ in_app_subscription:InAppSubscription;
319
323
  }
320
- export interface RetrieveStoreSubsInputParam {
324
+ export interface ProcessReceiptInputParam {
321
325
 
322
326
  /**
323
327
  * @description **Apple App Store** : The Base64 encoded [App Store in-app purchase receipt](https://developer.apple.com/documentation/storekit/original_api_for_in-app_purchase/validating_receipts_with_the_app_store?language&#x3D;objc#overview) taken from the Apple device after successful creation of the in-app purchase subscription.
@@ -327,6 +331,20 @@ The following are instructions to obtain the value of the path parameter for the
327
331
  */
328
332
 
329
333
  receipt:string;
334
+
335
+ /**
336
+ * @description Parameters for product
337
+
338
+ */
339
+
340
+ product?:{currency_code:string,id:string,name?:string,period?:string,period_unit?:string,price:number,price_in_decimal?:string};
341
+
342
+ /**
343
+ * @description Parameters for customer
344
+
345
+ */
346
+
347
+ customer?:{email?:string,first_name?:string,id?:string,last_name?:string};
330
348
  }
331
349
  export interface ImportReceiptResponse {
332
350
  in_app_subscriptions:InAppSubscription[];
@@ -375,10 +393,10 @@ The following are instructions to obtain the value of the path parameter for the
375
393
 
376
394
  customer?:{email?:string,id?:string};
377
395
  }
378
- export interface ProcessReceiptResponse {
379
- in_app_subscription:InAppSubscription;
396
+ export interface RetrieveStoreSubsResponse {
397
+ in_app_subscriptions:InAppSubscription[];
380
398
  }
381
- export interface ProcessReceiptInputParam {
399
+ export interface RetrieveStoreSubsInputParam {
382
400
 
383
401
  /**
384
402
  * @description **Apple App Store** : The Base64 encoded [App Store in-app purchase receipt](https://developer.apple.com/documentation/storekit/original_api_for_in-app_purchase/validating_receipts_with_the_app_store?language&#x3D;objc#overview) taken from the Apple device after successful creation of the in-app purchase subscription.
@@ -388,20 +406,6 @@ The following are instructions to obtain the value of the path parameter for the
388
406
  */
389
407
 
390
408
  receipt:string;
391
-
392
- /**
393
- * @description Parameters for product
394
-
395
- */
396
-
397
- product?:{currency_code:string,id:string,name?:string,period?:string,period_unit?:string,price:number,price_in_decimal?:string};
398
-
399
- /**
400
- * @description Parameters for customer
401
-
402
- */
403
-
404
- customer?:{email?:string,first_name?:string,id?:string,last_name?:string};
405
409
  }
406
410
 
407
411
  }