#adam_connect-max-externalaccounts

1 messages ยท Page 1 of 1 (latest)

rough thornBOT
#

๐Ÿ‘‹ 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/1281257702990942281

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

undone bough
#

Can you share the request id where you're getting this error?

quartz grove
#

The logs are not showing API requests I am making ??

undone bough
#

If you are making this request on a connect account, then you'll need to filter the logs by connect requests

#

There should be a toggle for that

quartz grove
#

Done that - and it's still now showing any GET requests, net alone POST ones, for over 2 hours

undone bough
#

Are you filtering by live requests?

quartz grove
#

I don't believe so - the API key shown, on the last log I see, shows as "sk_test....."

undone bough
#

Do you have multiple accounts? Is it possible you're logged into the wrong platform?

quartz grove
#

Don't think it's that either. I can see requests I made earlier today with the same API key.

#

If it helps the connect account ID is acct_1Ot5zER56R4XTNAp

undone bough
#

Yeah does look like you have 200 external accounts attached

#

So the error makes sense

#

By default it will only return 10, so you'd need to paginate

quartz grove
undone bough
#

I'd need the request id for where you list them and only 1 is returned to verify

#

Dashboard I assume only shows the default external account (of which there can only be one)

quartz grove
#

Ah, only showing the default one on Dashboard kind of makes sense .... especially if the account has 100s of them ๐Ÿ™‚

rough thornBOT
quartz grove
#

Still not showing the request in the logs.

eager locust
#

Hi ๐Ÿ‘‹

I'm stepping in as my colleague needed to step out

#

can you share a request ID

quartz grove
#

If I do "stripe external_accounts acct_1Ot5zER56R4XTNAp" in the Dashboard shell that also shows just 1 account

eager locust
#

We really don't know much about how the Dashboard functions here. We can only give advice on using the APIs

quartz grove
eager locust
#

How are you making requests?

quartz grove
#

Ah, they are showing up now; but only if I select "Platform account" un the filers

#

An example request ID is req_oUyK0ZzBhbioXm

eager locust
#

Looking at this request, it looks like you are making this API request using some sort of 3rd party software, not a native Stripe SDK.

quartz grove
#

Correct - it'll either by made from either our own application or via Postman

#

We have not changed how we make our calls to your API; we just know that recently (within a few days) they don't appear to be returning the same data

eager locust
#

In your initial message you mentioned

We are testing the POST external_accounts endpoint

But the request you shared was a GET request. Are there other behaviors you are not seeing?

quartz grove
#

The logs aren't even showing me the response that Stripe sent bacl

eager locust
#

We have never shown the results of GET requests in our logs.

#

It's something I've run into ever since I started working at Stripe so I'm pretty sure that's not a new behavior

quartz grove
#

OK.

The request_id for the POST is req_Z4UUNZHPXbBhG6 which states "Account acct_1Ot5zER56R4XTNAp already has the maximum 200 external accounts attached.". However, a GET request [ req_VHEaKHiZOW2xdp ] only returns 1 external account.

We have code which regularly deletes "old" external accounts. It does this by making a GET call and then looping round the external_accounts, returned, making a DELETE call for each one. However this code no longer does anything as the GET doesn't return the 200+ accounts

eager locust
#

Looking in our logs, I am seeing records_returned=9 for the GEt request. Since you aren't specifying a limit in your request, our API will default to returning 10 object.

quartz grove
#

And yet it is only showing 1. The entire response JSON we get back from https://api.stripe.com/v1/accounts/acct_1Ot5zER56R4XTNAp/external_accounts is:

{
"object": "list",
"data": [
{
"id": "ba_1PumcZR56R4XTNApKsfbWH1f",
"object": "bank_account",
"account": "acct_1Ot5zER56R4XTNAp",
"account_holder_name": "",
"account_holder_type": "company",
"account_type": null,
"available_payout_methods": [
"standard"
],
"bank_name": "HSBC BANK PLC",
"country": "GB",
"currency": "gbp",
"default_for_currency": true,
"financial_account": null,
"fingerprint": "r9cdu7o02NKfjfmJ",
"future_requirements": {
"currently_due": [],
"errors": [],
"past_due": [],
"pending_verification": []
},
"last4": "2345",
"metadata": {},
"requirements": {
"currently_due": [],
"errors": [],
"past_due": [],
"pending_verification": []
},
"routing_number": "40-05-15",
"status": "new"
}
],
"has_more": false,
"url": "/v1/accounts/acct_1Ot5zER56R4XTNAp/external_accounts"
}

#

regardless of what we set as the limit value

eager locust
#

Can you share a recent request you made to delete one of the accounts?

quartz grove
#

That's the problem we haven't sent any recently (we only do the clean up about once a month).

To expand on how our code works, we make a GET call and then DELETE all external_accounts where "default_for_currency" IS NOT true. But that is the only external_account the GET request is returning so our code doesn't actually make any DELETE calls at all.

This then causes the "maximum 200" problem when we then try and make a POST

eager locust
#

Okay this is rather confusing so I've reached out to some colleagues who are helping me investigate this. We are attempting to reproduce the error.

eager locust
#

Okay it looks like there was a change in our code recently that might have impacted how this API behaves. We are raising this issue internally

quartz grove
#

OK

eager locust
#

Okay we have team members actively working on a fix for this. I can't guarantee when it will be deployed but it should be fixed today.

quartz grove
#

Excellent. That's good to hear

eager locust
#

Thank you for your patience on reporting this.

quartz grove
#

Not a problem

eager locust
#

I'm going to close this thread but I see we have a fix under review and it should be deployed later today. If you encounter this issue again please feel free to reach out us.