Support for quantity in APIs
See original GitHub issue- When creating subscriptions, ability to specify a
quantity
(e.g.price=$20/mo, quantity=$2 => invoiceItem recurring amount=$40
). Related: #1434 - When creating external charges, specifying a
quantity
should be reflected into the invoice (e.g.price=$20, quantity=$2 => invoiceItem amount=$40
)
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Need API For To Get Total Quantity, Available To Transact ...
Need API For To Get Total Quantity, Available To Transact Quantity And Available To Reserve Quantity Using REST Websesrvices.
Read more >Limits and Quotas on API Requests | Analytics Reporting API v4
This document describes the limits and quotas of requesting the Management APIs and Reporting APIs. Google Analytics is used by millions of ...
Read more >quantity | API Reference | ArcGIS API for JavaScript 4.25
Quantity type used to represent measurements across the JS API. Type Definitions. Angle. Properties. value Number. Scalar value representing a angle.
Read more >updateQuantity | eBay Browse API - eBay Developers Program
This method updates the quantity value of a specific item in the eBay member's cart. You specify the ID of the item in...
Read more >Inventory API: What It Does - Square Developer
Use the Square Inventory API to adjust inventory quantities and review inventory changes for products in a Square catalog.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You need to ensure the conceptual integrity of your framework is maintained. Define things in the catalog. Assign the catalog values to the subscription when creating it and update them as needed. A per seat usage cost for a given range of seats (top tier policy) can be defined in the catalog giving users price per seat costs for a given number of seats.
You then need to be able to query the system catalog for the per seat price at a given quantity so that this can then be used to update the subscription. In cases where only the quantity changes but the seat price remains the same only the quantity should be updated.
System logic on pricing and quantity breaks needs to be controlled at the server end. The client should ask the server for a change to the quantity of seats that are being applied to the subscription in much the same way that happens when previewing changes on future dated invoices with a dry run. Business alignment and approval rules can then also be applied to the change request.
Hope that helps.
Got it. Just wanted to minimize the chance of duplicated effort.