JSON to Elixir Converter

How to use

1. Paste a representative JSON payload that matches the response, event, or config shape your Elixir code actually consumes.
2. Review the generated `defmodule` blocks, `%__MODULE__{}` type specs, and inferred field types for nested data.
3. Copy the output into your project and add decoder, changeset, or domain-specific helpers where your app needs them.

Benefits

• Produces Elixir struct modules that are easier to reason about than ad hoc map traversal.
• Gives Phoenix and service codebases a typed starting point before hand-written parsing or validation layers.
• Keeps nested payload structure explicit through generated child modules and list types.

Best use cases

• Phoenix apps that want transport structs before mapping payloads into contexts or changesets.
• Elixir services and jobs that repeatedly parse external JSON into predictable shapes.
• Teams replacing loose maps with clearer module-based data contracts.

Elixir struct tips

• Treat generated structs as transport models first, then layer Ecto schema or validation logic separately.
• Use realistic JSON samples so optional fields, nested modules, and list shapes are inferred accurately.
• Add parser or decoder helpers after generation because this route focuses on struct and type-spec scaffolding.

Sample JSON

{
  "id": 101,
  "name": "Ada Lovelace",
  "active": true,
  "roles": ["admin", "editor"],
  "profile": {
    "email": "ada@example.com",
    "score": 9.8
  }
}

Sample Elixir output

defmodule UserModel do
  @type t :: %__MODULE__{
    id: integer(),
    name: String.t(),
    active: boolean(),
    roles: [String.t()]
  }

  defstruct [:id, :name, :active, :roles]
end

FAQ