Skip to main content

GraphQL Libraries

You can make GraphQL requests with any HTTP client — the API is just a POST endpoint. That said, dedicated GraphQL libraries can simplify things like query building, caching, and error handling.

Any Language

The Legalesign GraphQL API is a standard HTTP endpoint. Any language that can make a POST request with a JSON body and an Authorization header will work. No vendor-specific SDK is required — see the authentication guide.

JavaScript / Node.js

fetch (built-in)

Node.js 18+ and all modern browsers include fetch natively. This is the simplest option and what the Node.js tutorial uses — no dependencies needed.

graphql-request

Lightweight, promise-based GraphQL client. Good for simple scripts and server-side code.

https://www.npmjs.com/package/graphql-request

Apollo Client

Full-featured client with caching, React integration, and state management. Powerful but may be overkill if you only need a few API calls.

https://www.apollographql.com/docs/react

AWS Amplify

If you're building a web application with a user login flow, Amplify provides authentication and GraphQL support together.

https://docs.amplify.aws

Python

requests

The standard HTTP library. Works well for GraphQL — just POST a JSON body. This is what the Python tutorial uses.

https://docs.python-requests.org

gql

A dedicated GraphQL client for Python with query validation, transport options, and async support.

https://github.com/graphql-python/gql

C# / .NET

HttpClient (built-in)

.NET's built-in HttpClient works well for GraphQL. This is what the C# tutorial uses — no additional packages needed.

GraphQL.Client

A dedicated .NET GraphQL client with typed responses and serialization support.

https://github.com/graphql-dotnet/graphql-client