#mattnenterprise - connect + reports

1 messages ยท Page 1 of 1 (latest)

heavy stag
dusk jay
#

Give me a minute. Gonna get one.

short slate
#

Hi ๐Ÿ‘‹ I'm stepping in for @heavy stag I can take a look once you have these request IDs.

dusk jay
#

Example request ID is req_FvhHpvkEuOkk0J

short slate
#

The status of this report run is pending. Meaning the report has not been generated yet.

dusk jay
#

Report frr_1LdbD234h7gmV08v6ABMs6CX ?

short slate
#

Completed 62 minutes ago

#

You should be able to download it using the Files API

dusk jay
#

Yes, but it only has the headers.

#

If I download the same report in the UI it has data.

short slate
#

How are you retrieving the file?

dusk jay
dusk jay
#

Is there another way it is suppose to be done ? The API returns a file size of only 170 bytes.

short slate
#

How do you integrate with the API in general?

#

If you use any of our client libraries (.NET, Go, Python, etc.) you can use them to retrieve the file: v

dusk jay
#

I'm just using curl. We generally use the https://github.com/beam-community/stripity_stripe library as we use elixir, but it doesn't yet have support for reporting. I'm just trying to validate I can get this information from the API before writing any Elixir code. I don't understand why we can't use curl for a testing ground as it is just an HTTP API ?

GitHub

An Elixir Library for Stripe. Contribute to beam-community/stripity_stripe development by creating an account on GitHub.

short slate
#

I think you should be able to. I'm just trying to eliminate different reasons the resulting data payload is not what you want

dusk jay
#

The UI works fine and returns data for the same report. Just not sure why only the CSV headers are returned through the reporting API file. Trying to figure out if I need to pass something else to the API or if it isn't possible to run reports for express connect accounts through the API.

short slate
#

Oh wait....I think the issue is you would need to specify the Express Account ID header in the CURL request.

dusk jay
#

The CURL requests were run with the Stripe-Account header.

#

Were you able to look into the request ID or report ID I gave earlier to see if the parameters and headers look right for running the report ?

short slate
#

The request looks good. The API would have returned an error otherwise

#

The report record shows as having completed compiling the data.

dusk jay
#

It just has no data in the actual file except the CSV headers. I know the account has data because I downloaded the same report in the UI and it has actual itemized transaction data in it.

floral mountain
#

๐Ÿ‘‹ Hopping in since @short slate has to head out

#

let me just catch up

#

Are you using Express Accounts + Destination charges?

dusk jay
#

Yes.

floral mountain
#

Gotcha - then I think you shouldn't be using the Stripe-Account header and you want a slightly different report type. The Stripe-Account header is needed when you're doing direct charges that live directly on the connected account. Since you're doing destination, those charges still technically live on the Platform (so you don't need the Stripe-Account header to get the report). I think you also want one of the connected_account_payouts.itemized.* reports instead (https://stripe.com/docs/reports/report-types#schema-connected-account-payouts-itemized-3)

dusk jay
#

I'm giving that a try.

dusk jay
#

The report type I was looking for turned out to be connected_account_payout_reconciliation.itemized.5. Thank you!