#vktwenty6_api

1 messages Β· Page 1 of 1 (latest)

heady latchBOT
#

πŸ‘‹ 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/1463466517541949452

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

drowsy niche
#

There will be a req_xxx ID in the response headers for the failing request(s) – can you share one?

icy nimbus
#

Do I check this in n8n?

#

Because in stripe, I don't see the errors there.

#

Here's a look of the http request:

drowsy niche
icy nimbus
#

No worries. N8n just make it easier to enter the parameters, headers and body. Just look at the image and see if those are correct.

#

I'll check your link.

#

This one: req_v2J921iq8ytsp72WX

drowsy niche
icy nimbus
drowsy niche
#

I don't think that req_xxx ID maps to the request from the screenshot. It's for a different endpoint for starters: v2/core/accounts/acct_1S7Eo8Pqp7LhUWZ9

icy nimbus
#

ah I was just testing requesting some other data.

#

That's one of the tests that I did

#

Let me check for more

drowsy niche
#

Well the requests are returning different errors. I need to see the one you actually want help with

icy nimbus
#

I tried running the balance_transactions request, but it did not show up in the logs. In the n8n, I only see this error: Forbidden - perhaps check your credentials?
You cannot directly access a connected account controlled by a single platform with an org-level API key if the platform is not in an organization.

#

I'll try a different api

drowsy niche
#

Yeah I don't think this is supported today. You can't access a connected account via an org key today if the platform is not involved in the request

icy nimbus
#

Is my thinking correct about org api keys?

#

I can use it to access api data for all accounts?

drowsy niche
#

Yes, but not accounts which are controlled by a platform

icy nimbus
#

This is where I'm confused. How do we know which account is the platform?

#

Because based on my understanding, if we know the platform_id, we can access the connected accounts via org api keys, right?

#

also, I made sure that I added all acount under the organization.

drowsy niche
#

Can you at least give me an acct_xxx ID where this is failing? Flying blind here without a concrete example

icy nimbus
#

acct_1S7ErRLzA5WdxT6u

#

Here's the org id: org_6U0yyZ7CSQQhh4eIqmnIAcq

drowsy niche
#

I suspect it won't work on acct_1S7ErRLzA5WdxT6u as it was an account created by a Connect platform: acct_1PnPYnL7OgsfeTPW

icy nimbus
#

How did you find the platform: acct_1PnPYnL7OgsfeTPW?

drowsy niche
icy nimbus
#

I've read this documentation in stripe api:
In the preceding code example, replace {{CONTEXT}} with the relevant value:

For the standalone account, use acct_1aTnTtAAB0hHJ26p.
For the connected account, use a path that identifies both the platform and the connected account, following the format acct_1R3fqDP6919yCiFv/acct_1032D82eZvKYlo2C.

drowsy niche
icy nimbus
#

How? I was going crazy finding it, but I couldn't. haha

#

Can you tell me which account is it/

drowsy niche
#

The application/platform name is 'Booking Platform'. Can't really share any more details beyond that. I don't think it's an account of yours based on what I can see

icy nimbus
#

Yes, it's my company's account. Okay, I don't see that account in the list?

drowsy niche
#

What 'list'?

icy nimbus
#

I don't find it there.

#

The booking platform

#

I believe If I can add that platform to the organization, then this will solve my problem

drowsy niche
#

Then maybe you're not a user on the account? I don't know. Is the platform in the org?

icy nimbus
#

No, it's not there. My boss gave me access to his stripe account, and it has the list, but it doesn't contain the booking platofrm account

drowsy niche
#
Organization (org_6SD3oI0eSQemPzdmaGLJ5j6)
  β”œβ”€β”€ Platform account  (acct_1R3fqDP6919yCiFv)
  |   └── Connected account (acct_1032D82eZvKYlo2C)
  └── Standalone account (acct_1aTnTtAAB0hHJ26p)

That's your example really. Except the platform seemingly isn't in the org so it's failing

icy nimbus
#

Yes, you're right. Do you think the booking platform account is a separate stripe account?

drowsy niche
icy nimbus
#

I mean it's not in the login that I have.

#

In the account given to me, I can see all the list of accounts but not the booking platform account.

drowsy niche
#

As I said, then that login isn't a user on the account

icy nimbus
#

So that means, all connected accounts have a different login vs. the platform account

drowsy niche
#

I think you're missing something conceptually. Accounts can have multiple users (each with a Stripe login). They're not accessible by just one email address/user

#

If you can't see an account in your accounts list, and you're signed in to Stripe as abc@xyz.123 then the Stripe user for that email address is not a user on the account

#

You need to figure out that part, I can't help with that. Hopefully once you do that and move the platform account into the org, that unblocks your API requests