Unify and manage your data

Scan match statistics using filter

Learn how to scan Autopilot match statistics using filters with cursor-based pagination, filtering, and sorting.

The Scan Autopilot match statistics API retrieves Autopilot match statistics using pagination. It supports advanced filtering, sorting, and querying through expressions.

The API returns results in pages and includes a scrollId in each response. You use this scrollId in subsequent requests to retrieve the next set of results. This approach enables efficient traversal of filtered and sorted datasets.

HTTP method and endpoint

Use the following HTTP method and endpoint path to submit the request:

POST /configuration/{tenantId}/autopilot/stats/_scan?filter={filter}&limit={limit}&sort={sort}&order={order}

This endpoint scans Autopilot match statistics and returns results in pages, with support for filtering and sorting.

The following table describes the endpoint path parameters.

ParameterTypeRequiredDescription
tenantIdStringYesTenant identifier

Query parameters

The following table describes the query parameters.

ParameterTypeRequiredDescriptionAccepted values / Default
filterStringNofilter expression
limitIntegerNoPage sizeDefault: 100, max: 100
sortStringNoSort field name
orderStringNoSort orderasc or desc

Request headers

The following request headers must be included.

HeaderValueRequired
AuthorizationBearer {token}Yes

Request body

For the first request, omit the request body or send null. For subsequent requests, pass the scrollId returned by the previous response in the request body. For example, use the scroll ID: "xyz" in the next request to retrieve the following set of results.

Response body

The following table describes the fields returned in the response body.

FieldTypeDescription
scrollIdStringIdentifier used to retrieve the next set of results in the current scroll session.
valuesArrayList of result objects returned in the response.
tenantIdStringTenant identifier associated with the result.
lookupTypeStringName of the lookup type.
sourceStringSource system or origin of the unmapped value.
unmappedValueStringOriginal source value that did not previously have a lookup mapping.
candidateLookupCodeStringLookup code selected as the candidate for mapping.
candidateValueStringDisplay value of the selected lookup candidate.
semanticScoreNumberSimilarity score assigned to the candidate match.
centroidMatchBooleanIndicates whether the candidate matched the centroid-based comparison logic.
currentFrequencyNumberObserved frequency of the unmapped value in the current evaluation window.
requiredFrequencyNumberMinimum frequency threshold required before the value can be mapped automatically.
frequencyAtMappingNumberFrequency count recorded at the time the mapping was created.
frequencyWindowHoursNumberTime window, in hours, used to calculate source frequency.
statusStringStatus of the mapping result.
mappedAtNumberTimestamp, in epoch milliseconds, when the value was mapped.
mappedByStringUser that created the mapping.
createdAtNumberTimestamp, in epoch milliseconds, when the result record was created.
sourceFrequencyObjectFrequency summary for the unmapped value.
sourceFrequency.totalCountNumberTotal number of times the unmapped value appeared in the evaluated period.
sourceFrequency.hourlyFrequencyObjectHourly breakdown of observed frequency, keyed by epoch-millisecond time buckets.
updateDateNumberTimestamp, in epoch milliseconds, when the result was last updated.
aiConfidenceNumberConfidence score assigned by the AI model for the proposed mapping.
aiReasoningStringExplanation of why the candidate value was selected as a match.
dcrIdStringIdentifier of the data change request (DCR) associated with the mapping result, if applicable.
configVersionNumberVersion of the configuration used when the mapping decision was generated.

Response body

The following example shows a successful response.

{
    "scrollId": "xyz",
    "values": [
        {
            "tenantId": "my_tenant",
            "lookupType": "Specialty",
            "source": "Reltio",
            "unmappedValue": "Cardiovascular Medicine",
            "candidateLookupCode": "Cardiology",
            "candidateValue": "Cardiology",
            "semanticScore": 0.8898679,
            "centroidMatch": false,
            "currentFrequency": 5,
            "requiredFrequency": 1,
            "frequencyAtMapping": 5,
            "frequencyWindowHours": 1,
            "status": "AUTOMAPPED",
            "mappedAt": 1775474337868,
            "mappedBy": "SYSTEM",
            "createdAt": 1775474334659,
            "sourceFrequency": {
                "totalCount": 5,
                "hourlyFrequency": {
                    "1775473200000": 5
                }
            },
            "updateDate": 1775474337868,
            "aiConfidence": 0.92,
            "aiReasoning": "Cardiovascular Medicine is an alternate name for the specialty of Cardiology, which deals with diseases of the heart and blood vessels.",
            "configVersion": 1
        },
        {
            "tenantId": "my_tenant",
            "lookupType": "Specialty",
            "source": "Reltio",
            "unmappedValue": "Cardiovascular Specialist",
            "candidateLookupCode": "Cardiology",
            "candidateValue": "Cardiovascular Medicine",
            "semanticScore": 0.8819044,
            "centroidMatch": false,
            "currentFrequency": 30,
            "requiredFrequency": 1,
            "frequencyAtMapping": 30,
            "frequencyWindowHours": 1,
            "status": "MANUALLY_MAPPED",
            "mappedAt": 1775474666342,
            "mappedBy": "your_user",
            "createdAt": 1775474542454,
            "sourceFrequency": {
                "totalCount": 30,
                "hourlyFrequency": {
                    "1775473200000": 30
                }
            },
            "updateDate": 1775474666342,
            "aiConfidence": 0.92,
            "aiReasoning": "The unmapped value 'Cardiovascular Specialist' refers to the same specialty as the candidate 'Cardiovascular Medicine', which has the code 'Cardiology'.",
            "dcrId": "93ceaf7e-f035-469e-89be-6a88a823c092",
            "configVersion": 2
        }
    ]
}