# Testing and Debugging The GraphQL endpoints provide functionality to make it easier to test against a real account. ## Ignoring Test Requests Every operation made against the GraphQL endpoints cause your website's data to be mutated. When doing performance testing or an equivalent, it is often necessary to exclude test traffic so as to not pollute your live account. Using the header `X-Nosto-Ignore: True` will cause any traffic from being recorded. Queries and Mutations will work normally but any API calls containing this header will not be archived or accrue towards the statistics. An example of how this header can be leveraged can be found on our [Nosto's GraphQL Android Example](https://github.com/Nosto/example-android/wiki/Adding-Debugging-Support) app. ## Debugging Requests Every operation made against our GraphQL endpoint returns a unique request identifier contained in an `X-Request-Id` response header. While we ensure that the APIs are as robust as possible if you do encounter an HTTP 5XX response from the endpoint, simply log the request identifier along with the error as the unique request identifier allows our engineers to troubleshoot the issue swiftly. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nosto.com/techdocs/apis/graphql-an-introduction/graphql-testing-and-debugging.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.