#gigstartr - transfer events
nimble steppe
hye there, just looking into this
I think it is related to some legacy events but trying to confirm
lethal brook
k. Building in failure responses, but couldn't see how these were useful - both failures look like ones that would have been in the err object of the original API call
nimble steppe
lethal brook
well, yeah, that's what I was refering to
but they're still in your documentation in list of all events
nimble steppe
Right, because integrations on old API versions may still see them
but you can most likely just ignore them if not significant to you
lethal brook
Well, I am a tad paranoid ("just because you're paranoid doesn't mean they're not actually after you"), and don't like to "just ignore"
I suppose I could send a feature request to support to label such things with version information - when they become relevant, when they cease being referenced
nimble steppe
But this applies to all events not relevant to you, you should only listen for ones that are necessary for you to take some action.
lethal brook
I'm only listening to TRANSFER events (in this bit'o'code), so it IS kinda relevant which ones will be generated
I can (and did) surmise that those events were "dead" and/or no longer relevant, but code review and basic error-checking require I follow up on ALL documentation inconsistencies.
nimble steppe
if you're talking about modern transfers (from a platform to a connected account) then those events are not relevant
lethal brook
Yes, I've surmised that, and yes, I'm using the most current API version and (express) connected accounts
nimble steppe
👍 -- i can share feedback that we should make it more clear in the docs that these are vestigial
lethal brook
As I said, I follow up on everything. I'd appreciate that followup! thx.
(net-net, btw, is I was making sure WHEN I could document a "receipt" for the action in my database, hence wanting to know if I had to wait for a "paid" event for success, and/or a "failed" event for failure.. It makes sense, now, that failure is immediate and the .create can be used for success/receipt)
(go ahead and close this, or I might snark again!)