Comment 1 for bug 799612

Hi Florian, can you provide some clarification on exactly what you need? Here's what you can do right now in the REST API:

Given an email address, you can get a list of all that's address's memberships. You get a sequence of member entries, and from each of these you can find its mailing list, role, and member id. So while you'd still have to do a search, it should be of a much smaller set.

Note that to identify a "membership", you need the triplet of address-or-user[*], mailing list, and role.

[*] You can now provide a user as long as the user has a preferred address.