Online Tool Store
REST to GraphQL Mapper
REST to GraphQL Mapper produces the mechanical half of the schema; the relationships between types are the part worth designing yourself.
🔒 This tool runs entirely in your browser. Your files are never uploaded to a server.
Developer
REST to GraphQL Mapper
Frontend preview — no upload or external service.
Draft GraphQL schema
Three endpoints become a User type, a users query returning [User!]!, a user(id: ID!) query, and a createUser mutation taking a CreateUserInput.
How the REST to GraphQL Mapper works
- List your REST endpoints, one per line, with method and path.
- Choose whether to generate mutations as well as queries.
- Treat the output as a first draft — the interesting part of a GraphQL schema is the relationships between types, which REST paths do not describe.
FAQ
Can a REST API be converted automatically?
The endpoint list gives you queries and mutations, and that is the easy half. The value of GraphQL is in the graph — how types relate — and no path list encodes that. Expect to design the relationships by hand.
What about the N+1 problem?
A schema that resolves each field with its own REST call will make one request per item per field. That is the standard GraphQL pitfall, and it is solved with batching via DataLoader rather than in the schema.
Should every REST endpoint become a field?
No. A REST API often has endpoints that exist to work around REST's shape — bulk fetches, denormalised views, compound updates. Those usually disappear in a well-designed graph.
How we compare
| Feature | Online Tool Store | A CLI script | An IDE plugin |
|---|---|---|---|
| Queries and mutations | ✓ | ✗ | ✓ |
| Nothing uploaded | ✓ | Local | ✗ |
| Suggests input types | ✓ | ✗ | ✓ |
| No install | ✓ | ✗ | ✗ |
REST to GraphQL Mapper produces the mechanical half of the schema; the relationships between types are the part worth designing yourself.