#donklitschko_api

1 messages ยท Page 1 of 1 (latest)

lofty minnowBOT
#

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

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

stoic steppeBOT
fierce hedge
#

Hello

#

Do you have a location ID you can share where you see this?

wet copper
#

tml_Fgtn9QyKxcIR8K

fierce hedge
#

Looking

wet copper
#

thanks

#

this is the full response:
{
"id": "tml_Fgtn9QyKxcIR8K",
"object": "terminal.location",
"address": {
"city": "London",
"country": "GB",
"line1": "Unit 2, 1 Tapper Walk",
"line2": "",
"postal_code": "N1C 4AQ",
"state": "London"
},
"display_name": "Blink Payment",
"livemode": false,
"metadata": []
}

fierce hedge
#

I do see the relevant logs

wet copper
#

Ah I see thanks

fierce hedge
#

๐Ÿ‘

wet copper
#

But why is the most recent one on the 26th march>

#

If we called the API today?

fierce hedge
#

Can you run a fresh test? And you believe the ID you shared above was created today?

#

No I do see logs for today

#

I don't see any from March 26th

wet copper
fierce hedge
#

Yeah I think you are looking at the wrong account

#

At least not the account related to the ID you shared above

#

Do you have access to multiple Stripe accounts?

wet copper
#

I do, but I'm positive this was created using the secret key from this account

fierce hedge
#

Yeah I'm skeptical of that, sorry. For the ID you shared I can see logs from today for Location creation and then the previous ones are from February.

#

I'd recommend running another test and looking at the request ID that is in the header of the response

#

And then search that request ID in your Dashboard

wet copper
#

Ok I'll have a look

#

I'll let you know the result - thanks for the help