#volodymyr_terminal-location
tropic thistleBOT
👋 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/1502337063964643521
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
final stone
StripeTerminal 2.23.3
sour sun
Can you also share the response to that request? We save the request, but not the response with GET requests on our side.
final stone
tropic thistleBOT
Hello @final stone, we have sent you a direct message, please check it at https://discord.com/channels/@me/1502339828031688960
- 🔗 The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
sour sun
When using curl my guess is you are using a secret key?
final stone
yes
sour sun
I believe the connection token is scoped to a specific location, so it would not list anything out side of that. So a single location response makes sense, i'm still trying to make sense of the empty response.
When creating the token, are you passing in a location scoped to the account? Potentially if a location was passed in that isn't directly on the account (say on another connected account) that could hypotethically result in an empty response.
final stone
Let me check how that works
sour sun
Yeah, so the token used for the request you provided, the creation request shows a location ID was passed in(when creating the token, not making the list call), that's not showing on your account, so that explains the empty response. You'd want to use the secret key if you need a comprehensive list of locations.
The ephermeral key is location scoped, so it's basically going to return only the location it's scoped to, and if the location passed in, isn't on the account, you'll get an empty response.
final stone
yes, seems location id from test env somehow appeared in prod DB
thank you for your time
sour sun
of course, happy to help.
final stone
I was wondering: if the key is location-scoped and we know an incorrect location was passed, which other APIs would be affected by this?
I checked, and it seems connecting to readers worked fine since they registered to the last known location. I also don’t see any errors from Payments either.
tropic thistleBOT
quick gust
final stone
The ephermeral key is location scoped, so it's basically going to return only the location it's scoped to
The issue I had with the Locations API was caused by this: "when creating the token, an incorrect location was passed", so the response was empty. So I was wondering, is this the only API that affected by this? It seems that all payment related APIs worked fine