Zum Hauptinhalt springen

Create Config

POST 
/configs

Create a new config in the API key's project.

The name must be unique within the project. kind selects the config type and the shape of parameters, which is validated against that kind. For invoice-v2: the inline extraction_config.schema must be a well-formed JSON object schema, and every matcher's dataset_id, column and resolved scalar field path must exist. For redaction: default_custom_terms holds at most 50 terms of up to 200 characters each; terms are trimmed and de-duplicated case-insensitively.

Mapping roles (matchers[].mappings[].role, optional — defaults to auto):

  • identifier — must-match: a row qualifies only if the extracted value equals the column exactly (raw comparison, no normalization). Multiple identifiers AND together; an identifier whose extracted value is empty constrains nothing.
  • descriptive — scored text signal; abbreviations, word order and language differences are expected.
  • numeric — scored number signal; small rounding differences are tolerated.
  • auto — scored signal weighed at the matching engine's discretion; never a hard constraint.

A row counts as a match when its score reaches the matcher's min_score; rows are ordered by score and capped at limit.

Request​

Responses​

Config created successfully