# GET /api/v1/transmissions/{} is deprecated

SparkPost API deprecated GET /api/v1/transmissions/{} without giving a shutdown date yet.

SparkPost has deprecated the GET /api/v1/transmissions/{} endpoint without a shutdown date. Requests to this route will eventually fail. The provider notes that this feature has been deprecated.

## What to use instead

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.

- API: SparkPost API (api.sparkpost.com)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `GET /api/v1/transmissions/{}`
- Source: [Announcement](https://developers.sparkpost.com/api/transmissions/)
- Verified: October 26, 2026, against SparkPost API's own pages
- Page: https://www.okapi.bot/providers/sparkpost-api/breaking-changes/get-api-v1-transmissions-is-deprecated/

## SparkPost API's words

> Deprecation Notice : This feature has been deprecated.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent