The documentation says I can retrieve all user profiles for a domain by sending a GET to:
https://www.google.com/m8/feeds/profiles/domain/*domainName*/full<https://www.google.com/m8/feeds/profiles/domain/domainName/full> What I actually get back is the first 60 profiles and a <link rel='next' href=…> with a URL including a "start-key" to get the next 60 profiles. This is exactly how the Provisioning and Shared Contacts APIs work and I routinely follow the "next" links from them without any problems. But when I use the "next" link I get back from the Profiles API, it just gives me the first 60 profiles again and the exact same "start-key" again. Since that approach didn’t work, next I tried sending multiple requests specifying "start-index" and "max-results", incrementing "start-index" each time. Google honored whatever I sent for "max-results", but no matter what "start-index" I sent, it started with the first profile. So far, the best I’ve come up with is to use the Provisioning API (where the "next" links work properly) to get the usernames then retrieve each profile individually. That works, but it’s abysmally slow. I’m also concerned that when we finish with our relatively small test group and migrate thousands of users onto this domain, that approach will exceed some Google requests per unit of time limit. Does anyone know a better approach? Better yet, does anybody have any idea how to get the attention of somebody at Google who might fix their API? I think it’s clearly broken, but Google Support won’t accept reports of clearly broken APIs. They just tell me to use this forum. -- You received this message because you are subscribed to the Google Groups "Google Contacts, Shared Contacts and User Profiles APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://code.google.com/apis/contacts/community/forum.html
