How XML Files Are Processed
Similar to JSON files, XML 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.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 node text contents and attributes are redacted. Node names are assumed to not contain PII and are not redacted.
- Entity detections numbering is consistent within individual values only, not across the entire file.
- The XML 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.
- External sources, such as hyperlinks, images, and references (including custom schemas) in the XML are not loaded, processed, or redacted and will be handled verbatim as text. If you require this type of data to be handled in the XML, please consider writing your own handler.
- Because tag and element values are modified, it is possible for the de-identified XML to not match the original file schema. For example,
<money currency="US">23</money>will be redacted as<money currency="[LOCATION_COUNTRY]">[MONEY]</money>. Please adjust the enabled entity types for your needs.
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