Sendcloud API
GET /insights/parcels/counts-summary endpoint removal
Stopped workingSubscribe to Sendcloud APIShare
Calls to GET /insights/parcels/counts-summary on Sendcloud API stopped working on September 14, 2026.
Calls it hits
GET /insights/parcels/counts-summary
In Sendcloud API's words
* **GET** `/insights/parcels/counts-summary`
Facts
- API
- Sendcloud API
panel.sendcloud.sc - Kind
- Endpoint removal
- Announced
- September 14, 2026
- Takes effect
- September 14, 2026
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Sendcloud API's own pages
Questions
When does this change take effect?
Calls to GET /insights/parcels/counts-summary on Sendcloud API stopped working on September 14, 2026.
What happens to calls after September 14, 2026?
They have failed since September 14, 2026.
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 Sendcloud API 10
-
GET /analytics/carriersEndpoint removal Stopped working -
GET /analytics/shipping-methodsEndpoint removal Stopped working -
GET /brand/{id}/return-portal/customs-declaration/downloadEndpoint removal Stopped working -
GET /insights/parcels/bucketsEndpoint removal Stopped working -
GET /insights/parcels/seriesEndpoint removal Stopped working -
GET /insights/products/bucketsEndpoint removal Stopped working -
GET /insights/products/seriesEndpoint removal Stopped working -
GET /service-points/{id}/storeEndpoint removal Stopped working -
POST /service-points/check_and_storeEndpoint removal Stopped working -
POST /service-points/items_fit_in_shipmentEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.