#ebon2000
tiny stirrup
high gyro
hi! wouldn't be able to confirm anything without looking at the accounts and failed API requests involved directly.
high gyro
I'd probably suggest reaching out to https://support.stripe.com/?contact=true to get your accounts all set up properly since there are multiple layers here(we can give you access to a beta feature but only for your own account and it then doesn't work if you make Connect requests); it's more about your setup and use cases than any specific code or develpment work on your side
fast veldt
The use case is that we are an accounting and invoicing platform. Users connect their accounts to us in accounting and we pull all their transactions and build their accounting ledger. All is good with this and it all works well. But for issuing transaction we need to look up the transaction using the source so that we can get some more information and create the vendor in the accounting platform related to the issuing transaction.
The issue is only when we try and look up the Issuing Transaction using the id that we get this error
high gyro
sounds good, likely it's just that your platform account doesn't have access configured properly for this(like we only gave you access to read transcactions on your own account and not via Connect). I'd reach out to support to explain the use case for help
unfortunately the reality of using Connect like this to read data is that the connected accounts can be using various betas or private APIs and then you would need access to them as well to be able to access their data and generate reports and it's always a bit painful to set up