---
title: "GET /api/v1/document/document-field-detectors/{uid}/"
method: GET
path: "/api/v1/document/document-field-detectors/{uid}/"
tags: ["document", "v1"]
---

# GET /api/v1/document/document-field-detectors/{uid}/

`GET /api/v1/document/document-field-detectors/{uid}/`

Retrieve Document Field

## Path parameters

- `uid` string, required

## Query parameters

- `jq_filters` object

## Response `200`

- DocumentFieldDetectorDetail
  - `uid` string, uuid
  - `category` 'simple_config', nullable — Field detector category used for technical needs e.g. for determining which field detectors were created automatically during import process.
  - `field` string, required
  - `field__code` string
  - `field__title` string
  - `field__uid` string
  - `field__type` string
  - `field__document_type__title` string
  - `exclude_regexps` string, nullable — Enter regular expressions, each on a new line, for text patterns you want EXCLUDED. The Field Detector will attempt to skip any Text Unit that contains any of the patterns written here, and will move on to the next Text Unit. Avoid using “.*” and similar unlimited multipliers, as they can crash or slow ContraxSuite. Use bounded multipliers for variable length matching, like “.{0,100}” or similar. Note that Exclude regexps are checked before Definition words and Include regexps. If a Field Detector has Exclude regexps, but no Definition words or Include regexps, it will not extract any data.
  - `definition_words` string, nullable — Enter words or phrases, each on a new line, that must be present in the Text Unit. These words must be in the Definitions List. If ContraxSuite fails to recognize these words as definitions, then the Field Detector skips and moves to the next Text Unit. If there are Include regexps, then the Field Detector checks against those requirements. The Field Detector marks the entire Text Unit as a match. Note that the Field Detector checks for definition words after filtering using the Exclude regexps.
  - `include_regexps` string[]
  - `regexps_pre_process_lower` boolean — Set 'ignore case' flag for both 'Include regexps' and 'Exclude regexps' options.
  - `detected_value` string, nullable — The string value written here will be assigned to the field if the Field Detector positively matches a Text Unit. This is only applicable to Choice, Multichoice, and String fields, as their respective Field Detectors do not extract and display values from the source text.
  - `extraction_hint` 'TAKE_FIRST' | 'TAKE_SECOND' | 'TAKE_LAST' | 'TAKE_MIN' | 'TAKE_MAX', nullable — Provide additional instruction on which specific values should be prioritized for extraction, when multiple values of the same type (e.g., Company, Person, Geography) are found within the relevant detected Text Unit.
  - `text_part` 'FULL' | 'BEFORE_REGEXP' | 'AFTER_REGEXP' | 'INSIDE_REGEXP' — Defines which part of the matched Text Unit should be passed to the extraction function. Example: In the string "2019-01-23 is the start date and 2019-01-24 is the end date," if text part = "Before matching substring" and Include regexp is "is.{0,100}start" then "2019-01-23" will be parsed correctly as the start date.
  - `detect_limit_unit` 'NONE' | 'UNIT' — Choose to add an upward limit to the amount of document text ContraxSuite will search for this Document Field. For example, you can choose to only search the first 10 paragraphs of text for the value required (this often works best for values like “Company,” “Execution Date,” or “Parties,” all of which typically appear in the first few paragraphs of a contract).
  - `detect_limit_count` integer — Specify the maximum range for a bounded search. Field detection begins at the top of the document and continues until this Nth "Detect limit unit" element.

---

[API](https://skmtc.net/lexpredict/apis/contraxsuite-api.md) · [All operations](https://skmtc.net/lexpredict/apis/contraxsuite-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lexpredict/contraxsuite-api/versions/3429f921b4cb/schema)