api.eu.sparkpost.com
GET /api/v1/transmissions/{id} endpoint removal
api.eu.sparkpost.com has deprecated GET /api/v1/transmissions/{id} without a shutdown date. Calls made to this endpoint will eventually fail. The official documentation notes that this feature has been deprecated.
Calls it hits
GET /api/v1/transmissions/{id}
What to use instead of these calls
SparkPost documents no replacement for reading back a scheduled transmission. You must keep the scheduled transmission details on your side and follow its messages with GET /api/v1/events/message filtered by campaign_ids.
SparkPost documents no replacement for reading back a scheduled transmission.
In api.eu.sparkpost.com's words
Deprecation Notice : This feature has been deprecated.
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 GET /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
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.