Include from_json() deserializer Use std::optional for nullable fields

Features

⚙️ Modern C++ Types

std::string for string fields
std::vector<T> for arrays
std::optional<T> for nullable fields
Nested struct generation

📦 nlohmann/json

from_json() deserializers
j.at("key").get_to(field) pattern
Header-only library support
Automatic #include headers

🔧 Type Mapping

JSON integer → int
JSON float → double
JSON boolean → bool
JSON null → std::optional

C++ nlohmann/json Guide

Using nlohmann/json

nlohmann/json is a popular header-only C++ library for JSON. Add it to your project and define from_json() for automatic deserialization.

// Install via CMake or download single header:
// https://github.com/nlohmann/json/releases
// #include <nlohmann/json.hpp>

#include <string>
#include <nlohmann/json.hpp>

struct User {
    int id;
    std::string name;
    bool active;
};

void from_json(const nlohmann::json& j, User& o) {
    j.at("id").get_to(o.id);
    j.at("name").get_to(o.name);
    j.at("active").get_to(o.active);
}

// Usage:
// nlohmann::json j = nlohmann::json::parse(jsonString);
// User u = j.get<User>();

Parsing JSON in C++

#include <iostream>
#include <nlohmann/json.hpp>

int main() {
    std::string jsonStr = R"({"id":1,"name":"Alice","active":true})";
    nlohmann::json j = nlohmann::json::parse(jsonStr);

    User u = j.get<User>();
    std::cout << u.name << std::endl;

    // Serialize back
    nlohmann::json out = u;  // requires to_json()
    std::cout << out.dump(2) << std::endl;
    return 0;
}

Common Use Cases

REST API clients: Deserialize HTTP JSON responses into typed C++ structs
Game engines: Load configuration and asset metadata from JSON files
Embedded systems: Parse sensor data and telemetry in C++ firmware
Data pipelines: Process JSON records in high-performance C++ applications
Config files: Read application settings from JSON configuration files

FAQ

Q: When should I use std::optional?

A: Use std::optional<T> for fields that may be null or missing in the JSON. nlohmann/json handles optional fields gracefully when you check with j.contains("key") before getting.

Q: What C++ standard is required?

A: std::optional requires C++17 or later. For C++14 compatibility, disable the optional option and handle nullable fields manually.

Q: How do I handle nested objects?

A: Nested JSON objects generate separate C++ structs with their own from_json() functions. nlohmann/json calls these automatically during deserialization.

Practical notes for C++ JSON models

nlohmann/json makes JSON feel native in modern C++, and generated structs with to_json and from_json let you convert whole objects in one line. A few details matter once the code runs against real data.

Tips and common pitfalls

Use j.at("key") when a field is required (it throws if missing) and j.value("key", default) when it is optional.
The NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE macro can replace hand-written conversion functions for simple structs.
Catch nlohmann::json::exception around parsing untrusted input; malformed JSON throws parse_error.
For very large or performance-critical payloads, consider simdjson or RapidJSON, which parse much faster at the cost of convenience.

JSON to C++ Struct Generator