cryshado_api

[gaunt wing]

👋 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.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 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/1379572249022955732

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• cryshado_api, 5 days ago, 32 messages

[fluid hinge]

Hi there 👋
Let me take a look at this

[normal robin]

Also, I have another question about the Connect integration. When making API requests on behalf of connected accounts, are rate limits applied separately to each connected account, or do they count toward the platform’s overall api rate limit?

[fluid hinge]

Each connected account has their own API rate limit allocation (500 requests per transaction).
https://docs.stripe.com/rate-limits#api-read-request-allocations

I just talked to my colleague about the service agrrement question. The Account V2 API is still a beta, so this part doesn't exist at all currently in V2.

One reason is because V2 is quite limited currenlty anyway to specific features like global payouts etc.

[normal robin]

This question originally came up in the context of us developing our own dashboard. The question was whether we should store all the data received from webhooks related to our connected accounts, or whether we could fetch some of it from the API on behalf of the connected account (for instance, when a user wants to view more detailed information about a transaction).

As I understand it, given the per transaction based rate limit, the first approach is preferable. We should primarily rely on webhook data and only make read requests to the API in cases where we need to index data that we hadn’t previously stored in our system.

[normal robin]

Does that sound like a correct approach when building our own dashboard?

[normal robin]

By the way, is there an estimated date for when V2 will be out of beta? We're currently building a new service using V2, assuming it's the near future and that it makes more sense to adopt V2 now rather than migrate later.

[fluid hinge]

If you are creating your own dashboard, then to me it would make more sense to store your own data. You can update the data based on your integration processes and for things outside your integration you can use webhook event you receive to update your data.

When/If the V2 will get out of beta is something only the product team will know. In this case I recommend reaching out to our support team -> https://support.stripe.com/?contact=true

[normal robin]

Ok, got it, thanks

[fluid hinge]

No problem, You are most welcome