Example Advanced Match Request Parameter Sets
matchConfidenceThreshold is configured in the Markaaz Enterprise Partner Portal (EPP) UI with a default of 8.3. This value can be changed by users in the UI and used for all Advanced Match requests, or an override value can be passed per request via matchConfidenceThresholdOverride.
Onboarding Verification, closest match (fully automated)
Scenario: You want the single best match and automated decisioning based on whether or not a match is found per your matchConfidenceThreshold setting.
"matchCount": 1
"showNonMatches": false
"showGrades": true
"matchConfidenceThresholdOverride": nullOnboarding Verification, small business (broader review)
Scenario: Sole‑props/micro‑SMBs may require evaluating sub‑threshold candidates. showNonMatches will bypass the configured matchConfidenceThreshold, returning businesses regardless of score.
"matchCount": 10
"showNonMatches": true
"showGrades": true
"matchConfidenceThresholdOverride": nullOnboarding Verification, manual review
Scenario: Agents want to review the top n businesses at/above the configured matchConfidenceThreshold. In this example n = 10.
"matchCount": 10
"showNonMatches": false
"showGrades": true
"matchConfidenceThresholdOverride": nullDynamic risk bands (programmatic override)
Scenario: Use your own defined low/med/high bands to flex threshold programmatically per API request; always combine the returned score with grades metadata. For example, set a dynamic matchConfidenceThresholdOverride based on country.
"matchCount": 1
"showNonMatches": false
"showGrades": true
"matchConfidenceThresholdOverride": {per-request value}Updated 8 days ago