v50

latestOpenAPI 3.1.0raw.githubusercontent.com2026-07-031984301.2 MB
PerfectMatch Mapping

Create PerfectMatch Mapping

For more details on the PerfectMatch feature please consult the official documentation.

After creating a mapping, target files from the matchingProjects are automatically matched to the source files in the new project. This is a long-running background operation, and its status can be tracked by polling the Get PerfectMatch Mapping endpoint.

post/perfect-match-mappings

Query parameters

fieldsstring

A comma separated list of fields to include in the response. Every value in the list should either consist of a top-level property name (excluding the items envelope for endpoints returning lists) or refer to a property of a top-level property of type object, in the following form: "toplevelpropertyname.subpropertyname". When this query parameter is omitted, default resource representations are returned (excluding fields marked as optional). The same applies to nested objects when just specifying the top-level property name, without explicitly listing sub-property names. When specifying the fields query parameter, only the specified fields are returned. The id property is always returned.

Headers

Authorizationstring required

The bearer access token provided by Auth0.

X-LC-Tenantstring required

The identifier of the account where the request is executed.

Request body

projectIdstring required

The project identifier this mapping will be used on.

matchingProjectsstring[]

A collection of projects that will be used to find matches and candidates for PerfectMatch mapping.

Response

Created

idstring required

The mapping identifier.