Three dated deadlines now — and one of them arrives quietly, a release before the date everyone's watching.
Token-Based Authentication, SOAP web services, and SuiteScript 1.0/2.0/2.x are all being retired on Oracle's published schedule now. This page states the sourcing for each, the date I last checked it, and doesn't inflate any of it.
All three now have published dates.
Oracle's dates: 2027.1, then 2028.1. From 2027.1 you cannot create new integrations that use TBA — SOAP, REST and RESTlets alike. At 2028.1 support ends for the ones you already have, and they stop authenticating. SuiteAnalytics Connect (ODBC/JDBC) is excepted.
Oracle's dates: 2027.1, 2027.2, then 2028.2. No new SOAP integrations from 2027.1. From 2027.2 only the 2025.2 endpoint remains supported. At 2028.2 all endpoints are disabled and every remaining SOAP integration stops working. This is a removal, not a deprecation.
Oracle's dates: 2026.2, 2027.1, 2028.1, then 2028.2. Warnings begin 2026.2. 1.0 enters critical-only support 2027.1. At 2028.1, scripts annotated 2.0 or 2.x silently start executing as 2.1 — no redeploy needed. At 2028.2 every script must be on 2.1 or it stops working.
Until this month, SuiteScript 1.0 was the exception — frozen, but with nothing scheduled. Oracle has since attached a date to it too. That doesn't make the other two less urgent; TBA and SOAP still deserve attention first if your account is exposed on either.
Four phrases get used interchangeably in this conversation, and they mean very different things. Sorting them out is most of the value of this page.
A vendor who slides from the first of those to the fourth inside a single sentence is worth reading carefully.
The honest answer is that nobody can tell you without looking — and most accounts have never looked.
For integrations, what you need is the login audit trail rather than the configuration screens: what actually authenticated, by which method, and when. Configuration tells you what exists; the audit trail tells you what's alive. An account with forty integration records where six have authenticated in ninety days has a completely different problem from one where all forty are live.
Remediating TBA and SOAP isn't something I offer yet — it's on my list to build, and if it's what you actually need, say so. What people ask for is how I decide what gets built next. Meanwhile the queries aren't secret, and if this helps you scope your own work, that's a better outcome than you not knowing.
Your SuiteScript estate is the part I do work on. Same blindness, different question: which scripts are yours versus a vendor's, which are actually deployed, which use APIs with no 2.1 equivalent, and which would genuinely be hard to move. That's what the catalog answers, and it's where every engagement starts.
One page each, with the source documents linked.
17 September 2026. TBA and SOAP against Oracle's NetSuite Help Center, last checked 25 August 2026. SuiteScript 1.0/2.0/2.x against a LinkedIn post from RSM and BrokenRubik's writeup citing Oracle's SuiteAnswers article 1047412 (last updated 16 September 2026) — I haven't read that article directly, since it sits behind a NetSuite login, so treat that date as corroborated secondhand sourcing until I can confirm it firsthand.
I re-check this at every NetSuite release and change the date above whether or not anything moved. If you find something here that is out of date or wrong, tell me and I will fix it.
The claim I previously left out — that NetSuite 2026.2 adds a warning banner for SuiteScript 1.0 — is now corroborated by two independent sources and is stated as fact above.
Every custom script cataloged and scored for complexity and risk, with the vendor-owned and unconvertible ones named and excluded. Engagements start at $2,000.
See what it costs