DX: Checkout & Checkout Link API to accept product_id too vs. product_price_id only
Description
Support either product_price_id or product_id in the following endpoints.
POST /v1/checkouts/custom/POST /v1/checkout-links/
In case product_id is provided, the endpoints should default to the currently active product_price_id and first one in case of multiple (subscriptions, e.g monthly or annual).
Current Behavior
Today, we require a product_price_id. However, in most cases product_id is more intuitive in addition to being automatically updated to the most recent price in case of changes in the dashboard. We still want to support the latter for historic reasons + for customers seeking more advanced use cases and being more explicit.
Expected Behavior
- I can create a checkout session
POST /v1/checkouts/custom/withproduct_idinstead ofproduct_price_idand it will automatically use the active price for the session - I can create a checkout link
POST /v1/checkout-links/withproduct_idinstead ofproduct_price_idand upon going to the generated link I'm presented with a checkout reflecting the active price - I can change the price of the product and 1) run the same checkout API request and get the latest price & 2) use the old checkout link and come to the checkout with an updated price
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too