# API Users - metadata search - a bug?

**URL:** <https://community.auth0.com/t/api-users-metadata-search-a-bug/8770>\
**Category:** Get Help\
**Tags:** app\_metadata, metadata, search, bug, user-metadata\
**Created:** [November 18, 2017, 12:24am UTC](https://community.auth0.com/t/api-users-metadata-search-a-bug/8770 "2017-11-18T00:24:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zatziky](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/zatziky/32/10325_2.png) [@zatziky](https://community.auth0.com/u/zatziky)\
**Post date:** [November 18, 2017, 12:24am UTC](https://community.auth0.com/t/api-users-metadata-search-a-bug/8770/1 "2017-11-18T00:24:19Z")

</div>

I am not able to filter the search query for `app_metadata`. Our users have this shape:

```
 {
   "connection": "email",
   "email": "jill@jill.com",
   "user_metadata": {"name":"Jill Jill"},
   "app_metadata": {
       "app": {
            "id" :"appId"
        }
   }
 }

```

I have tried to query for `app_metadata.app.id` with the urls below but all of them return no results at all:

- `https://{{auth0_domain}}/api/v2/users?q=app_metadata.app.id:"appId"`
- `https://{{auth0_domain}}/api/v2/users?q=app_metadata.app.id:appId`
- `https://{{auth0_domain}}/api/v2/users?q=user.app_metadata.app.id:"appId"`
- `https://{{auth0_domain}}/api/v2/users?q=user.app_metadata.app.id:appId`

According to the [incident report](https://status.auth0.com/incidents/71nlbr16j7ng) only queries without `user.` should be working now.

Executing `https://{{auth0_domain}}/api/v2/users` works and returns 50 results. I have checked the `app.id` several times for spelling errors.

Is it a bug OR am I missing some point?

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [November 30, 2017, 11:07pm UTC](https://community.auth0.com/t/api-users-metadata-search-a-bug/8770/2 "2017-11-30T23:07:16Z")

</div>

It was a forced breaking change, in particular, as stated in that linked incident the user search over custom fields was restricted in some tenants in order to ensure that basic user search functionality could be restored. As also mentioned in the incident there was an email address that could be used by impacted tenants in order to inquire about the possibility to have those restrictions lifted if they had created the tenant account before the incident. I see that you or someone associated with your tenant domain has used that communication channel and that the situation is now addressed, however, wanted to give an update here in case someone else faces the same situation which in that case the recommended approach would be to indeed use the communication channel listed in the incident.

---

<div class="post-metadata">

**Author:** ![zatziky](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/zatziky/32/10325_2.png) [@zatziky](https://community.auth0.com/u/zatziky)\
**Post date:** [December 1, 2017, 12:54am UTC](https://community.auth0.com/t/api-users-metadata-search-a-bug/8770/3 "2017-12-01T00:54:53Z")

</div>

Hey Jmangelo, I wrote to support and they re-enabled it for us because we were still eligible for this API. Thanks for your response anyways.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:57am UTC](https://community.auth0.com/t/api-users-metadata-search-a-bug/8770/4 "2018-03-02T05:57:27Z")

</div>


