#vmehtawhq_api
warm quartzBOT
đ 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/1267451143550799966
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
nimble sky
I use a list filter account param to get account's PMCs.
stiff path
pmc_1PhruGQXRwZVQFn0un9NUJUq belongs to a different account (acct_1L86DUQXRwZVQFn0) to the one you're using to make the API request
warm quartzBOT
nimble sky
Right, so I get a 404 using my API key.
stiff path
Yes, because you're using the API key that belongs to the wrong account (acct_1EaPCrHFzwE4pTge)
nimble sky
But how am I able to list the PMCs if I am using a platform level key?
stiff path
acct_1L86DUQXRwZVQFn0 is an Express connected account, so you likely need to pass the Stripe-Account header to 'authenticate' as the account: https://docs.stripe.com/connect/authentication
nimble sky
Is this a new thing? I am not sure if I have used it anywhere else
stiff path
Nope, has always worked this way in Connect contexts. If you want to read/write on behalf of a connected account as the platform you must pass the Stripe-Account header
nimble sky
Does onBehalfOf works the same way?
rotund lance
No, onBehalfOf only specifies the settlement merchant for the payment. But the request is still made on the Platform account.
Stripe-Account header actually makes the call on the connected account.
nimble sky
Cool, thank you!
rotund lance
Happy to help.