# The legacy /service/ API (v1 to v4.1 REST and SOAP) is deprecated

SugarCRM API deprecated /service/* without giving a shutdown date yet.

SugarCRM API deprecated the legacy /service/* endpoints without a shutdown date. Affected calls include legacy REST and SOAP requests to these endpoints, which will eventually fail. SugarCRM API notes that legacy APIs remain accessible for now, but existing integrations must move to modern endpoints.

## What to use instead

Move calls from /service/v4_1/rest.php and soap.php to the REST API under /rest/v11_x/, obtaining an OAuth2 token from /rest/v11_x/oauth2/token.

- API: SugarCRM API (*.sugarondemand.com)
- Kind: Removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/service/*`
- Source: [Announcement](https://support.sugarcrm.com/documentation/sugar_developer/sugar_developer_guide_25.2/integration/web_services/)
- Verified: November 6, 2026, against SugarCRM API's own pages
- Page: https://www.okapi.bot/providers/sugarcrm-api/breaking-changes/the-legacy-service-api-v1-to-v4-1-rest-and-soap-is-deprecated/

## SugarCRM API's words

> As of Sugar 7.0, SOAP support is no longer offered with the new APIs. The legacy APIs will remain accessible in the product, however, any existing integrations should be updated to use the latest REST endpoints.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent