#zerocool_api
tame needleBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- zerocool_terminal-reader, 4 days ago, 12 messages
cedar whaleBOT
đ 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/1242955957177422064
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sweet coral
I don't think that has GA'd yet. It's still a preview feature that will GA at a later date: https://docs.stripe.com/api/terminal/readers/object#terminal_reader_object-last_seen_at
onyx creek
Got it, it would be accessible if I used the CURL client just not the go client then?
sweet coral
I'm not sure if it's available at all. Usually a preview is just a plug for features that haven't been released yet, but let me see if I can find anything on it
onyx creek
Got it, thank you!
I just ran the CURL and it does return last_seen_at as unix time. It will be nice once this field is accessible through Go as well.
sweet coral
For sure. I'm happy to put that in as a feature request for the library. It has been in "preview" a long time, so I can't guarantee it will get any traction, but I'm happy to poke them anyway