# Support for \_\_typename in the top field of a mutation

**URL:** <https://community.fibery.io/t/support-for-typename-in-the-top-field-of-a-mutation/10441>\
**Category:** API & Programming\
**Created:** [February 26, 2026, 2:26pm UTC](https://community.fibery.io/t/support-for-typename-in-the-top-field-of-a-mutation/10441 "2026-02-26T14:26:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![finoto](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/finoto/32/10838_2.png) [@finoto](https://community.fibery.io/u/finoto)\
**Post date:** [February 26, 2026, 2:26pm UTC](https://community.fibery.io/t/support-for-typename-in-the-top-field-of-a-mutation/10441/1 "2026-02-26T14:26:32Z")

</div>

I’m using the [graphql-platform](https://github.com/ChilliCream/graphql-platform) as a client library to create entities in a space. This library works by code-generating type-safe C# code from the queries and the schema for the space.

One side effect of this is that the library always injects a \_\_typename field at every level of the query. This means that I can’t run any queries since it’s not supported on the top field.

Example minimal mutation:

```graphql
mutation Test {
  supportTickets {
    __typename
  }
}

```

response:

```json
{
  "errors": [
    {
      "message": "Operation [__typename] is not found for SupportSupportTicket",
      "locations": [
        {
          "line": 86,
          "column": 3
        }
      ],
      "path": [
        "supportTickets"
      ]
    }
  ],
  "data": {
    "supportTickets": null
  }
}

```

The library authors have said a long time ago that this field is required by the GraphQL spec, and I don’t have a way to disable this field during code-generation: [Allow Strawberry Shake to remove \_\_typename from queries · Issue #3565 · ChilliCream/graphql-platform · GitHub](https://github.com/ChilliCream/graphql-platform/issues/3565)

Is there a reason why the \_\_typename field is not supported at this level? It seems to work on all other levels.

---

<div class="post-metadata">

**Author:** ![Oleg](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oleg/32/1887_2.png) [@Oleg](https://community.fibery.io/u/Oleg)\
**Post date:** [February 27, 2026, 1:43pm UTC](https://community.fibery.io/t/support-for-typename-in-the-top-field-of-a-mutation/10441/2 "2026-02-27T13:43:42Z")

</div>

Hello, @finoto

Thanks for letting us know about this issue. Will check what we can do here and let you know in several days.

---

<div class="post-metadata">

**Author:** ![Oleg](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oleg/32/1887_2.png) [@Oleg](https://community.fibery.io/u/Oleg)\
**Post date:** [March 2, 2026, 1:22pm UTC](https://community.fibery.io/t/support-for-typename-in-the-top-field-of-a-mutation/10441/3 "2026-03-02T13:22:52Z")

</div>

@finoto Hi, again

The issue was fixed and updated version of graphql is in production. Please let us know if any issues.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3ed2464ee2a08eedf81584451cc0639f31e284a9.png)