JSON to Kotlin (Gson) Converter

How to use

1. Paste a representative JSON payload that reflects the real API structure.
2. Review the generated Kotlin model classes, nested types, and Gson annotations.
3. Copy the output into your Kotlin project and refine nullability or package naming as needed.

Benefits

• Speeds up Kotlin model generation for Android and JVM services.
• Preserves tricky JSON keys through Gson annotation-based mappings.
• Reduces manual data class authoring for nested payloads.

Best use cases

• Android projects using Retrofit with Gson converters.
• Kotlin services that consume third-party JSON APIs.
• Teams moving from handwritten DTOs to generated model scaffolds.

Kotlin Gson tips

• Review nullability carefully when APIs return optional or partially sparse data.
• Keep the payload sample close to real production responses for better type inference.
• Use generated models as DTOs and map them into domain models where needed.

Implementation tips

• Review Kotlin nullability for fields that may be missing in real responses.
• Keep generated Gson DTOs separate from domain models when layering matters.
• Check key naming for snake_case and symbol-heavy payloads before shipping.

Sample JSON

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

Sample output

// Kotlin (Gson) output preview

FAQ