How JSONs Are Processed
Similar to XML files, JSON files are processed using the method described in the Structured Data Guide. The output file retains its original format with redaction markers of the format “[LABEL_X]” in place of the detected PII. The file passed in should adhere to the JSON standard as defined.Constraints
Please consider writing a handler for your specific application using the Structured Data Guide to get around any of the constraints listed below.
- The file processing routes are synchronous; large files over 5MB in size may take a long time to process.
- Only values are redacted. Key names are assumed to never contain PII and are not redacted.
- Entity detection numbering is consistent within individual values only, not across the entire file.
- The JSON must be entirely human-readable content. Encoded content such as Base64 is not natively supported and may lead to inaccurate PII detection. Please process this content separately.
- Due to the way the data is formatted, deeply hierarchical (>10 levels) JSON structures take proportionally longer to process.
Support Matrix
| CPU Container | GPU Container | Community API | Professional API | |
|---|---|---|---|---|
| Supported | Yes | Yes | Up to 250 KiB | No |
Sample Request
Connect with one of our privacy experts to run this code.
Sample Response
Response