Which webhook is sent when a Stripe report run completes successfully?

Which webhook is sent when a Stripe report run completes successfully?

• A. reporting.report_type.updated
• B. reporting.report_run.succeeded
• C. reporting.report_run.started
• D. reporting.report_created

Answer: (B)

Stripe notifies you about the lifecycle of long-running tasks like generating a report through webhook events. When a report run finishes and everything went well, the event you want to listen for is reporting.report_run.succeeded. That signal confirms the job has completed successfully and the resulting file is ready to use. The other events reflect different moments in the lifecycle: reporting.report_run.started happens at the start of the run, reporting.report_created is about the run object being created, and reporting.report_type.updated relates to changes in the configuration of the report type rather than a specific run’s completion. So, if you’re waiting for a successfully finished report, the succeeded event is the one to hook into.

Stripe notifies you about the lifecycle of long-running tasks like generating a report through webhook events. When a report run finishes and everything went well, the event you want to listen for is reporting.report_run.succeeded. That signal confirms the job has completed successfully and the resulting file is ready to use. The other events reflect different moments in the lifecycle: reporting.report_run.started happens at the start of the run, reporting.report_created is about the run object being created, and reporting.report_type.updated relates to changes in the configuration of the report type rather than a specific run’s completion. So, if you’re waiting for a successfully finished report, the succeeded event is the one to hook into.