Manage GraphQL endpoints in AEM graphql-aem-endpoint

The endpoint is the path used to access GraphQL for AEM. Using this path you (or your app) can:

  • access the GraphQL schema,
  • send your GraphQL queries,
  • receive the responses (to your GraphQL queries).

There are two types of endpoints in AEM:

  • Global

    • Available for use by all sites.
    • This endpoint can use all Content Fragment Models from all Sites configurations (defined in the Configuration Browser).
    • If there are any Content Fragment Models that should be shared among Sites configurations, then these should be created under the global Sites configurations.
  • Sites configurations:

    • Corresponds to a Sites configuration, as defined in the Configuration Browser.
    • Specific to a specified site/project.
    • A Sites configuration specific endpoint will use the Content Fragment Models from that specific Sites configuration together with those from the global Sites configuration.
The Content Fragment Editor can allow a Content Fragment of one Sites configuration to reference a Content Fragment of another Sites configuration (via polices).
In such a case, not all content is retrievable using a Sites configuration specific endpoint.
The content author should control this scenario; for example, it may be useful to consider putting shared Content Fragment Models under the Global Sites configuration.

The repository path of the GraphQL for AEM global endpoint is:


For which your app can use the following path in the request URL:


To enable an endpoint for GraphQL for AEM you need to:

Enabling your GraphQL Endpoint enabling-graphql-endpoint

To enable a GraphQL Endpoint you first need to have an appropriate configuration. See Content Fragments - Configuration Browser.

If the use of content fragment models have not been enabled, the Create option will not be available.

To enable the corresponding endpoint:

  1. Navigate to Tools, General, then select GraphQL.

  2. Select Create.

  3. The Create new GraphQL Endpoint dialog opens. Here you can specify:

    • Name: name of the endpoint; you can enter any text.
    • Use GraphQL schema provided by: use the drop-down list to select the required site/project.
    note note
    The following warning is shown in the dialog:
    • GraphQL endpoints may introduce data security and performance issues if not managed carefully. Ensure that appropriate permissions are set after creating an endpoint.
  4. Confirm with Create.

  5. The Next steps dialog will provide a direct link to the Security console so that you can ensure that the created endpoint has suitable permissions.

    note caution
    The endpoint is accessible to everyone. This can - especially on publish instances - pose a security concern, as GraphQL queries can impose a heavy load on the server.
    You can set up ACLs, appropriate to your use case, on the endpoint.

Publishing your GraphQL Endpoint publishing-graphql-endpoint

Select the new endpoint and Publish to make it fully available in all environments.

The endpoint is accessible to everyone.
On publish instances this can pose a security concern, as GraphQL queries can impose a heavy load on the server.
Set up ACLs appropriate to your use case on the endpoint.