All lessons T
Data Transformation beginner 8 min

Normalize API Field Names Before Mapping JSON

Turn human column labels into consistent property names before building a payload mapper.

Scenario

A spreadsheet export arrived with friendly column labels — First Name, Account ID — but the API mapper expects camelCase JSON keys like firstName and accountId. Hand-editing headers is where inconsistencies like AccountID vs accountId creep in, and a mapper that silently drops unmatched keys turns one typo into missing data. Normalize the names once, consistently, before anyone writes a brittle one-off mapping.

Broken input

First Name,Last Name,Account ID,Signup Date

Goal

Use Case Converter to convert display labels into consistent camelCase API field names. One conversion pass beats four manual renames, and it applies the same acronym rule everywhere.

Tool sequence

  1. Open Case Converter.
  2. Paste the header row and pick camelCase (or the casing your API contract actually specifies — check before assuming).
  3. Read the converted output and decide the acronym rule explicitly: Account ID can become accountId or accountID, and mixing the two styles breaks lookups later.
  4. Replace the spreadsheet headers with the converted keys before the file goes anywhere near the mapper.
  5. If the headers feed a CSV import, continue in CSV to JSON; if you suspect duplicate columns, run the list through Line Sort / Unique / Deduplicate first.

Checkpoint output

First Name   → firstName
Last Name    → lastName
Account ID   → accountId
Signup Date  → signupDate

Every label maps to a predictable camelCase key with one consistent acronym rule, so the mapper needs no special cases.

Common mistakes

  • Forgetting that acronyms like ID need a project-wide rule — accountId and accountID are different keys to every JSON parser.
  • Mixing display labels and field keys in the same mapper, so the code works on one export and fails on the next.
  • Normalizing names before checking for duplicate columns, which turns two distinct columns into one silently overwritten key.
  • Converting to the casing you prefer instead of the casing the receiving API documents.

Related tools and lessons