Unify and manage your data

Get Configuration history by Version

Learn how the API retrieves a specific version of Autopilot configuration for a tenant.

The Get Configuration history by version API retrieves a specific historical version of the Autopilot configuration for a tenant. The service returns the configuration that corresponds to the requested version number.

You can use this Autopilot API to review past configurations and compare versions. The service retrieves a selected version from stored configuration history without affecting the active configuration.

HTTP method and endpoint

Use the following HTTP method and endpoint path to retrieve a specific version of the Autopilot configuration:

GET /configuration/{tenantId}/autopilot/history/{version}

The following table describes the endpoint path parameters.

ParameterTypeRequiredDescription
tenantIdStringYesTenant identifier
versionIntegerYesVersion number to retrieve

Request headers

The following request headers must be included.

HeaderValueRequired
AuthorizationBearer {token}Yes

Request Body

This operation does not require a request body.

Response body

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

FieldTypeDescription
tenantIdStringUnique identifier of the tenant.
defaults
defaultsObjectDefault Autopilot configuration settings applied at the tenant level.
enabledBooleanIndicates whether Autopilot is enabled.
modeStringOperating mode of Autopilot (for example, ACTIVE or PREVIEW).
autoMapEnabledBooleanIndicates whether automatic mapping is enabled.
autoMapThresholdNumberMinimum similarity score required for automatic mapping.
suggestionEnabledBooleanIndicates whether mapping suggestions are enabled.
suggestionThresholdNumberMinimum score required to generate a mapping suggestion.
createLookupEnabledBooleanIndicates whether automatic creation of new lookup values is enabled.
createLookupThresholdNumberMinimum score required to automatically create a new lookup value.
suggestLookupEnabledBooleanIndicates whether suggestions to create new lookup values are enabled.
suggestLookupThresholdNumberMinimum score required to suggest creating a new lookup value.
misspelledThresholdNumberMinimum score used to detect potential misspellings.
requiredFrequencyNumberMinimum number of occurrences required before Autopilot takes action.
frequencyWindowHoursNumberTime window, in hours, used to evaluate frequency.
lookupTypes
lookupTypesArrayList of lookup type-specific configurations. Empty if no overrides are defined.
updatedByStringIdentifier of the user who last updated the configuration.
updateDateNumberTimestamp of the last update in epoch milliseconds.
versionNumberVersion number of the configuration.
anyEnabledBooleanIndicates whether Autopilot is enabled for any scope.

Example response

The following example shows a response body with the tenant-level default matching configuration, lookup type settings, and audit metadata.

{
    "tenantId": "my_tenant",
    "defaults": {
        "enabled": true,
        "mode": "ACTIVE",
        "autoMapEnabled": true,
        "autoMapThreshold": 0.9,
        "suggestionEnabled": true,
        "suggestionThreshold": 0.8,
        "createLookupEnabled": true,
        "createLookupThreshold": 0.9,
        "suggestLookupEnabled": true,
        "suggestLookupThreshold": 0.75,
        "misspelledThreshold": 0.7,
        "requiredFrequency": 1,
        "frequencyWindowHours": 1
    },
    "lookupTypes": [],
    "updatedBy": "my_user",
    "updateDate": 1775474092854,
    "version": 1,
    "anyEnabled": true
}