# Internal server error when using \`where\` field in GraphQL API

**URL:** <https://community.prismic.io/t/internal-server-error-when-using-where-field-in-graphql-api/828>\
**Category:** Developing with Prismic\
**Tags:** graphql\
**Created:** [June 15, 2020, 5:14pm UTC](https://community.prismic.io/t/internal-server-error-when-using-where-field-in-graphql-api/828 "2020-06-15T17:14:41Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![alex](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@alex](https://community.prismic.io/u/alex)\
**Post date:** [June 17, 2020, 1:38am UTC](https://community.prismic.io/t/internal-server-error-when-using-where-field-in-graphql-api/828/4 "2020-06-17T01:38:16Z")

</div>

@Pau Thanks for the explanation, I think this was the cause of [my ticket as well](https://community.prismic.io/t/graphql-wherefilter-throws-500-filtering-boolean/849).

Is there a plan for the Prismic team to fix this? Naming a field with an underscore is a completely reasonable ask, especially since api fields appear to only allow lowercase characters. Using an underscore to make a field more readable shouldn’t break querying

---

_[View the full topic](https://community.prismic.io/t/internal-server-error-when-using-where-field-in-graphql-api/828)._