POST /v1/do-not-email-list → endpoint removal
Snov.io API
Deprecated, no date
The provider has deprecated the POST /v1/do-not-email-list endpoint without a shutdown date. Calls made to this route will eventually fail. The method previously allowed adding an email or domain to prevent sending emails to it, but it is now marked as deprecated.
Calls it hits
POST /v1/do-not-email-list
What to use instead of these calls
Call POST /v2/blacklists/{list_id}/items instead, which adds the valid items and returns the reason for each invalid one.
In Snov.io API's words
After this email/domain has been added to the list, you won't be able to send emails to it. This method is deprecated. Use Add items to a Do-not-email list
Facts
- API
- Snov.io API
api.snov.io - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Snov.io API's own pages
Questions
When does this change take effect?
Snov.io API deprecated POST /v1/do-not-email-list without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Snov.io 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.