From what I can tell the Carrier name on the API is pretty dated material. The mobile carrier lookup on the other hand appears to be valid.
What are the implications of a developer pulling the carrier information from the carrier lookup as opposed to using the API?
Are there any restrictions about doing so?
The problem here is the content on the API is really of no relevance in regards to the Carrier because that information is stale. The interest of the developer here is to get accurate carrier information and it seems you have a great tool to do so.
Hi Dan,
Thanks for providing this fantastic API, we're very excited about it. We've seen a similar issue reported by tknman, which is that while the data on the web tool for reverse carrier lookup is correct, the API returns different (and incorrect data). Clearly WhitePages have the correct information, it's just that the API must be feeding from a different database or something to that effect.
The API usage works better for us and we're not looking to break any rules.
Can you please advise?
Thanks!
From what I can tell the Carrier name on the API is pretty dated material. The mobile carrier lookup on the other hand appears to be valid.
What are the implications of a developer pulling the carrier information from the carrier lookup as opposed to using the API?
Are there any restrictions about doing so?
The problem here is the content on the API is really of no relevance in regards to the Carrier because that information is stale. The interest of the developer here is to get accurate carrier information and it seems you have a great tool to do so.
Your thoughts please?
Thanks
Dan_WhitePages – 3 weeks ago
Tknman,
It is against our websites Terms of Service to scrape data from it. This would include the carrier lookup tool.
Adva Mobile – 5 days ago
Hi Dan,
Thanks for providing this fantastic API, we're very excited about it. We've seen a similar issue reported by tknman, which is that while the data on the web tool for reverse carrier lookup is correct, the API returns different (and incorrect data). Clearly WhitePages have the correct information, it's just that the API must be feeding from a different database or something to that effect.
The API usage works better for us and we're not looking to break any rules.
Can you please advise?
Thanks!