Apollo GraphOS Platform
OverviewQuickstart
APIs and Tools
GraphOS Platform API

GraphOS MCP Server

InstallTools
Apollo Sandbox
Schema Management
Overview

Schema Delivery

Publishing

OverviewPublish with RoverPublish with the Platform APIGuide: Publish with GitHub Actions
Launches

Graph Artifacts

OverviewDeploy with Graph ArtifactsTagsOCI RegistrySelf-host Artifacts

Contracts

OverviewCreateUsage PatternsReference

Schema Checks

OverviewRun ChecksCustom ChecksChecks ConfigurationGitHub IntegrationChecks Reference

Schema Linting

OverviewLinter Rules

Schema Proposals

OverviewConfigureCreateReviewImplement
Explorer IDE
OverviewConnect and AuthenticateOperation CollectionsSubscription SupportEmbedScriptingAdditional Features
Graph Security
OverviewPersisted Queries
Metrics and Insights
Overview

Metrics Collection and Forwarding

Sending Metrics to GraphOSOperation SignaturesDatadog Forwarding

Insights and Analysis

Operation MetricsField UsageError DiagnosticsSubgraph MetricsSegmenting by Client

Notifications and Alerts

OverviewDaily ReportsSchema ChangesSchema ProposalsPerformance AlertsBuild Status
Access Management
Organizations

API Keys

OverviewGraph API KeysSubgraph API KeysPersonal API KeysOperator API KeysManage API Keys with GraphOS StudioManage API Keys with the Platform API
Members, Roles, and PermissionsAudit Logs

SSO

OverviewMulti-Organization

SAML

OktaMicrosoft Entra IDGeneric SAML Setup

OIDC

OktaMicrosoft Entra IDGeneric OIDC Setup

SCIM

OverviewOktaMicrosoft Entra ID
Graph Management
Using VariantsAdding SubgraphsManaging SubgraphsUpdating Graph ComponentsTransferring Graphs
Production Readiness
Production Readiness Checklist

Testing and Load Management

Overload ProtectionLoad TestingTesting with Federation

Environment and Deployment

Environment Best PracticesSchema Change ManagementUpdating Client SchemaDeployment Best Practices
Platform Limits
Products
Apollo GraphOS PlatformManage, observe, and scale your graph.Apollo ConnectorsConnect REST APIs to your graph declaratively.Apollo FederationFederate multiple subgraphs into a single supergraph.Rover CLIInteract with your graph from the command line.Apollo RouterRun and configure your graph gateway.Apollo OperatorDeploy and manage Apollo Router on Kubernetes.
Open source
Apollo Client (Web)Simplify GraphQL data management in web apps.Apollo iOSSwift-first GraphQL client for iOS.Apollo KotlinKotlin-first GraphQL client for Android and JVM.Apollo ServerBuild GraphQL servers with Node.js.Apollo MCP ServerExpose GraphQL tools to AI agents with MCP.IDE SupportEnhance your development workflow with IDE support.
Resources

GraphQL Subscription Support

Execute GraphQL subscription operations in GraphOS Studio Explorer

The GraphOS Studio Explorer provides support for executing GraphQL subscription operations using a variety of protocols (including WebSocket and HTTP). You can configure the Explorer to use whichever protocol your GraphQL endpoint requires.

Setup

To execute a GraphQL subscription operation in the GraphOS Studio Explorer, first open the Explorer's Connection settings to specify your subscriptions endpoint and implementation:

Subscription settings in the Explorer
note
Remember that the path and protocol of your subscriptions URL might differ from those of your primary endpoint.
Which 'implementation' do I choose?
  • If you're subscribing to a subgraph or a standalone GraphQL server, choose whichever WebSocket subprotocol the server uses.
    • If you aren't sure which subprotocol the server uses, choose Autodetect and the Explorer will attempt to determine the correct subprotocol.
  • If you're subscribing to the router, choose Multipart subscriptions. This is the HTTP-based protocol that the router uses.

Executing a subscription

You define a subscription operation in the Explorer's Operation panel, just as you do for a query or mutation. When you run the subscription, a Subscriptions panel appears in the bottom right that updates as new data arrives:

Subscriptions panel in the Explorer

  • The most recently received payload is displayed at the top of the panel.

  • The dot next to STATUS indicates whether the Explorer is connected to your subscriptions endpoint (green if connected, red if disconnected).

  • Click the X next to Listening to stop listening for updates. The updates you've already received remain in the panel.

  • Click the X next to Subscriptions to close the panel entirely.

Troubleshooting connection issues

If you can't connect to your subscriptions endpoint, double-check all the following in the Explorer's Connection settings:

  • The protocol of your endpoint URL (ws/wss for WebSocket, http/https for HTTP)

  • The path of your endpoint URL

  • Your selected subscriptions implementation (see Setup)