APIs & Services
Matching API

Example queries

17min

This page lists a set of example queries which can be used as a starting point when working with the Matching API.

The ClientSuppliedId is a field required to use the Matching API. It is a unique alphanumeric string assigned to each input record, which allows you to correlate your record to the Altrata returned record.

Query

Submit queries to create a Matching job and be returned a requestId to retrieve the results.

Persons Match

Submit a set of Person objects to be matched by name and organization name.

clientSuppliedId, firstName, lastNameand organizationNameare mandatory input fields.

GraphQL


Person by ID Match

The personByIdMatch query allows you to match records via unique ids. The API accepts the following id schemes:

  • altrataId
  • clientSuppliedId
  • bxPersonId
  • rsPersonId
  • workEmail
  • linkedinProfile
  • wxPersonId
  • briPersonId
  • wePersonId

clientSuppliedId is a mandatory input along with at least one of the fields. Input schemes may be mixed, that is, within one request you may match on (for example) workEmail and linkedinProfile.

If multiple ID schemes are passed within a single array element, and these result in multiple matches, the API will return these matches as discrete PossibleMatches.

The following example matches a single record by email. The email to match is [email protected] and the ID

GraphQL


The following example matches multiple records by email:

GraphQL


The following example mixes multiple ID schemes:

GraphQL


Organization Match

Submit a set of Organization objects to be matched by name.

GraphQL


Organization by ID Match

Submit a set of Organization objects to be matched by Altrata IDs.

The organizationByIdMatch query allows you to match records via unique ids. The API accepts the following id schemes:

  • altrataId
  • clientSuppliedId
  • bxOrganizationId
  • rsOrganizationId
  • workEmail
  • linkedinProfile
  • wxOrganizationId
  • briOrganizationId

clientSuppliedId is a mandatory input along with at least one of the fields.

GraphQL


Status

Check the current status of a Matching job. The job is ready for results retrieval when the status is Matched Results Available.

GraphQL


You must change the requestId to be the requestId which was returned to you previously.



Results

Retrieve results for a Matching job. Three queries will be required:

1

personUniqueMatches to obtain all Unique Matches

2

personPossibleMatches to obtain all Possible Matches

3

personNoMatches to obtain all No Matches

4

Once results are obtained, you may wish to connect to the Profile API to obtain further information on your matched results

Each response may be paginated. See Paging to learn how to page over the results. Each of the above queries contains a jobSummary object which will provide the overall match statistics of your job.

Person Unique Matches

Retrieve paginated unique matches for a given Matching job.

GraphQL


Person Possible Matches

Retrieve paginated possible matches for a given Matching job.

GraphQL


Person No Match

Retrieve paginated results that were not matched.

GraphQL


Organization Unique Matches

Retrieve paginated unique matches for a given Matching job.

GraphQL


Organization Possible Matches

Retrieve paginated possible matches for a given Matching job.

GraphQL


Organization No Match

Retrieve paginated results that we were unable to match.

GraphQL