Clean API Responses: Remove Nulls, Trim Whitespace, Normalize JSON

API responses can be valid JSON and still be full of noise that makes downstream systems fragile.

Third-party payloads often include null values, empty strings, padded text, empty arrays, and optional fields that do not matter for your workflow.

This guide shows how to clean API responses with Forge Json so the output is easier to store, compare, and send into another API step.

This is a common pattern when you need to normalize JSON for databases, queues, automation workflows, or review tools.

This guide is for developers, automation builders, and data teams working with third-party API payloads.

Before and After

Before: user profile data with extra whitespace and empty optional fields

{
  "users": [
    {
      "name": "  Alice Johnson  ",
      "phone": null,
      "bio": "Software engineer   ",
      "tags": []
    }
  ]
}

After: compact user data that is easier to store and compare

{
  "users": [
    {
      "bio": "Software engineer",
      "name": "Alice Johnson"
    }
  ]
}

If you also need to transform e-commerce orders or merge JSON configuration files, the same pipeline approach can help you turn unreliable input into reusable output.

Why API JSON Gets Messy

Third-party APIs often serve general-purpose payloads. One endpoint may support many clients, product states, and optional profile fields, so the response includes placeholders that are not useful for your workflow.

That becomes painful when you need:

• clean records for storage or search
• stable output for comparing changes over time
• fewer empty values before sending data downstream
• predictable JSON for automation pipelines

Without a repeatable cleanup workflow, this usually turns into scattered cleanup code that is hard to audit and easy to forget.

The raw JSON example below shows user records with padded strings, null values, empty strings, empty arrays, and nested optional fields.

How to Fix It with Forge Json

Forge Json's Clean JSON utility can apply a practical cleanup workflow from a small set of explicit rules.

You can copy this setup directly:

{
  "removeNulls": true,
  "removeEmptyStrings": true,
  "removeEmptyArrays": true,
  "trimStrings": true,
  "sortKeys": true
}

For this example, the workflow produces a short set of useful steps:

1. Remove null fields such as phone and apartment.
2. Remove empty strings and empty arrays that do not carry useful data.
3. Trim padded strings and sort keys for stable output.

Result

You end up with:

• trimmed strings
• fewer empty optional fields
• stable key ordering
• cleaner JSON for storage, automation, or review

If the cleanup removes too much, run it again with fewer rules enabled. Smaller cleanup passes are usually easier to review and safer to reuse.

The support material below shows the raw API response, cleanup configuration, and final cleaned output.

This pattern works well for API response cleanup and can be reused across similar JSON workflows.

Related JSON workflows:

• transform JSON
• merge JSON
• JSON pipelines

Use the example panel below to open this sample input and generated workflow directly in the editor.

FAQ

How do I remove null values from JSON?

You can remove null values by filtering fields programmatically or using a JSON cleanup tool that removes empty or unused fields automatically.

Why should I clean API responses?

Cleaning API responses reduces bugs, simplifies downstream logic, and ensures consistent data for storage and processing.

What is JSON normalization?

JSON normalization means transforming data into a consistent structure by removing noise, standardizing fields, and formatting values predictably.