GET /v1/exist → endpoint removal
Hunter API
Deprecated, no date
Hunter API deprecated the GET /v1/exist endpoint without a shutdown date. Subsequent requests to this endpoint fail. The provider notes that this call is deprecated and directs users to its newer verification alternative.
Calls it hits
GET /v1/exist
What to use instead of these calls
Call the Email Verifier, GET /v2/email-verifier?email=..., instead.
In Hunter API's words
This API call is deprecated, please use the Email Verification call instead.
Facts
- API
- Hunter API
api.hunter.io - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Hunter API's own pages
Questions
When does this change take effect?
Hunter API deprecated GET /v1/exist without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Hunter 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.