SmartThings charging for API access as of December 15th. 2026

Below is an email I received from SmartThings this morning. I haven’t seen it mentioned on here yet but I think it is of interest to the home automation community at large:


You’re receiving this email because you have a Personal Access Token (PAT) registered on your SmartThings account. We’re writing to let you know about upcoming changes that affect PATs.

What’s Changing

As part of our ongoing efforts to scale and maintain the SmartThings API, we are updating our legacy PAT policy.

Expiration Date: Your PAT(s) will expire on December 15, 2026.
Impact: Any scripts, personal dashboards, or third-party connections relying on this PAT will stop working after December 15, 2026, unless migrated to a paid supported API plan.
New Developer & Business Plans

PATs are intended for short-term development access to the SmartThings API. To support ongoing continued access to the SmartThings API, we recommend using OAuth through our SmartThings API Developer or Business plans.

On November 4, 2026, we released updated API plans for both business partners and individual developers.

Next Steps

To learn about how to continue operation of your integrations:

For Individual Developers: Visit the SmartThings Developer Center starting November 4, 2026 to sign up for the Developer Plan to maintain your current integrations and/or to build a new API Access App.

Availability for the individual Developer Plan: Note that the SmartThings API Developer Plan will be limited to certain countries upon launch. Country availability can be found in the FAQs on our SmartThings API page and in the Developer Center Console.

The December 15th date applies to all affected PATs including those owned by developers in countries where the Developer Plan is not available. If you have questions about your situation, contact developer support.

For Business Partners: To discuss pricing tailored to your usage, please contact us at [email protected].
Plan details, pricing, and availability are subject to change.

For full details, please read our announcement on the SmartThings Blog. We will continue to share additional updates regarding token management policies as they become available.

Thank you for building with SmartThings.

Best regards,
The Samsung SmartThings Team

Yes it has. Many times. Use the magnifier and search on SmartThings, enjoy report after report for the last couple of months. You simple not seeing because of the amount WTH submissions, it is getting buried.

Yeah…I figured that out. I had been searching for “smarthings” (with one ‘t’). I’m dumb, it’ll be ok :slight_smile:

I maintain a Home Assistant custom integration for Samsung TVs and The Frame (ha-samsungtv-smart, a maintained fork of ollo69’s), so I wanted to add a constructive note for anyone here who owns a Samsung TV specifically — as distinct from SmartThings appliances.

I share the concern about the move to a paid SmartThings API. From the communication Samsung has sent out, the paid plans go live in early November 2026, and API keys/tokens — OAuth and personal access tokens alike — stop working in mid-December without a plan.

The good news for TV owners: a Samsung TV doesn’t actually need SmartThings for most of what people automate. The integration talks to the TV directly on your LAN:

  • Power on/off (Wake-on-LAN + the TV’s own WebSocket)
  • Source switching, app launch and remote keys
  • The Frame’s Art Mode — upload, matte, slideshow, brightness — over the local art channel
  • Local “IP Control” for picture modes, expert calibration and speaker output
  • Quick settings (picture/sound mode, game mode…) read and set locally

SmartThings is optional here: connecting it adds a few extras (some state reporting, extra sound modes on certain models), but the core control is fully local and keeps working with no cloud key at all.

So if you own a Frame or other Samsung TV and are worried about losing control in December, running this integration in local-only mode is a path that doesn’t depend on the paid API. It won’t help with fridges, washers or other SmartThings-only appliances — that’s a separate problem, and the questions put to Samsung above are the right ones — but for the TVs at least, there’s a way to stay fully local.

Repo: GitHub - TheFab21/ha-samsungtv-smart: Home Assistant custom integration for Samsung Smart TVs (Tizen) and The Frame — Art Mode, local IP Control, SmartThings/OAuth2. A maintained fork of ollo69/ha-samsungtv-smart. · GitHub (also on HACS). Happy to answer setup questions.