checkPerson
|
POST |
/api/widget/checkPerson |
Able to pass the unique client API key (from TrackerRMS) and username (the user’s email address) to the api along with key contact information to check they exist in the system and which record types have been found.
Sample Request:
{
"trackerrms": {
"checkPerson": {
"credentials": {
"username": "my.name@domain.com",
"password": "Welcome123",
"oauthtoken": "1bc7ca1e-8b9a-11e9-bc42-526af7764f64"
},
"details": {
"email": "person.name@domain.com",
"phone": "5557672",
"linkedin": "http://www.linkedin.com/my/profile"
}
}
}
}
Sample Response:
{
"status": 0,
"message": "success",
"count": 0,
"recordLink": "https://usevo1.tracker-rms.com"
"recordTypes": "CRU"
"firstRecord": {
"fullname”: “John Smith”,
“jobtitle”: “Managing Director”,
“company”: “ABC Incorporated”,
“phone”: “555-6893”,
“cell”: “555-8928”,
“email”: “john.smith@abcorp.com”,
“linkedin”: “https://www.linkedin.com/in/johnsmith”
}
}
Response status codes:
|
0 |
success |
|
1 |
user not found |
|
2 |
user not active |
|
99 |
Invalid request |
Response Record Types:
|
C |
Contacts |
|
R |
Resources |
|
U |
Users |