HTTP 429 from brand new personal access token

Devices & Integrations
1

I have been bounced around many samsung support channels and it seems there is no support for the api so im posting here instead

when I create a brand new personal access token for my device (tumble dryer) and grant it every access type, as soon as I make a request on it, I get a HTTP 429: attempt 1 limit 1 response.

a day later and the response is just 401 unauthorized, despite still being an active registered api token with all scopes.

i believe this is an error in the api service/authentication. Does anyone have the same issue? Is there a fix? Do you know how/where I contact the helpdesk for the smartthings api team?

i spent additional cash to ensure I got a smart device that would work on my homeassistant setup and it doesnt work and theres no support in sight. The links on the personal access token page are dead. I dont want to return my device. Please send help!

thanks

2

There are recent changes to PAT’s. Check out this topic Changes To Personal Access Tokens (PAT)

3

New PATs are supposed to be more aggressively rate limited on the /devices endpoint but that doesn’t sound right. What were you doing with the PAT?

That sounds right. PATs have a 24 hour validity now.

I just tested a new PAT on an app that reads very many endpoints and I am not seeing anything unusual.

1 Like