The Match endpoint accepts plaintext (raw) PII as input data.

When you send plaintext PII to the Match endpoint, data normalization and fuzzy matching occurs during the matching process. A sequence of matching steps, using the "match cascade", is used until a match to a maintained RampID is found.

If a maintained RampID is not found after all match cascade steps are performed, a derived RampID is returned. The response also includes insights about that record and metadata about how the match was obtained when using the Match endpoint.

All calls to the Match endpoint must be structured as batch request calls. Make a POST call to and pass in a JSON array of URL strings that start with /people/ and that contain the appropriate body parameters. You can pass in up to 1000 URL strings in a single batch call.