# Agent API # Get Customer Informacion ## **API: Get Customer Informations** ### **Description** The API is responsible for retrieving the client’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**
goActionagent\_summary\_statsAction to perform
goUserMyUserAPI authorized user.
goPassMyPassAuthorized user's password.
responsetypejson/xmlFormat of the response (`json` recommended).
phone numberPhone\_NumberInsert the client’s phone number.
leed idleed\_idCall ID.
**Note:** This endpoint uses body parameters for authentication instead of tokens or headers. ### **Request Examples:** #### **GET:** ```bash curl -X GET "https://DOMAIN.croco-dial.net/goAPIv2/goAgent/goAPI.php?goUser=MyUser&goPass=MyPass&goAction=goGetCustomerInfo&responsetype=json&phone_number=PhoneNumer&lead_id=MyLeadID" ``` #### **POST (Form Data)** If you prefer to send the data as form parameters: ```bash 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** ```json { "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**
FieldDescription
`result`Indicates the overall status of the API operation (e.g., `success`, `error`, `validation_failed`).
`lead_info`Container object that holds the structured information related to the lead.
`lead_id`Unique identifier assigned to the lead within the system. Used as the primary reference for subsequent operations.
`list_id`Identifier of the campaign or list to which the lead is assigned, enabling segmentation and organization.
`title`Honorific or professional title associated with the lead (e.g., Mr., Ms., Dr.).
`first_name`Given name of the lead.
`middle_initial`Middle name initial of the lead, if available.
`last_name`Family name or surname of the lead.
`phone_number`Primary contact phone number used for outbound or inbound communication.
`alt_phone`Secondary or alternative contact phone number.
`email`Email address associated with the lead for electronic correspondence.
`address1`Primary street address including street name and number.
`address2`Additional address details such as apartment, suite, or unit number.
`address3`Optional extended address field depending on system configuration.
`city`City of residence associated with the lead’s address.
`state`State or administrative region of the lead’s address.
`province`Province or territorial division, used when applicable based on country standards.
`postal_code`ZIP code or postal code corresponding to the lead’s address.
`country_code`Two-letter country code compliant with ISO 3166-1 alpha-2 standards (e.g., US, MX, CA).
`gender`Gender classification of the lead (`M` = Male, `F` = Female, `U` = Unknown).
`date_of_birth`Lead’s date of birth formatted according to the ISO 8601 standard (YYYY-MM-DD).
`status`Operational status code assigned to the lead within the system, determined by internal business logic.
`user`System user or agent currently assigned to manage the lead.
`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`).