#pocketvendor_api
last heraldBOT
👋 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/1486042116202299503
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- pocket_terminal-aod, 23 hours ago, 6 messages
crisp talon
To add to the above, I feel like I'm missing a deploy group or something in this process to get deploys to both S700 and S710 (despite the Dashboard UI showing deploys worked).
sly moat
hi there. I"ll be with you in just a moment
crisp talon
No worries, take your time. No rush on my side.
I have a connected account, with platform controls enabled (acct_1TEUgSHdz1HJyaFS), that has registered their S710 to a location but the install is not happening.
wet sorrel
hello! jumping in to help out with this, gimme just a bit to catch up
to be completely transparent, our knowledge of S710 behavior on the team is still a little fresh, and our knowledge of dashboard exclusive behavior is a little iffy - i haven't really worked with the dashboard deployment tool yet and i doubt anyone on my team has. let me take some quick stabs at triaging the issue and i'll see if i can't get it figured out, but we might need to transition this to an email case so we can dig in a bit more
crisp talon
No worries, but that helps me cope with how I feel like I'm flying blind here too 🙂
wet sorrel
any chance you have the terminal device ID handy?
https://docs.stripe.com/api/terminal/readers/object#terminal_reader_object-id
crisp talon
If it's at all helpful, I had created all of my deploy groups and everything via direct command line api calls long before it was available in the Dashboard
tmr_GbAjgz6lON7KFh on location tml_Gb9QwQSAmv37MF
wet sorrel
also do you mind if i send you a request to log into your account? you'll get a DM asking for your approval
wet sorrel
yep! i think i found the ID, is this it? acct_14vBEUJM1OE6Um6K
crisp talon
Yes that's my platform
last heraldBOT
Hello @crisp talon, we have sent you a direct message, please check it at https://discord.com/channels/@me/1486046469688660029
- 🔗 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.
crisp talon
Approved!
wet sorrel
when you say "The number of locations always shows as 0." can you tell me where you're seeing that? a link to the specific dashboard page and a screenshot would be amazing
also is this an issue with all S710s? or just one?
stepping away for a minute or two but i'll be back
crisp talon
So here:
When I click the "Update" links under the "Deployed Groups" section in the right column
wet sorrel
as a quick lil sanity check can you try running list readers on that connected account and let me know if you get the reader back?
https://docs.stripe.com/api/terminal/readers/list
crisp talon
{
"object": "list",
"data": [
{
"id": "tmr_GbAjgz6lON7KFh",
"object": "terminal.reader",
"action": null,
"device_deploy_group": "",
"device_sw_version": "2.40.1.0",
"device_type": "stripe_s710",
"ip_address": "192.168.3.83",
"label": "super-building-traveler",
"last_seen_at": 1774372263440,
"livemode": true,
"location": "tml_Gb9QwQSAmv37MF",
"metadata": {},
"serial_number": "STR71Z1G549000498",
"software": {
"version": "Firmware 2.40.1.0 - ROM BBPOS_WISEPOS_WTH13.2.1.21-user"
},
"status": "online"
},
{
"id": "tmr_Gb9bzQphW6yBnX",
"object": "terminal.reader",
"action": null,
"device_deploy_group": "",
"device_sw_version": "2.40.1.0",
"device_type": "stripe_s710",
"ip_address": "192.168.2.114",
"label": "dull-jambul-wood",
"last_seen_at": 1774372282939,
"livemode": true,
"location": "tml_Gb9QwQSAmv37MF",
"metadata": {},
"serial_number": "STR71Z1G549000505",
"software": {
"version": "Firmware 2.40.1.0 - ROM BBPOS_WISEPOS_WTH13.2.1.21-user"
},
"status": "online"
},
{
"id": "tmr_Gb9QyA2E67htML",
"object": "terminal.reader",
"action": null,
"device_deploy_group": "",
"device_sw_version": "2.01.00.38-SZZZ_Prod_US_v12-481001",
"device_type": "stripe_m2",
"ip_address": "",
"label": "Livemode Reader",
"last_seen_at": 1774358872078,
"livemode": true,
"location": "tml_Gb9QwQSAmv37MF",
"metadata": {},
"serial_number": "STRM2D507022196",
"software": {
"version": "Firmware 2.01.00.38-SZZZ_Prod_US_v12-481001 - ROM "
},
"status": "offline"
}
],
"has_more": false,
"url": "/v1/terminal/readers"
}
wet sorrel
ok yeah it looks like it's specific to this endpoint which the dashboard is calling: /v1/terminal/device_deploy_groups
last heraldBOT
wet sorrel
unfortunately our team doesn't really know much about that API or this deployment flow since it's more specific to live mode and our team generally focuses more on development and our SDKs, so i think you'll have better luck chatting with our support team here (using the Contact support button)
you have to navigate past a chat bot to get to a person but if you give it a summary of your problem and bother it enough about talking to a person it should let you through
crisp talon
Haha, I love your honesty
And yes I'm aware - been working on apps on the Stripe api since 2013!
Thanks for trying. Much appreciated
wet sorrel
yep! best of luck 🙂
crisp talon
I was able to get the locations assigned from 0 to 1 using this (the connected accounts location and account ID)
curl -s https://api.stripe.com/v1/terminal/locations/tml_Gb9QwQSAmv37MF
-u "$STRIPE_API_KEY:"
-H "Stripe-Account: acct_1TEUgSHdz1HJyaFS"
-H "Stripe-Version: 2019-11-05;terminal_deploy_api_beta=v1"
-d "device_deploy_groups[stripe_s710]=tmddg_GazSRw43i9avEJ"
The S700 skips this step because its deploy group is is_default: true. Is it possible to flip the is_default to true on the new deploy group as well? That way new S710 locations would auto-deploy like the S700s.
wet sorrel
oops sorry, i missed your message! i double checked and it looks like we do have an API for interacting with deploys, but it's private preview which we can't support here on the server, and from skimming the API i am not seeing a way to update the default state of deploys
it's possible that there is a way to do it via the dashboard, but the support team will know more about that than us
crisp talon
Yeah I have access to the private api "Stripe-Version: 2019-11-05;terminal_deploy_api_beta=v1", which is how I was able to get this far!