I tested with a fairly old (10+ year) gmail account and every field other than the full name came back as null which is surprising, will try a few more tests and see how i go, but that wasnt the expected result :)
Thanks Ryan! It only supports query by email at the moment but if you can explain the social url use case and the atteibutes you’d want to retrieve I’ll see what’s possible.
if this is truly "real-time" and not a cached graph, how do you handle rate limiting and CAPTCHAs at scale? Even with "public" data, on-demand scraping usually requires massive residential proxy rotation which eats that $0.03 margin alive.
if you tried the curl command then yes this is indeed fast. the example curl command is hardcoded, [email protected] is used with a static response for the purposes of allowing users to test the shape of the api without needing to be authed. low time to first test was my aim.
keen to hear if you have a use case for something like this?
if this is truly "real-time" and not a cached graph, how do you handle rate limiting and CAPTCHAs at scale? Even with "public" data, on-demand scraping usually requires massive residential proxy rotation which eats that $0.03 margin alive.
if you tried the curl command then yes this is indeed fast. the example curl command is hardcoded, [email protected] is used with a static response for the purposes of allowing users to test the shape of the api without needing to be authed. low time to first test was my aim.
keen to hear if you have a use case for something like this?