Forums/Community/Community Support
Answered
Transaction API : Product ID
Jon
asked this on May 03, 2011 02:51 am
I'm working with the transaction API, and it appears as though the Product ID field is always the same (current product) regardless of what it was at the time that the transaction occurred. Is this intended functionality? If so, how can I look back at the different products my customers have been subscribed to over time?
Comments
Hello Jon,
Thanks for contacting Chargify.
I am forwarding your question to our technical sales team for their review.
Regards,
Jay G.
Hi Jon,
I think it is as you say... always current product ID, no history of past products (assuming there were changes, like upgrades, along the way).
But I'll tag this for Level 2 support to see if they have any comment.
Thanks.
--- Lance
Jon,
I believe Lance is right, transactions are associated to a subscription and that subscription is subscribed to a product. When you call the transaction API method, it's just returning the current subscription details.
If you want historical record, you'll likely have to track it yourself (you could use webhooks
payment_successevent, and check if the product is the same as the last recorded one. If not, then it's been changed - and record the new value)-- Kori
Passing the buck on recording historic data kind of sucks for API consumers.
Everything else that is part of the transaction payload is recorded as it existed at the time of the transaction, so it makes no sense for the product_id to be live. You should change the way product_id works, or add a new field that actually records the historic product_id information.
Joel - your timing is great. We will be doing this, starting very soon. This will include a reconstruction of product history in the account transactions, as best we can given the data we have (which should be accurate going back over a year)
Thanks for the update, Michael.
Hey Michael,
Any bump on this?