#christina-sigma-connect

1 messages · Page 1 of 1 (latest)

misty ventureBOT
civic pendant
#

@slow cloak not that I know of, you'd build your own integration to access this

#

christina-sigma-connect

slow cloak
#

Is there documentation for building out the integration to access this?

civic pendant
#

I don't really get the question. What part is confusing you exactly?

slow cloak
#

The integration piece that you are referring to

#

Is this in the API documentation?

#

Can we share out the reports via the API?

civic pendant
#

I'm really sorry I must be missing something obvious. The way you framed your question it looked like you already have a full API integration to run your own custom Sigma reports, is that not the case?

slow cloak
#

Yes, we do

#

So, we could share them out then.

#

[1:37 PM] Osman Mohammad

Run a report from the API | Stripe Documentation

Run a report from the API

Access Stripe's financial reports programmatically to automate your reconciliation workflow.

#

Is that what we could use?

civic pendant
#

not sure what that quote is from or what the context is, there's 3 sentences, two seem like a doc link with no context 😅

slow cloak
#

I found the documentation for running a report from the API

#

Recommended integration pattern for automated reporting

Prerequisite: configure a webhook that explicitly selects to receive reporting.report_type.updated events; webhooks that listen for ‘all events’ won’t receive them.

A reporting.report_type.updated webhook is sent as soon as a new day’s data is available for a given report type. The payload includes the updated ReportType object. You’ll typically receive 20-30 webhooks each day, two for each report type. (Different users are eligible for different reports.)
Upon receiving the reporting.report_type.updated webhook for the desired report type and range of data availability, create a report run. The response contains a new ReportRun object, initialized with status=pending.
When the run completes, a reporting.report_run.succeeded webhook is sent. This webhook includes the nested field result.url. (As mentioned above, in the rare case of a failure, we’ll send a reporting.report_run.failed event instead.)
Access the file contents at result.url, using your API key.

#

Thank you. We will follow this.