Skip to main content

Lookup – Added

New optional tags property (list of strings) on lookup (reference data list) versions, so lists can be categorised (for example KYC). Tags are accepted when creating or updating a lookup version and are returned on full lookup version responses. When tags is omitted or null on an update, the existing tags are kept; when a new version is created without tags, it inherits the tags of the active version; sending [] clears them. Tags are trimmed and de-duplicated (case-insensitively) before being stored. Each version can have at most 20 tags, each 1–50 characters of letters, digits, hyphens and spaces; invalid tags return 400 Bad Request. Existing lookups return an empty list, so this change is fully backward compatible. (AB#554576)

Affected Endpoints​

  • POST /lookupcommand/api/lookup
  • POST /lookupcommand/api/lookup/items
  • POST /lookupcommand/api/lookup/{lookupId}
  • POST /lookupcommand/api/lookup/{lookupId}/items
  • PUT /lookupcommand/api/lookup/{lookupId}/version/{versionNumber}
  • PUT /lookupcommand/api/lookup/{lookupId}/version/{versionNumber}/items
  • GET /lookupquery/api/lookup/{lookupId}
  • GET /lookupquery/api/lookup/{lookupId}/version/{versionNumber}
  • GET /lookupquery/api/lookup/name/{lookupName}
  • POST /lookupquery/api/lookup/versions
  • POST /lookupquery/api/lookup/{lookupId}/column-filter