#bjoveski
1 messages · Page 1 of 1 (latest)
hi! first off — we know almost nothing about Sigma here, but I'll try.
sli is Subscription line item, it's the id of the line item on a subscription that has the recurring price
it used to be the case in old API versions that line items did not have a unique ID and the line item on the invoice was the same as the items in the Subscription, it was changed in https://stripe.com/docs/upgrades#2019-12-03 but it's possible Sigma uses the old format or something
thank you - great to have the sli confirmation
what is the difference between the "subscription item" and "subscription line item"? the same separation exists for "invoice item" and "invoice line item"
in particular, sigma doesn't seem to expose "subscription line items" (but it does expose the other 3:
subscription item is the items array on the Subscription, it's the "things" that subscription is subscribed for, like the recurring prices and their quantity and their reported usage
subscription line item is not a specific object, it's the line item on an invoice that corresponds to the line that charges for a recurring price on the subscription(as opposed to items that are for one-off additions or prorations or etc). i.e. it is the invoice line items that are type:subscription
AFAIUI, the SubscriptionItem for recurring prices has the ID sli_xxx, and in old API versions, the line item on each invoice that gets created which is charging for the subscription, would inherit/use that same ID. But then it was made so that every invoice line item has a unique ID instead
thank you - that makes sense
one more question - the invoice line item has metadata hash; the docs say "Note that for line items with type=subscription this will reflect the metadata of the subscription that caused the line item to be created."
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
do they get copied from the subscription line item metadata or the subscription metadata?
not sure, but it would be super quick to test, just create a Subscription in test mode and pass metadata to that field, and then again but don't pass it to that field and to the subscription.metadata instead, and look at the first Invoice of each subscription to see what appears in the lines
that's a great idea - will do that. i also assume that it comes from the line items due to the 1-1 mapping between them, but will double check
also just double checking - there is no test mode for sigma; correct?