Which action starts the API workflow to download a Stripe report?

Which action starts the API workflow to download a Stripe report?

• A. Create a reportrun for that day's data via the API
• B. Listen to the reporting.report_type.updated event.
• C. Stripe sends a reporting.report_run.succeeded webhook.
• D. Download your report via the link

Answer: (B)

This question is about how Stripe’s Reporting workflow is kicked off. The process is event-driven: a change to the report type configuration triggers the generation flow. When Stripe emits the report_type.updated event, it signals that a new or updated report type should initiate a new report run. From there, you monitor the run and, once it succeeds, you retrieve the generated report via the provided download link. Other options describe steps that occur later or are manual/notification actions rather than the starting trigger. Creating a reportrun can start a run, but the trigger being tested is the event indicating the report type was updated. A webhook about a successful run is a status notification, not the initiation. Downloading via a link is the final action after the run is ready, not what starts the workflow.

This question is about how Stripe’s Reporting workflow is kicked off. The process is event-driven: a change to the report type configuration triggers the generation flow. When Stripe emits the report_type.updated event, it signals that a new or updated report type should initiate a new report run. From there, you monitor the run and, once it succeeds, you retrieve the generated report via the provided download link.

Other options describe steps that occur later or are manual/notification actions rather than the starting trigger. Creating a reportrun can start a run, but the trigger being tested is the event indicating the report type was updated. A webhook about a successful run is a status notification, not the initiation. Downloading via a link is the final action after the run is ready, not what starts the workflow.