#laxmanpula-report-events

1 messages · Page 1 of 1 (latest)

waxen crown
#

Is the issue that the events are being created/generated for the connect account and are just not reaching your webhook, or that the events are not being created at all?

severe smelt
#

events are not generated at all

#

this is what I see on stripe dashboard

waxen crown
#

Do you have an example of a reporting run on the connect account that we can take a look at?

severe smelt
#

I assume the report run will be the result of event reporting.report_type.updated?

#

is there way I can verify if the reporting.report_type.updated
event is already triggered for my connect account from the dashboard?

spark stag
#

Hello! I'm taking over for karbi. How are you triggering the report runs? Can you give me the request ID of a report run request you're making?

severe smelt
#

Thank you Rubeus. No events are triggered for the connect webhook we setup.

#

we call Report run api once we receive the evtn for reporting.report_type.updated

spark stag
#

Are you using Standard, Express, or Custom accounts?

severe smelt
#

Standard connect account

spark stag
#

How are you running the reports?

severe smelt
#

once we receive the webhook event for reporting.report_type.updated, we call the reporting api.

#

ReportRun.create(report_type=report_type, parameters=parameters)

spark stag
severe smelt
#

we never called ReportRun API. we will call this api when we reciev the reporting.report_type.updated event. But the issue is reporting.report_type.updated events was never triggered by Stripe for the webhook.

#

when I navigated to my webhook .. I see this.

spark stag
#

Sorry, I don't think I quite understand. Can you give me the account ID of the connected account where you're expecting to receive these events?

severe smelt
#

sure.

spark stag
#

Looking, hang on...

severe smelt
#

sure. thank you.

spark stag
#

Ah, okay, so you don't have any webhook endpoints on the connected account itself listening for reporting.report_type.updated, so we're not going to generate those events.

#

Can you clairify if you want to call the reports API from the connected account or via your platform account?

severe smelt
#

ReportRun.create(report_type=report_type, parameters=parameters) the parameters will have connected_account

#

but I am confused.. we have the connect account setup and listening for the events

spark stag
#

That's a Connect webhook endpoint though. Typically with Connect you would run reports on your platform account that include connected account data. That process does not involve report events on the connected accounts at all, only on your platform account.

#

In other words, you would use Connect-specific reports on your platform rather than use reporting events/APIs on your connected accounts.

severe smelt
#

just to my understanding, we get the connect events as well on our platform webhook?

#

hence we can run the report?

#

connected_account_payout_reconciliation.itemized.4 this is the report we are expecting to run

#

on connected account.

spark stag
#

No, the connect events aren't involved at all. You would set up an account webhook endpoint to listen for these events on your platform.

#

You don't run that report on your connected account, you run it on your platform.

severe smelt
#

yeah.. this webhook is setup on platform account only.

spark stag
#

Right, it's a webhook endpoint on your platform, but it's a Connect webhook endpoint.

#

It should not be a Connect webhook endpoint, it should be an Account webhook endpoint.

severe smelt
#

but I have other connect end point to get charge related evetns, that does get events received.

#

for the same connect account

#

issue is only with reporting events

spark stag
#

Right, that's because reports work different.

#

Sorry, I think we're talking past each other. Let me try and explain a different way...

#

When using Connect and you're the platform, you do not run reports on your connected accounts. You also do not listen for report events from your connected accounts using a Connect webhook endpoint. None of that happens.

#

What does is happen is your platform has access to Connect-specific reports on your platform account. One example is the one you mentioned earlier: connected_account_payout_reconciliation.itemized.4. That report exists on your platform account, the events associated with exist on your platform account, and the API calls you make related to it are made on your platform account.

#

Does that make sense?

severe smelt
#

Yes.

#

thank you for explaining. So, if I how do i generate report connected_account_payout_reconciliation.itemized.4 for my connect account using Report API.

spark stag
#

That's explained in detail in the reporting docs I linked above. Do you have a specific question about the docs there?

severe smelt
#

Thank you Rubeus.

#

I am good for now. I will reachout if I have any questions.