Teams adopting GraphQL rarely start from a blank page — they usually have existing REST endpoints returning JSON. This converter takes a sample JSON response and drafts GraphQL schema definition language from it, turning objects into type definitions with typed fields so you can bootstrap a schema instead of writing SDL from scratch.
It is a practical shortcut when wrapping a legacy REST API behind a GraphQL gateway, and a fast way to sketch types during API design discussions: paste the payload you are debating and the corresponding type definitions appear instantly, ready to refine as a team.
Your API payloads are processed exclusively by code running in this browser tab. There is no server component listening on the other end, so response samples containing user data never leave the device you are working on.
Field types are inferred from your sample values and mapped to the built-in scalars: String, Int, Float, and Boolean. Values the tool cannot classify more precisely default to String, which you can refine by hand.
Each nested object becomes its own named type definition, and the parent field references that type. Arrays of objects become list types wrapping the generated type, mirroring how GraphQL schemas naturally compose.
No. It produces type shapes only. Deciding which fields are non-null and how each field is resolved requires knowledge of your backend, so those parts remain yours to write.