a6-recipe-graphql-proxy

Configure APISIX GraphQL proxy routing with a6 operation-based variables.

1|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/api7/a6 --skill a6-recipe-graphql-proxy-api7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a6-recipe-graphql-proxy
Source: https://github.com/api7/a6/tree/main/skills/a6-recipe-graphql-proxy
Command: npx skills add https://github.com/api7/a6 --skill a6-recipe-graphql-proxy-api7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GraphQL proxying patterns with a6 enable teams to implement operation-aware routing, REST-to-GraphQL conversion, and security controls across GraphQL APIs, reducing integration friction and deployment toil.

Core Features & Use Cases

  • Operation-based routing using GraphQL variables like graphql_name, graphql_operation, and graphql_root_fields to direct requests to specific backends.
  • Per-operation rate limiting and security patterns (plugins and policies) to protect GraphQL endpoints.
  • REST-to-GraphQL conversion via the degraphql plugin to bridge REST clients with GraphQL backends.
  • Declarative configuration support for reproducible deployments via a6 config sync/diff.

Quick Start

Create a route that uses GraphQL operation variables to route queries to a read backend and mutations to a write backend, then apply a per-operation rate limit.

Frequently Asked Questions about a6-recipe-graphql-proxy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route GraphQL queries and mutations to different backends in an API gateway?

You can route GraphQL operations to dedicated backends by evaluating operation variables like graphql_name, graphql_operation, and graphql_root_fields, allowing queries and mutations to target separate services.

Can I apply rate limiting to specific GraphQL operations instead of the entire endpoint?

Yes, per-operation rate limiting applies security policies to individual GraphQL operations, protecting endpoints by restricting traffic based on the specific query or mutation being executed rather than the aggregate endpoint.

What is the best way to expose a GraphQL backend to REST API clients?

REST-to-GraphQL conversion bridges REST clients with GraphQL backends using the degraphql plugin, translating standard REST requests into GraphQL operations to reduce integration friction without requiring client-side GraphQL adoption.

Do I need the a6 command to configure GraphQL proxy routing patterns?

Yes, a6 command support is required for route creation, config sync, and diff, enabling declarative configuration for reproducible deployments of GraphQL proxy routing, security patterns, and conversion rules.

How does operation-aware routing improve GraphQL API security?

Operation-aware routing improves GraphQL API security by applying granular, per-operation rate limiting and security policies directly to specific queries and mutations, preventing excessive traffic or malicious operations from overwhelming dedicated backends.