Smartsheet API
GET /2.0/home endpoint removal
Deprecated, no dateSubscribe to Smartsheet APIShare
Smartsheet API has deprecated GET /2.0/home without a shutdown date. Calls to this endpoint will eventually fail once retired, though a final sunset date is currently being re-evaluated. Smartsheet API announced the change on March 25, 2025.
Calls it hits
GET /2.0/home
What to use instead of these calls
Use GET /2.0/workspaces and the workspace children endpoints instead.
In Smartsheet API's words
While the endpoints remain deprecated, a final sunset date is currently being re-evaluated.
Facts
- API
- Smartsheet API
api.smartsheet.com - Kind
- Endpoint removal
- Announced
- March 25, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Smartsheet API's own pages
Questions
When does this change take effect?
Smartsheet API deprecated GET /2.0/home without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Smartsheet 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.
More from Smartsheet API 10
-
DELETE /2.0/reports/{id}/shares/{id}Endpoint removal Stopped working -
DELETE /2.0/sheets/{id}/shares/{id}Endpoint removal Stopped working -
DELETE /2.0/sights/{id}/shares/{id}Endpoint removal Stopped working -
DELETE /2.0/workspaces/{id}/shares/{id}Endpoint removal Stopped working -
GET /2.0/folders/{id}Endpoint removal Stopped working -
GET /2.0/folders/{id}/foldersEndpoint removal Stopped working -
GET /2.0/reports/{id}/sharesEndpoint removal Stopped working -
GET /2.0/reports/{id}/shares/{id}Endpoint removal Stopped working -
POST /v2/sheets/{id}/copyParameter removal Stops workingin 9 days -
POST /v2/sheets/{id}/moveParameter removal Stops workingin 9 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.