> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/s/schema.md). # Schema In a database, a schema defines the structure and organization of data. In GraphQL, it specifies the capabilities of the API and how to query it. A schema is a formal definition of the structure, constraints, and relationships of data in a system. The term is used in multiple contexts: in relational databases, a schema defines tables, columns, data types, and relationships; in GraphQL, a schema specifies the types, queries, mutations, and subscriptions available in the API; in JSON Schema, it defines the expected structure and validation rules for JSON documents. API schemas serve as contracts between API producers and consumers. OpenAPI specifications and JSON Schema definitions describe the expected format of request bodies, response payloads, query parameters, and headers. These schemas enable automated validation, documentation generation, and client SDK generation. In API gateway architectures, schemas are used for request validation -- the gateway can reject requests that do not conform to the defined schema before they reach backend services. This protects backends from malformed input and provides clear error messages to API consumers. Schema validation at the gateway level is especially valuable in serverless environments, where it prevents unnecessary function invocations for invalid requests. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/s/schema.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.