Sendcloud API
POST /api/v3/orders/{id}/split/ removal
Deprecated, no dateSubscribe to Sendcloud APIShare
Sendcloud API deprecated POST /api/v3/orders/{id}/split without giving a shutdown date yet.
Calls it hits
POST /api/v3/orders/{id}/split
In Sendcloud API's words
POST /api/v3/orders/{id}/split/
Facts
- API
- Sendcloud API
panel.sendcloud.sc - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Sendcloud API's own pages
Questions
When does this change take effect?
Sendcloud API deprecated POST /api/v3/orders/{id}/split without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Sendcloud 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 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/counts-summaryEndpoint 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
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.