SugarCRM API
legacy /service/ API (v1 to v4.1 REST and SOAP) removal
Deprecated, no dateSubscribe to SugarCRM APIShare
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.
Calls it hits
/service/*
What to use instead of these calls
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.
In 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.
Facts
- API
- SugarCRM API
*.sugarondemand.com - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against SugarCRM API's own pages
Questions
When does this change take effect?
SugarCRM API deprecated /service/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: SugarCRM 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.