---
title: 'Generated GraphQL reference'
description: 'Find the authoritative types for your deployed project schema.'
---

# Generated GraphQL reference

The deployed schema in Explorer is the reference for your project's operations. Flexkit's entity and attribute definitions determine its types; a universal static list cannot describe every customer's schema.

## Schema map

| Configuration              | Inspect in GraphQL                                     |
| -------------------------- | ------------------------------------------------------ |
| Entity `name` and `plural` | Object type and query/mutation naming.                 |
| System record identity     | `_id` field and corresponding filters.                 |
| Global scalar              | Direct field with its declared data type.              |
| Local attribute            | Scope-aware object/selection and input shape.          |
| Relationship               | Nested object or list, connection and mutation inputs. |
| Asset                      | Asset identity and metadata fields.                    |

## Inspect before coding

Refresh Explorer's schema after deployment. Inspect the query or mutation, its arguments, nested input types, nullability, and return type. Copy the operation into a checked application example and validate it against that deployed schema.

Use [queries](/docs/api/graphql/queries) for reads and [mutations](/docs/api/graphql/mutations) for write workflow guidance. Keep generated types aligned with the deployed project when maintaining a typed client.

Do not substitute generic graph-database examples for your generated contract. A field removed from configuration is not available simply because an older client still references it.


---

[View full sitemap](/docs/sitemap.md)