Join us for GraphQL Summit, October 10-12 in San Diego. Use promo code ODYSSEY for $400 off your pass.
Launch GraphOS Studio
Apollo Server 2 is officially deprecated, with end-of-life scheduled for 22 October 2023. Additionally, certain features are end-of-life as of 31 December 2023. Learn more about these deprecations and upgrading.

API Reference: Schema reporting plugin

Using the plugin

This API reference documents the ApolloServerPluginSchemaReporting plugin.

This plugin enables your GraphQL server to register its latest with the Apollo every time it starts up. Full details on schema reporting can be found in the Apollo Studio docs.

Schema reporting does not currently support graphs that use Apollo Federation. This plugin will not work if your graph is a federated or a composed federated graph running in a gateway. If you have a federated graph, you will need to register via the CLI; see Setting up managed federation.

In order to use this plugin, you must configure your server with a graph API key, either with the APOLLO_KEY environment or by passing it directly to your ApolloServer with new ApolloServer({apollo: {key: KEY}}). (This is the same way you configure your ApolloServer to enable usage reporting.)

If you just want to turn on reporting with its default configuration, you can set the APOLLO_SCHEMA_REPORTING environment to true. If you want to configure reporting (or prefer your setup to be via code rather than environment s), import ApolloServerPluginSchemaReporting from the apollo-server-core package and pass it to your ApolloServer in the plugins array:

import { ApolloServer } from "apollo-server";
import { ApolloServerPluginSchemaReporting } from "apollo-server-core";
const server = new ApolloServer({
plugins: [

This plugin was introduced in Apollo Server 2.18. In previous versions, reporting was configured using the engine option to the ApolloServer constructor. That option continues to work; see the migration guide for details.


Name /


The reporter waits before starting reporting. By default, the report waits some random amount of time between 0 and 10 seconds. A longer interval leads to more staggered starts which means it is less likely multiple servers will get asked to upload the same schema.

If this server runs in lambda or in other constrained environments it would be useful to decrease the reporting max wait time to be less than default.

This number will be the max for the range in ms that the reporter will wait before starting to report.



Override the reported that is reported to the Apollo . This schema does not go through any normalizations and the string is directly sent to the Apollo registry. This can be useful for comments or other ordering and whitespace changes that get stripped when generating a GraphQLSchema.

If you pass this option to this plugin, you should explicitly configure ApolloServerPluginUsageReporting and pass the same value to its overrideReportedSchema option. This ensures that the ID associated with requests reported by the usage reporting plugin matches the schema ID that this plugin reports. For example:

new ApolloServer({
plugins: [
overrideReportedSchema: schema
overrideReportedSchema: schema


The URL to use for reporting s. Primarily for testing and internal Apollo use.


typeof fetch

Specifies which Fetch API function implementation to use when reporting s.

Usage reporting plugin
Inline trace plugin
Edit on GitHubEditForumsDiscord