GraphQL Support
Saved requests, schema workflows, mock matching, and GraphQL execution details.
GraphQL Support
Bifurc includes first-class GraphQL request and mock workflows, plus schema-aware tooling for exploration and authoring.
What you can do
- save GraphQL requests with endpoint, query, variables, and headers
- introspect schemas from a running endpoint
- store SDL or introspection results in the workspace
- generate starter operations from discovered schema fields
- mock GraphQL responses by endpoint, operation type, and operation name
- use environment variables across endpoints, variables, headers, and scripts
Typical workflow
- Open Request → GraphQL
- Create a request tab
- Enter the endpoint URL
- Introspect the schema or attach a saved schema
- Generate or write a query
- Add variables and headers
- Send the request
- Save it into the workspace for repeat use
Mocking workflow
- Open Mock → GraphQL
- Create a mock
- Match by endpoint pattern
- Choose an operation type:
query,mutation,subscription, orany - Optionally specify an operation name
- Define the response status, headers, and body
- Enable the mock and route traffic through Bifurc
Matching model
GraphQL proxy-level mocking is operation-aware:
- request body must parse as JSON
- Bifurc reads
query,operationName, and variables - operation type is detected from the GraphQL document
- enabled mocks are checked for endpoint and operation compatibility
Good use cases
- frontend work against incomplete backends
- contract testing for specific operations
- mocking mutations without touching production-like services
- keeping reusable GraphQL examples in git-backed workspaces