The resolution endpoints allow users to search for matching entities against a provided list of attributes. The endpoint is similar to the search endpoint, except it’s tuned to only return the best match so the client doesn’t need to do as much or any post-processing work to filter down results.
OAuth authentication of the form <token>.
Entity address. For optimal matching results, it’s recommended to concatenate the full address string (street, city, state, postal code).
Entity type. If multiple values are passed for any field, the endpoint will match entities with ANY of the values.
Specifies the search algorithm to use. corporate (default) is optimized for accurate entity attribute matching, ideal for business verification. suppliers is tailored for matching entities with trade data, suitable for supply chain use cases. search mimics /search/entity behavior, best for name-only matches.
Adding this param enables an alternative matching logic. It sets the minimum number of matching tokens the resolved hits need to have in common with the user input to be considered a “hit”. Accepts non-negative integers.
Specifies the minimum score required to pass, which controls the strictness of the matching threshold. The default value is 77, and tuned for general use-case accuracy. Increase the value for stricter matching, reduce to loosen.
Enables a name search fallback when either the corporate or supplier profiles fails to find a match. When invoked, the fallback will make a call similar to /search/entity on name only. By default set to false.
Bypasses the post-processing setps and re-ranking. Useful for debugging. By default set to false, set to true to enable.
Whether to enable LLM-based data cleaning to remove noise and standardize entity attributes. Defaults to true if not supplied. Set to false to disable LLM cleaning.
