Introducing GraphQLBridge: Use Your Existing .NET REST APIs as a GraphQL Server — No Resolvers Needed!

Have you ever wanted to expose your existing ASP.NET Core controllers as a GraphQL API without rewriting a single line of business logic? GraphQLBridge makes that possible — no resolvers, no boilerplate, and no magic. Just annotate your existing controller methods, and you instantly have a working GraphQL endpoint.

🧠 Why GraphQLBridge?

Most GraphQL solutions for .NET require writing a separate schema, resolvers, and wiring everything up manually. This can be painful when you already have a well-structured set of RESTful APIs.

With GraphQLBridge, you can:

• ✅ Reuse your existing [Controller] and [Http...] methods
• ✅ Map GraphQL queries and mutations using attributes
• ✅ Automatically parse fragments, variables, and input types
• ✅ Skip writing resolvers — we bridge GraphQL to your .NET methods for you

🤯 What’s Under the Hood?

• Parses incoming GraphQL query using GraphQLParser
• Matches operation names to your controller methods via [GraphQLBridgeResolver]
• Converts fragments, variables, and input types to match method parameters
• Uses reflection to invoke methods with accurate binding

🔒 Bonus
Works seamlessly with standard .NET auth, middlewares, and model validation — it’s just your controller being called under the hood!

📦 Try It Out
Try GraphQLBridge right away without any schema definitions:

👉 Graphql Bridge

Share and Like! 👍