Data You Can Send
Learn about the data you can send in an AbiliTec API call.
When you use the AbiliTec API, you can send the following data to the lookup or match endpoint:
- PII such as names, postal addresses, email addresses, and phone numbers
- Raw (plaintext) PII
- Hashed PII
To improve matching accuracy in certain situations when using the Match endpoint, you can include location data such as the latitude or longitude and the IP address. You can also include associative data such as year of birth or the sum of the last 4 digits of the social security number.
After you’ve used the AbiliTec API and you received AbiliTec IDs, you can send AbiliTec IDs as input to reduce the number of times PII is sent. This includes sending AbiliTec DocIDs or AbiliTec Links.
The table below lists the types of input data you can include when you use the AbiliTec API.
Input Data | Endpoint | Data Returned | Notes |
---|---|---|---|
Plaintext PII | Match | Maintained AbiliTec IDs Derived AbiliTec IDs * Match Metadata | Uses match cascade. Can include associative data and location data to improve matching. * Names, street addresses, and phone numbers can either be sent parsed (broken down into their individual components) or unparsed, but not both in the same call. |
Plaintext PII | Lookup | Maintained AbiliTec IDs Derived AbiliTec IDs (DocIDs only) | * Downcase before sending. |
SHA-1-hashed PII string | Lookup | * Maintained AbiliTec IDs | * Downcase before sending. |
MD5-hashed email addresses | Match | Maintained AbiliTec IDs Derived AbiliTec IDs * Match Metadata | * Can be sent along with plaintext PII |
MD5-hashed email addresses | Lookup | * Maintained AbiliTec IDs | * Downcase before sending. |
SHA-256-hashed email addresses | Lookup | * Maintained AbiliTec IDs | * Downcase before sending. |
SHA-1-hashed email addresses | Lookup | * Maintained AbiliTec IDs | * Downcase before sending. |
AbiliTec ID - Link | Match | * Match Metadata |
Updated over 3 years ago