JSON Field Redactor by Key

Redact explicitly named JSON object fields at any nesting depth, including objects inside arrays. Export transformed records and redaction counts without copying original field values into diagnostics.

When to use it

Remove known credential or contact fields from authorized structured exports before sending the transformed output to later workflow steps.

Price

$0.03 per completed report, for supported paying Apify users. One report-generated event, after files and a summary are stored. No per-row, per-URL or dataset-item charge. Invalid input and processor timeouts do not trigger the report event. Apify’s free-user rules and any separately applicable platform charges are governed by Apify.

Use a maximum charge limit that covers at least one report. No external AI models or API keys are needed.

Example input

{
  "recordsJson": "[{\"id\":\"001\",\"email\":\"demo@example.test\",\"profile\":{\"password\":\"demo-private\",\"city\":\"Paris\"}},{\"id\":\"002\",\"api_key\":\"demo-token\"}]",
  "fieldNames": [
    "password",
    "api_key",
    "email"
  ],
  "caseSensitive": false,
  "replacement": "[REDACTED]"
}

Results

• REPORT.json: complete summary, full records and bounded details.
• RECORDS.csv: all output records. Formula-like cells are escaped for spreadsheets; JSON is the authoritative typed result.
• REPORT.html: self-contained escaped report, with at most 20 output records in the preview.

RECORDS.json is a full JSON array; RECORDS.jsonl has one full object per newline. Both contain all output records.

The default dataset contains a single operational summary; it is not the records export. Download JSON or CSV for full output.

Limits and behavior

All text inputs are inline; no remote fetching or AI calls. Each source string is limited to 2 MiB UTF-8; total input envelope 5 MiB. Parsed JSON depth 32, at most 100,000 value nodes, at most 100 fields per object, nonempty field names up to 256 UTF-8 bytes. Duplicate JSON fields, non-finite numbers and decimals that would silently lose float precision are rejected. Maximum 10,000 input records total unless a smaller product limit is stated. Exports have at most 100 union columns and a combined 10 MiB size limit, which can be reached before the input limit. JSON and JSONL preserve typed values; CSV is escaped for spreadsheets. JSON formatting, whitespace and numeric spelling are not retained. Large integer values are retained within Python input limits; downstream consumers must support them. This is explicit key-based redaction, not a PII detector, anonymizer or compliance guarantee. Sensitive values under other keys, inside unstructured text, or inside key names remain unless the user selects the matching keys. Original INPUT is still stored in the user’s Apify run storage; transformation does not erase it. Inspect access and retention before processing sensitive data. Diagnostics contain counts only, not original matched values.

All products have a 25-second processor deadline, 256 MiB container memory, a 60-second run timeout and a combined 10 MiB export limit. Large or wide inputs may hit the export limit before the row limit. Failed exports do not charge the report event. No automatic restarts are enabled.

Privacy and operation

Use only data you are authorized to process. Inline data and outputs are stored in your run’s Apify storage under its configured access and retention settings. This Actor does not fetch external resources or invoke a model, and does not log source values. Review your own storage sharing and retention settings for sensitive inputs.

Billing uses a durable checkpoint. If a charge response is uncertain, the same run stops for ledger review instead of retrying payment automatically. Start a new run only after inspecting the earlier attempt. Report a problem through Apify’s Actor issue tracker with sanitized examples; do not post private records or tokens.