Detect entities such as PII, PHI or PCI in the file located at the provided URI using Private AI's entity detection engine. After entity detection, a copy of the file with all entities removed is created and placed in the folder specified by PAI_OUTPUT_FILE_DIR.
This route is similar to /v3/process/files/base64, but relies on URIs instead of base64-encoded strings. As this route avoids the overhead of base64 encoding, it is more suitable for processing large files and large volumes of data.
This route supports multiple filetypes, with the content type recognized automatically and processed accordingly.
| uri required | string (Uri) URI of the file to be processed. It can be an URL (e.g www.foo.com/files/random-image.jpeg) or an accessible file path on the host machine (e.g. /Users/sam/files/file.pdf). |
object (Entity Detection) This section contains a set of parameters to control the PII detection process. All fields have sensible default that can be changed for specific needs. | |
object (Pdf Options) Options to process PDF files, such as the rendering quality when each page is turned into an image. | |
object (Audio Options) Default: {"bleep_start_padding":0,"bleep_end_padding":0} Options to process audio files, such as the padding to add while redacting audio segments. | |
| project_id | string (Project Id) <= 32 characters ^[a-zA-Z0-9\-_\:]*$ Used to categorize requests for reporting purposes. Limited to alphanumeric characters or the following special characters :_- |
Successful Response
Validation Error
{- "result_uri": "string",
- "processed_text": "string",
- "entities": [
- {
- "processed_text": "string",
- "text": "string",
- "location": {
- "stt_idx": 0,
- "end_idx": 0,
- "stt_idx_processed": 0,
- "end_idx_processed": 0
}, - "best_label": "string",
- "labels": {
- "property1": 0,
- "property2": 0
}
}
], - "entities_present": true
}