Add mobile and landline phone numbers to your contact records by searching our Authoritative Data Source database using existing contact fields such as first name, last name, city, state, and postal address.
HTTP Header
The "content-type" in the HTTP header must be set to "application/json", otherwise an HTTP 400 Bad Request response will be returned.
Response
A single response may include one and only one Phone element for each Source requested.
| Field name | Type | Description |
|---|---|---|
| Areacode | string | 3 digit US area code |
| PhoneNumber | string | 7 digit US phone number |
| LineType | enum | Indicates the LineType |
| MatchLevel | enum | Indicates the MatchLevel under which the match was found. |
| MaxValidationLevel | enum | Indicates the maximum validation level achieved by the input criteria. Measured as MatchLevel. |
| ConnectionWindow | string | Provides insight into when the best time to contact the consumer is, allowing you to optimize dialing queue throughout the day for optimized results |
| ContactabilityScore | string | Indicates likelihood of right party contact, allowing you to identify which phones to dial and which phones to deprioritize. |
Contactability Score
Indicates likelihood of right party contact, allowing you to identify which phones to dial and which phones to deprioritize.
| Code | Phone Type | Verified | Phone Usage (12 Months) | Phone Usage (2 Months) |
|---|---|---|---|---|
| A | Wireless | Yes | Moderate to Heavy | Moderate to Heavy |
| B | Wireless | No | Moderate to Heavy | Light to Heavy |
| C | Wireless | Yes | Moderate to Heavy | Light |
| E | Landline | Any | Moderate to Heavy | Light to Heavy |
| F | Wireless | Any | Any | Minimal |
| G | Any | Any | Moderate to Heavy | Any |
| I | Any | Any | Light | Any |
| J | Any | Any | Minimal | Any |
| K | Any | Any | None | Any |
Connection Window
Provides insight into when the best time to contact the consumer is, allowing you to optimize the dialing queue throughout the day for optimized results.
Assume the example: HHHHIIIJ
- The first digit "H" corresponds to the best time range per the table below.
- The last 7 digits correspond to the best time by day of the week, with the second digit being Monday and the last digit being Sunday
Assume the example: HHHHIIIJ:
H => 12:00PM – 4:00PM (GMT)
H => 12:00PM – 4:00PM (GMT) - Monday
H => 12:00PM – 4:00PM (GMT) - Tuesday
H => 12:00PM – 4:00PM (GMT) - Wednesday
I => 4:00PM – 8:00PM (GMT) - Thursday
I => 4:00PM – 8:00PM (GMT) - Friday
I => 4:00PM – 8:00PM (GMT) - Saturday
J => 4:00PM – 8:00PM (GMT) - Sunday
| Code | Description |
|---|---|
| A-B | 12:00AM – 4:00AM (GMT) |
| C-D | 4:00AM – 8:00AM (GMT) |
| E-F | 8:00AM – 12:00PM (GMT) |
| G-H | 12:00PM – 4:00PM (GMT) |
| I-J | 4:00PM – 8:00PM (GMT) |
| K-L | 8:00PM – 12:00AM (GMT) |
| N | No Data Available |
LineType codes
[Click for a list of LineType codes and descriptions] (https://docs.accurateappend.com/reference#linetype).
HTTP Error Messages
Click to see a complete listing of error messages and codes.