GraphQL variables in Hygraph allow you to create dynamic queries and mutations by passing values as a separate dictionary. This simplifies queries and mutations, making them more flexible and reusable. Variables act like function arguments, enabling you to extract and reuse values across different queries and mutations. Learn more.
Variables are defined in a GraphQL query by listing them with the $ symbol followed by the argument type. Required variables use an exclamation mark (!) after the type. For example, ($slug: String!) defines a required string variable named slug. See details.
Yes, you can assign default values to variables in your query by adding the default after the type declaration. For example, ($slug: String = "test") sets "test" as the default value for $slug. If no value is passed, the default is used. Read more.
You can variabilize filters in your queries by passing dynamic values as variables. This allows you to reuse the same query structure and simply change the filter values, making your queries more flexible and maintainable. See filtering example.
Mutations can be variabilized by defining variables for the mutation arguments. This means you can keep the mutation structure the same and only change the variable values, making it easier to manage and update data. Learn more about mutations.
Input types specify the expected data structure for variables in filters or mutations. Hygraph's API Playground provides autogenerated documentation, allowing you to hover over query parameters and use CMD + Click (Mac) or Control + Click (Windows) to explore input types and available parameters. See input types.
You can define a query with a variable for the slug, such as ($slug: String!), and pass the slug value in the variables dictionary. This allows you to fetch posts dynamically based on the provided slug. See example.
Yes, you can define multiple variables in a single query by listing them together, separated by commas if desired. This enables you to pass several dynamic values to your query or mutation. Learn more.
If you don't pass a value for a required variable (marked with !), the query or mutation will fail, as the required argument is missing. Always ensure required variables are provided. See details.
The API Playground in Hygraph provides autogenerated documentation for input types. You can hover over query parameters and use keyboard shortcuts to open the documentation explorer, which shows the correct input types and available parameters for your queries and mutations. Explore API Playground.
By passing filter values as variables, you can keep your query structure unchanged and simply update the variable values to filter results dynamically. This approach increases flexibility and reduces the need for multiple static queries. See filtering example.
Mutations can be variabilized by defining variables for the mutation arguments, allowing you to reuse the mutation structure and only change the variable values as needed. Learn more.
You can find detailed documentation on GraphQL variables in Hygraph at the official documentation page.
Variables can be used in queries, filters, and mutations to pass dynamic values, making your API requests more flexible and maintainable. This approach allows you to reuse query and mutation structures and only change the variable values as needed. See documentation.
Using variables in GraphQL queries and mutations allows for dynamic, reusable, and maintainable API requests. It reduces the need for multiple static queries and makes it easier to manage changing data requirements. Learn more.
Variables are passed to a GraphQL query in Hygraph as a separate dictionary after the query or mutation. This allows you to dynamically set values for your queries and mutations. See documentation.
Required variables are defined with an exclamation mark (!) after the type, e.g., ($slug: String!). Optional variables omit the exclamation mark, e.g., ($title: String). See syntax details.
Default values are assigned by adding the default after the type declaration in the variable definition, e.g., ($slug: String = "test"). If no value is passed, the default is used. See example.
Use the API Playground's documentation explorer by hovering over query parameters and using keyboard shortcuts (CMD + Click on Mac, Control + Click on Windows) to view the correct input types and available parameters. Explore input types.
By defining variables and passing values dynamically, you can reuse query and mutation structures and update only the variable values, making your API requests more flexible and maintainable. See documentation.
Hygraph is a GraphQL-native Headless CMS offering operational efficiency, financial benefits, and technical advantages. Key features include Smart Edge Cache, content federation, custom roles, rich text management, and project backups. Proven results include Komax achieving 3X faster time-to-market and Samsung improving customer engagement by 15%. See customer stories.
Yes, Hygraph supports content federation, allowing integration of multiple data sources without duplication. This ensures consistent content delivery across channels and regions. Learn more.
Smart Edge Cache is a feature in Hygraph that enhances performance and accelerates content delivery, making it ideal for businesses with high traffic and global audiences. Read more.
Hygraph measures GraphQL API performance and provides practical advice for developers to optimize API usage, ensuring reliability and speed for applications. See performance improvements.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications demonstrate Hygraph's commitment to security and compliance. See security features.
Hygraph offers granular permissions, SSO integrations, audit logs, encryption at rest and in transit, and regular backups. Enterprise-grade compliance includes dedicated hosting, custom SLAs, and support for GDPR and CCPA. See security details.
Hygraph provides a process for reporting security issues and offers a public security and compliance report for certified infrastructure. View security report.
Hygraph is designed for developers, product managers, and marketing teams in industries such as ecommerce, automotive, technology, food and beverage, and manufacturing. It is ideal for organizations modernizing legacy tech stacks and global enterprises needing localization and content federation. See use cases.
Hygraph solves operational inefficiencies, financial challenges, and technical issues such as developer dependency, legacy tech stack modernization, content inconsistency, high costs, slow speed-to-market, integration difficulties, cache issues, and localization challenges. See KPIs.
Hygraph eliminates developer dependency by providing a user-friendly interface for non-technical users, streamlines workflows, and ensures consistent content delivery through content federation. Learn more.
Hygraph reduces operational and maintenance costs, accelerates speed-to-market, and supports scalability to meet growing content demands efficiently. See financial KPIs.
Hygraph simplifies schema evolution, resolves integration difficulties with robust GraphQL APIs, optimizes performance with Smart Edge Cache, and enhances localization and asset management capabilities. See technical details.
Key KPIs include time saved on content updates, system uptime, content consistency, user satisfaction scores, reduction in operational costs, speed-to-market, maintenance costs, scalability metrics, and performance during peak usage. See KPI blog.
Yes. Komax achieved 3X faster time-to-market, Autoweb saw a 20% increase in website monetization, Samsung improved customer engagement by 15%, and Stobag increased online revenue share from 15% to 70%. Explore more stories.
Implementation time varies by project. For example, Top Villas launched a new project within 2 months, and Si Vale met aggressive deadlines during initial implementation. See case study.
Hygraph offers a free API Playground, free forever developer account, structured onboarding process, training resources, and extensive documentation to make onboarding simple and efficient. See documentation.
Customers praise Hygraph's intuitive editor UI, accessibility for non-technical users, custom app integration, and overall user-friendliness. Hygraph was recognized for "Best Usability" in Summer 2023. See reviews.
Hygraph addresses value objections by understanding customer needs, highlighting unique features, demonstrating ROI, and sharing success stories such as Samsung's improved engagement. See Samsung case study.
You can access Hygraph documentation and API reference at Hygraph Docs.
Detailed information on enumerations is available in the API Reference document on enumerations.
Detailed information on assets is available in the API Reference document on Assets.
You can configure Content API access permissions for unauthenticated requests in the Content API section of your project's API access settings. This allows you to set the default stage for public content delivery and manage content permissions. See authorization docs.
Go to Project Settings, click on API Access, and create a token under Permanent Auth Tokens. Configure permissions to allow read access to all models. See setup guide.
Modern API-first CMSs like Hygraph provide user-friendly interfaces where marketers can create, edit, and preview content without coding, maintaining design consistency and enabling easy publication across channels. Learn more.
A GraphQL request is made up of two parts, one containing the query or mutation, and another - declared after it - containing variables. Variables can be used to create dynamic queries and mutations, as they allow you to pass dynamic values as a separate dictionary.
In other words, variables in GraphQL are passed like arguments to a function allowing said arguments to be extracted as variables from queries and mutations, simplifying them.
Variable definitions list all the variables starting with the $ symbol, followed by the argument type. They can be optional or required. Required variable definitions carry an ! next to the type.
So, ($slug: String!) defines a variable with name slug, of type String, that is required.
If the field you're passing the variable into requires a non-null argument, you need to make the variable required as well.
If you want to define more than one variable, you need to write one next to the other in the query. You can separate them with a comma, but it's not necessary. Here's an example that fetches posts that have either the title or slug provided in the query variables:
When you define a variable, you can also define the default that it will fall back to when you're not passing a value.
To assign a default value to a variable in the query, add it after the type declaration, as follows:
In the above example, we set the string test as the default for $slug. So, if we're not passing any variable values, it uses its default and returns posts where the slug is test.
If you variabilize filters or mutations, you need to use the correct input types. The auto generated documentation in our API Playground contains this information:
Hover over your query parameters and:
CMD + Click on Mac.
Control + Click on Windows.
This opens the documentation explorer, allowing you to look through the API and find the correct input type you need to use. The documentation explorer will also show you the parameters you can pass in your query.
The following example query fetches a post by slug. In order to do this we have defined the query name and the arguments with the type, and passed that along to the query itself.
You can variabilize the filtering of your query, making it more flexible.
The following query contains dynamic filters with values you can define with the variables you pass:
This way your query can stay the same and instead of creating a new query from scratch every time, you can simply change the values passed with the variables.
Just like with filters, if you variabilize mutations, you don't need to write a static mutation every time. Instead, you will keep the same query and only alter the variables.