Using GraphQL requires a domain schema. The schema is generated automatically when installing Ibexa DXP.
When you modify Content Types in your installation, you need to regenerate the schema:
To make use of enhanced Location handling, you can add the beta 3.0 version of ezplatform-graphql to your project.
GraphQL for Ibexa DXP is based on the Content Types, Content Type groups, and Content items defined in the Repository.
For each Content Type the schema exposes a singular and plural field, e.g.
Use the singular field to query a single Content item, and the plural to get a whole
(a list of Content items that supports pagination).
With the queries you can inspect:
- the existing types
- details of Content Types, and their Fields in the context of developing your own application
You can request additional content information such as the Section or Objects states,
available under the
You can also query Content Type and Content Type group information through the
The repository schema, accessed through
_repository, exposes the Ibexa DXP Repository
in a manner similar to the Public PHP API.
_repository field also enables you to query e.g. Object states configured for the Repository.
You can also use your own custom schema.
GraphQL is SiteAccess-aware, but can have only one schema per installation. This means you cannot use GraphQL with multiple repositories.
GraphQL for Ibexa DXP supports session-based authentication. You can get your session cookie by logging in through the interface or through a REST request.
If you have JWT authentication enabled, you can use the following query to get your authentication token:
1 2 3 4 5 6
1 2 3 4 5 6 7 8
You can access GraphQL with
The GraphiQL interactive client is included in the installation.
Access it through
Here you can run your queries and preview the results in an easy-to-read format.
GraphiQL offers side-by-side reference based on your generated schema in the Docs pane.