SparkPost API
GET /api/v1/transmissions/{id} endpoint removal
Deprecated, no dateSubscribe to SparkPost APIShare
SparkPost has deprecated the GET /api/v1/transmissions/{id} endpoint without a shutdown date. Requests to this route will eventually fail. SparkPost API notes that this feature has been deprecated.
Calls it hits
GET /api/v1/transmissions/{id}
What to use instead of these calls
Keep the scheduled transmission details on your side, and follow its messages with GET /api/v1/events/message filtered by campaign_ids. Moving away requires structural adjustments, as SparkPost documents no replacement for reading back a scheduled transmission.
SparkPost documents no replacement for reading back a scheduled transmission.
In SparkPost API's words
Deprecation Notice : This feature has been deprecated.
Facts
- API
- SparkPost API
api.sparkpost.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against SparkPost API's own pages
Questions
When does this change take effect?
SparkPost API deprecated GET /api/v1/transmissions/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: SparkPost 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 SparkPost API 1
-
No date
DELETE /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.