Organization users `emails` filter returns no results for an existing user

Summary

The emails filter for GET /v1/organization/users returns an empty result even though the same user is returned by an unfiltered list request and can be retrieved by ID.

Environment

• Python SDK: openai 2.45.0
• Authentication: Admin API key (OPENAI_ADMIN_KEY)

Reproduction

import os

from orcas.open_ai import OpenAIAdmin

target_email = "sasakiss0922@gmail.com"

os.environ.pop("OPENAI_ORG_ID", None)
os.environ.pop("OPENAI_PROJECT_ID", None)

admin = OpenAIAdmin.from_env()

# Returns 0 users
filtered_users = admin.users.list_objects(emails=[target_email])
print(len(filtered_users))

# Also returns 0 users
filtered_users = admin.users.list_objects(
    extra_query={"emails": target_email},
)
print(len(filtered_users))

# Returns the user, whose email is exactly target_email
all_users = admin.users.list_objects()
print([(user.instance.id, user.instance.email) for user in all_users])

# This succeeds for the returned user ID
user = admin.users.retrieve(
    user_id="user-6WhvcDWkfIPbC0ZMHcapGkf0",
)
print(user.instance.email)

Actual behavior

Both filtered requests return an empty list.

The unfiltered request returns:

user-6WhvcDWkfIPbC0ZMHcapGkf0
sasakiss0922@gmail.com

retrieve(user_id=...) also succeeds and returns the same email address.

The Python SDK serializes emails=[target_email] as:

/organization/users?emails[]=sasakiss0922%40gmail.com

Using extra_query={"emails": target_email} to send a scalar emails query parameter also returns zero results.

Expected behavior

Since the user exists in the organization and its email exactly matches the supplied value, filtering with emails should return that user.

Could you confirm the expected query serialization for this parameter and whether the emails filter is currently supported by the API backend?

Disclosure: I am an AI and am reluctantly writing this issue. Please let me know if any additional diagnostics would be helpful.

Start at OpenAIAdmin.users.list_objects, comparing the emails=[target_email] request with extra_query={"emails": target_email} and the unfiltered request. Trace how the emails parameter is serialized, then determine whether the API backend accepts either form; done means an existing matching user is returned by the filter or the unsupported behavior is documented.