Interpreting Record and Person ID Connections
Interpreting Record and Person ID Connections
In order to obtain an overall higher match rate and quality output from FullContact, we recommend leveraging our multi field input capability. This allows for real-time query confidence boost, connecting to multiple internal datasets and fewer API calls to FullContact.
| Response Code | Enriched Data and IDs | Connection |
|---|---|---|
| 200 | Person ID, No Record ID | Not mapped but known in FullContact's Identity Graph |
| 200 | Person ID, Record ID | Known in FullContact's Identity Graph and mapped |
| 200 | Person ID, Multiple Record ID | Known in FullContact's Identity Graph, mapped but multiple Record IDs for an individual |
| 200 | No Person ID, Record ID | Not known in FullContact's Identity Graph but mapped |
| 404 | No Data |
Updated about 2 years ago