SendGrid API
Legacy Sender Identities API removal
Deprecated, no dateSubscribe to SendGrid APIShare
The Legacy Sender Identities API has been deprecated without a shutdown date. This deprecation affects all requests to the /v3/senders* endpoints, which cover the obsolete legacy marketing campaigns feature. Once permanently removed, calls to these endpoints will fail.
Calls it hits
/v3/senders*
What to use instead of these calls
Manage senders with the Marketing Campaigns Senders API (/v3/marketing/senders). The new Marketing Campaigns keeps its own contacts, lists, and senders, so moving requires migrating your data rather than just updating endpoint calls.
The new Marketing Campaigns keeps its own contacts, lists and senders; moving means migrating them, not only the calls.
In SendGrid API's words
Legacy Marketing Campaigns This covers the obsolete Legacy Marketing Campaigns API.
Facts
- API
- SendGrid API
api.sendgrid.com - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against SendGrid API's own pages
Questions
When does this change take effect?
SendGrid API deprecated /v3/senders* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: SendGrid 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 SendGrid API 2
-
No date
/v3/campaigns*Removal Deprecated, no date -
No date
/v3/contactdb/*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.