I use the search graph API to search users by email. Here is an example of how I do this:
GET https://graph.facebook.com/search?q=Sample%40gmail.com&fields=name%2clink%2ceducation%2cid%2cwork%2cabout%2cpicture&limit=2&type=user&access_token=...
Before July 2013 Breaking Changes, it worked fine. As soon as I turned on violations, I started receiving HTTP 403, saying that the access token is invalid.
HTTP/1.1 403 Forbidden Access-Control-Allow-Origin: * Cache-Control: no-store Content-Type: text/javascript; charset=UTF-8 Expires: Sat, 01 Jan 2000 00:00:00 GMT Pragma: no-cache WWW-Authenticate: OAuth "Facebook Platform" "insufficient_scope" "(#200) Must have a valid access_token to access this endpoint" X-FB-Rev: 798183 X-FB-Debug: lZPVbdTmZrCo+Bde/MNEXy/halUzQx7qIDW5aiZeT0g= Date: Mon, 29 Apr 2013 07:25:29 GMT Connection: keep-alive Content-Length: 120 {"error":{"message":"(#200) Must have a valid access_token to access this endpoint","type":"OAuthException","code":200}}
As soon as I remove% 40 (@ sign) or part of .com from the request, I get normal HTTP 200 results. The problem is that this is not what I am looking for. I want to be able to search users by email as I could before.
Example queries executed :
GET https://graph.facebook.com/search?q=Samplegmail.com&fields=name%2clink%2ceducation%2cid%2cwork%2cabout%2cpicture&limit=2&type=user&access_token=... GET https://graph.facebook.com/search?q=Sample%40gmail&fields=name%2clink%2ceducation%2cid%2cwork%2cabout%2cpicture&limit=2&type=user&access_token=...
source share