anonymous-developer_webhooks

[unique peak]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question. Thank you for your patience!

⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1214247733062406154

📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.

[fiery idol]

Hello

You should be able to specify both interval_start and interval_end here

[cosmic tapir]

Not on this report

[fiery idol]

Hmm does it error?

[cosmic tapir]

yes

[fiery idol]

Can you share the request ID?

[cosmic tapir]

Here's a report run succeeded event frr_1Oq9ocGuzTr2QwdMG2tGFVR4

When your dashboard makes its call for the same report this is what the POST body looks lilke, you'll notice no interval_start

{
  "id": "frr_1Oqe2nGuzTr2QwdMK4oW0JJn",
  "object": "reporting.report_run",
  "created": 1709568433,
  "error": null,
  "livemode": true,
  "parameters": {
    "interval_end": 1709272800
  },
  "report_type": "ending_balance_reconciliation.summary.1",
  "reporting_query": {
    "id": "qry_1Oqe2mGuzTr2QwdM46S7pNr1",
    "object": "query",
    "completed": null,
    "created": 1709568432,
    "description": null,
    "status": "running",
    "user": "usr_NhUDrOFCkLhSaB"
  },
  "result": null,
  "status": "pending",
  "succeeded_at": null
}

What I have noticed is if in the dashbaord I query for a single day range, it requests an interval end of 6am UTC on the following day. But I don't know what the logic is to t that or whether that's what I am also supposed to be doing

[fiery idol]

Ah okay I see

Thanks for clarifying, let me check

[cosmic tapir]

Right now I am simply passively accepting reports which come in two times a day, and the data looks valid, but I cannot reconcile what I'm getting with what I get for a given day via your dashboard

[fiery idol]

Okay so the way the ending_balance_reconciliation.summary.1 works is that it is looking at your entire balance summary up until a certain point. So yeah it wouldn't make sense eto have an interval_start here -- the interval start is always the beginning of your account activity.

The fact that the Dashboard sets it as 6:00 UTC is likely because of the timezone set in your Dashboard

That is likely 12am local

So up to you if you want to reconcile this way by setting 06:00 UTC

[cosmic tapir]

I don't think this information can be correct based on the number I"m seeing, I am definitely not getting back numbers from the beginning of account activity

For example the total does not continually go up if your query successive days

Good point about the timezone in the dash, let me change that and see if I can get a match

[fiery idol]

Okay okay silly me. The only required param is interval_end but you can still use inteval_start to isolate to one day using the API

[cosmic tapir]

Hey i think that does reconcile it, we may be good, thanks

[fiery idol]

It should not error when using this.

If it does, I'd like to see that request ID

[cosmic tapir]

It does error if you try to provide that argument via the API

[fiery idol]

Really?

Can you share the request ID? I can also test.

[cosmic tapir]

Yes. I coudl try to find the record it's been a weak or two since I learned this

[fiery idol]

But I really don't think it should

[cosmic tapir]

I didn't either ha. But I think my issue is resolved now, so it's not a concern at this point

[fiery idol]

Okay sounds good. I'll test it out myself so I know going forward 🙂

[cosmic tapir]

I think you'll find this is the case. Thanks for you help

[fiery idol]

👍