Hello,
Same request sent twice with seconds in between replies with a different JSON structure/field types. This makes it really hard to parse stuff in some languages. Below are example responses.
Suggestion: if you really need to refactor stuff/change field types, you should create new endpoints instead and use API versioning appreach (i.e. v1, v2, etc) but not change published ones on the fly.
$ curl --request GET --url 'https://mailcheck.p.rapidapi.com/?disable_test_connection=true&domain=zzrgg.com' --header 'x-rapidapi-host: mailcheck.p.rapidapi.com' --header 'x-rapidapi-key: hidden'
{"valid":"1","block":"1","disposable":"1","domain":"zzrgg.com","text":"Disposable \/ temporary domain","reason":"Heuristics x4","risk":"97","mx_host":"nb-96-126-99-158.fremont.nodebalancer.linode.com","possible_typo":null,"mx_ip":"96.126.99.158","mx_info":"Using MX pointer nb-96-126-99-158.fremont.nodebalancer.linode.com DNS with priority: 10","last_changed_at":"2020-04-18T23:22:43+02:00"}
$ curl --request GET --url 'https://mailcheck.p.rapidapi.com/?disable_test_connection=true&domain=zzrgg.com' --header 'x-rapidapi-host: mailcheck.p.rapidapi.com' --header 'x-rapidapi-key: hidden'
{"valid":true,"block":true,"disposable":true,"domain":"zzrgg.com","text":"Disposable e-mail","reason":"Heuristics (x1a)","risk":90,"mx_host":"nb-96-126-99-158.fremont.nodebalancer.linode.com","possible_typo":[],"mx_info":"Using MX pointer nb-96-126-99-158.fremont.nodebalancer.linode.com from DNS with priority: 10","mx_ip":"96.126.99.158"}
When will you fix it?
Best
加入讨论 - 在下面添加评论:
Hi!
Sorry about that. We have been doing a major overhaul of the infrastructure and backend which will greatly improve both response times and results. Unfortunately there’s been a few hiccups.
All responses should now match the same (old) format, with the exception of the new field “last_changed_at”.
Thank you for understanding, and thanks for reporting it. We will definitely do API versioning better if we ever need to do it again.