0

losing email addresses in social.profile YQL query w JSON format

Using the YQL console with the get profile info query, i can see three emails for a user (in this case myself):

yql query: select * from social.profile where guid=me

emails I get back:

"emails": [{"handle": "shellyhivemind@gmail.com", "id": "1", "type": "HOME"},
{"handle": "shellydfarnham@yahoo.com", "id": "2","primary": "true","type": "HOME" },
{ "handle": "shellyrandham@yahoo.com", "id": "8","type": "HOME"}
],

But, when I'm doing the same YQL query from my application, I only see the first email (see below). What might account for this difference?

"emails":[{"handle":"shellyhivemind@gmail.com","id":"1","type":"HOME"},{"id":"2","primary":"true","type":"HOME"},{"id":"8","type":"HOME"}]

In the console, it says the rest query is going to http://query.yahooapis.com/v1/public/yql?q...callback=cbfunc. In my YQL query url i'm not including the "public" or the argument "callback=cbfunc", that's the only difference I see. When I try change it to public the query doesn't work, and when I add callback-cbfunc however it makes no difference in the results.

Any ideas? I need those emails, in particular the primary one.

by
1 Reply
  • Hi ShellyShelly... I'm going to guess (possibly incorrectly) that the issue might be related to the Permissions associated with your Consumer Key.

    If you go to the YDN My Projects page for your app (accessed from "http://http://developer.yahoo.com/dashboard"), you'll see a list of Permissions available for you app. Do you have the "Read/Write" scope selected for the Profiles API with this description ("With your user's permission, you can read and write their Profile information that is marked as either public, shared with Connections, or private, excluding Contact information.") and NOT the Profiles API with this description ("(Required for OpenSocial) With your user's permission, you can read their Profile information that is marked as either public or shared with Connections.")?

    I know it's confusing, and the team is working on cleaning up the language/descriptions around these, but hopefully changing these settings (and then using the updated Consumer Key and Secret that result from such a change) will make this work as anticipated.
    0

Recent Posts

in YQL