api.eu.sparkpost.com
DELETE /api/v1/transmissions/{id} endpoint removal
api.eu.sparkpost.com deprecated the DELETE /api/v1/transmissions/{id} endpoint without a shutdown date. Calls made to this endpoint fail under the deprecation notice. Developers targeting api.eu.sparkpost.com can no longer rely on deleting transmissions by transmission ID.
Calls it hits
DELETE /api/v1/transmissions/{id}
What to use instead of these calls
Cancel scheduled transmissions with DELETE /api/v1/transmissions?campaign_id={campaign_id} instead.
In api.eu.sparkpost.com's words
Deprecation Notice : This feature has been deprecated. Please use the delete by campaign ID feature instead.
Facts
- API
- api.eu.sparkpost.com
api.eu.sparkpost.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against api.eu.sparkpost.com's own pages
Questions
When does this change take effect?
api.eu.sparkpost.com deprecated DELETE /api/v1/transmissions/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: api.eu.sparkpost.com 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 api.eu.sparkpost.com 1
-
No date
GET /api/v1/transmissions/{id}Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.