Get Customer Informacion
API: Get Customer Informationsagent_summary_stats
Description
ThisThe endpointAPI retrievesis aresponsible summaryfor of agent activity and performance statistics overretrieving the last day. It is useful for supervisors and managers to monitor agent productivity, call handling metrics, and time distribution across various call and pause states. This returns detailed data per agent, including call counts (manual, inbound, dialer), time spent in login, pause, talk, and break statuses, as well as call outcomes and user profileclient’s information.
đź”— URL
https://DOMAIN.croco-dial.net/goAPIv2/goAgent/goAPI.php
Note: Replace DOMAIN with the specific domain you want to query.
📝 Required Parameters
| Parameter | Value | Description |
| goAction | agent_summary_stats | Action to perform |
| goUser | MyUser | API authorized user. |
| goPass | MyPass | Authorized user's password. |
| responsetype | json/xml | Format of the response (json recommended). |
| phone number | Phone_Number | Insert the client’s phone number. |
| leed id | leed_id | Call ID. |
Note: This endpoint uses body parameters for authentication instead of tokens or headers.
Request Examples:
GET:
curl -X GET "https://DOMAIN.croco-dial.net/goAPIv2/goReports/goAgent/goAPI.php?goAction=agent_summary_stats&goUser=MyUser&goPass=MyPass&goAction=goGetCustomerInfo&responsetype=json"json&phone_number=PhoneNumer&lead_id=MyLeadID"
POST (Form Data)
If you prefer to send the data as form parameters:
curl -X POST "https://DOMAIN.croco-dial.net/goAPIv2/goReports/goAPI.php" \
-H "Content-Type: application/x-www-form-urlencoded" \
--data-urlencode "goAction=agent_summary_stats" \
--data-urlencode "goUser=MyUser" \
--data-urlencode "goPass=MyPass" \
--data-urlencode "responsetype=json"\
--data-urlencode "phone number=Phone_Number"
Example Response
{
"result": "success",
"lead_info": {
"lead_id": 14246,
"list_id": 22799125,
"title": ""Lic",
"first_name": ""Bruno",
"middle_initial": ""M",
"last_name": ""Macias",
"phone_number": "8004321000",
"alt_phone": ""5587654321",
"email": ""brunoramiro@email.com",
"address1": ""Av. Reforma 123",
"address2": ""Interior 4B",
"address3": ""Col. Centro",
"city": ""Guadalajara",
"state": ""Jalisco",
"province": ""Ontario",
"postal_code": ""44100",
"country_code": ""MX",
"gender": "U",
"date_of_birth": "1825-10-23",
"status": "PU",
"user": "Bruno",
"comments": "Additional information was requested."
},
"custom_info": null,
"is_customer": 0
}
Data Fields per Agent
| Field | |
| Description | |
|
success, error, validation_failed). |
||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
gender |
Gender classification of the lead (M = Male, F = Female, U = Unknown). |
||
date_of_birth |
Lead’s |
||
status |
Operational status code assigned to the lead within the system, determined by internal business logic. | ||
user |
System user or |
||
comments |
Free-text field used to store notes or annotations related to the lead. | ||
custom_info |
Object containing configurable custom fields defined by the system; may return null if no custom fields are present. | ||
is_customer |
Logical indicator specifying whether the lead has been converted into a customer (1) or remains a prospect (0). |