NetSuitePort_2019_1* version retirement

Deprecated, no dateSubscribe to NetSuite SuiteTalk APIShare

NetSuite SuiteTalk API deprecated /services/NetSuitePort_2019_1* without giving a shutdown date yet.

Calls it hits

/services/NetSuitePort_2019_1*

What to use instead of these calls

Move the integration to the 2025.2 SOAP endpoint (/services/NetSuitePort_2025_2, a client regenerated from its WSDL), or to SuiteTalk REST web services with OAuth 2.0. The FAQ's endpoint table shows 2019.1 disabled from the 2026.1 NetSuite release.

A newer WSDL means regenerating the SOAP client and checking every record mapping, and SOAP itself goes with 2028.2: the team may rather move to REST.

In NetSuite SuiteTalk API's words

How long will the unsupported endpoints still be available? With every NetSuite release the oldest unsupported endpoint is disabled. With the 2028.2 NetSuite release, all endpoints will be disabled, and SOAP-based integrations will stop working.

NetSuite SuiteTalk API, Announcement

Facts

API: NetSuite SuiteTalk API *.suitetalk.api.netsuite.com
Kind: Version retirement
Takes effect: No date given yet
Calls after that day: Fail
Source: Announcement
Last updated: November 4, 2026
Verified: November 6, 2026, against NetSuite SuiteTalk API's own pages

Questions

When does this change take effect?

NetSuite SuiteTalk API deprecated /services/NetSuitePort_2019_1* without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: NetSuite SuiteTalk API has not given a shutdown date yet.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub