SendGrid API
Legacy Marketing Campaigns Contacts API removal
Deprecated, no dateSubscribe to SendGrid APIShare
SendGrid API deprecated the legacy marketing campaigns contacts endpoints under /v3/contactdb/* without a shutdown date. These endpoints cover what the documentation describes as an obsolete API. When retired, affected calls to /v3/contactdb/* will fail.
Calls it hits
/v3/contactdb/*
What to use instead of these calls
Manage contacts and lists using the Marketing Campaigns Contacts API endpoints /v3/marketing/contacts and /v3/marketing/lists instead. Moving requires migrating contacts, lists, and senders, as the new Marketing Campaigns maintains its own data rather than only updating endpoints.
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/contactdb/* 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/senders*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.