The Retrieval API Developer Hub

The Retrieval API allows you to match your data to the LiveRamp Identity Graph and receive RampIDs. API calls are made using batch request calls that contain up to 1000 records per call.

Guides    API Reference

How AbiliTec Works

At a high level, the primary use of AbiliTec consists of these basic steps:

  1. You send your PII-based consumer data (such as name, address, phone number, or email address) through the Abilitec API.
  2. We obfuscate the data and then compare it against the obfuscated data in the AbiliTec Identity Graph.
  3. If there is a matching record in the identity graph, the API returns a maintained AbiliTec ID along with insights about that record and metadata about how the match was obtained (if applicable). If there is no matching record, the API can return a derived AbiliTec ID for each PII touchpoint.
  4. AbiliTec IDs can then be used as unique identifiers to consolidate records or to group records by household.

In this way, no raw (plaintext) PII sent from a client is ever written to disc, as it only lives in temporary memory for the duration of the API call.

Batch Requests

The API is designed to make it really easy to get data for an individual person, place, or household (for example, for an individual record in a point of sale transaction). However, if your application needs the ability to access significant amounts of data in a single request (for multiple records and large files), the API also supports batch requests. This allows you to make up to 1,000 individual requests within a single call. Once all requests have been resolved, a consolidated response will be passed back to you.

Updated 2 years ago

How AbiliTec Works


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.