With Webservice v9 we’re introducing a major modernization of the platform.
Legacy protocols have been removed and the REST API structure has been simplified to make integrations cleaner and more future-proof.
In this article you’ll learn:
- what changed
- why these decisions were made
- how to safely upgrade from v8 (or older)
Why this release?
For years the webservice supported multiple protocols simultaneously: REST, SOAP and XMLRPC.
In practice almost every integration already uses REST, while the legacy protocols mainly added maintenance overhead and complexity.
Webservice v9 therefore makes a clear choice:
- One modern API — no legacy layers.
- Benefits include:
- less internal complexity
- improved performance
- clearer documentation
- long-term stability
SOAP and XMLRPC removed
Starting from version 9, the legacy protocols are no longer available.
Both had been deprecated for multiple releases.
v9 officially removes them completely.
If your integration still uses SOAP or XMLRPC, you must migrate to REST before upgrading.
Cleaner REST URL structure
We also simplified the REST endpoint URLs.
The /index.php/ segment is no longer required.
Old structure (v8 and earlier)
- POST /index.php/webservice/auth
- GET /index.php/webservice/read_entry/search_etntry
- POST /index.php/webservice/create_entry
- POST /index.php/webservice/update_entry
- POST /index.php/webservice/delete_entry
New structure (v9)
- POST /webservice/auth
- GET /webservice/entry
- POST /webservice/entry
- PUT /webservice/entry
- DELETE /webservice/entry
If your server does not have URL rewriting enabled, the /index.php/webservice/... URLs will continue to work.
Upgrade checklist
- Before deploying to production, verify the following:
- Identified all SOAP and XMLRPC calls in your codebase
- Migrated them to REST equivalents
- Updated REST URLs to remove /index.php
- Tested authentication via POST /webservice/auth
- Tested critical read/write operations
- Verified everything in a staging environment
Webservice v9 removes the past and focuses fully on a modern API.
Once upgraded, integrations become simpler, cleaner and easier to maintain going forward.
2/20/2026