top of page

These two APIs allow you to retrieve lead and customer statuses using these attributes:

"ID" - Lead/Account ID, Unique Salesforce ID of the lead/account   "Id": "00Q5e00000VCCEPEA5" 
"X1_1_Scheduled__c" - Consultation Scheduled Date "X1_1_Scheduled__c": "2023-02-20T16:30:00.000+0000", "X1_1_Scheduled_Local__c""02/20/2023 10:30 AM - CST"
"X1_1_Attended__c" - Consultation Attended Date "X1_1_Attended__c": false,   
"Status" - Current Status of the lead. If Status = Qualified, will be a corresponding Account "Status": "1-1 Request",
"Account_Status__c" - For Accounts, indicates the status. Prospect, 1st year customer, renewed customer, etc. "Account_Status__c": "Prospect"   
"IsConverted" - Indicates if the lead was converted to an account "IsConverted": false   
"Last_Login_Date__c" - Date of last login if a client "Last_Login_Date__c": null,   

POST

Get Lead Status

PARAMS

Token

ContactID

BODY

raw

[to be provided]

00Q5e00000VCCEPEA5

{
 
"Result": "100",
  "Lead": {
    "Id": "00Q5e00000VCCEPEA5",
    "X1_1_Scheduled__c": "2023-02-20T16:30:00.000+0000",
    "X1_1_Scheduled_Local__c": "02/20/2023 10:30 AM - CST",
    "X1_1_Attended__c": false,
    "Status": "1-1 Request",
    "IsConverted": false,
    "ConvertedContactId": null
  }
}

POST

Get Account Status

PARAMS

Token

ContactID

BODY

raw

[to be provided]

003f1000020OVRlAAO

{
 
"Result": "100",
 
"Account": {
   
"Id": "001f100001FTkXyAAL",
   
"X1_1_Scheduled__c": "2023-02-06T14:00:00.000+0000",
   
"X1_1_Scheduled_Local__c": "02/06/2023 8:00 AM - CST",
   
"X1_1_Attended__c": true,
    "Last_Login_Date__c": null,
    "Total_Logins__c": null,
    "CreatedDate": "2018-03-28T04:06:07.000+0000",
    "Account_Status__c": "Prospect"
  }
}

Our Lead API(s) leverage SSL (Secure Socket Layer) for encryption, the communication between the client and the server is secured using an encryption-decryption mechanism to ensure data confidentiality and integrity. SSL operates in the transport layer, encapsulating higher-level protocols such as HTTP. When a client establishes a connection to an SSL-enabled server, they perform an SSL handshake. During this handshake, both parties agree on a version of SSL/TLS (Transport Layer Security, the successor to SSL) to use, select cryptographic algorithms, and exchange cryptographic keys. The client and server will then use these keys to symmetrically encrypt and decrypt the transmitted data, ensuring that any eavesdropper intercepting the data in transit cannot easily decipher it. Additionally, SSL provides server authentication through the use of digital certificates, allowing clients to verify the identity of the server, ensuring they are communicating with the intended recipient and not a malicious actor. This combination of encryption, data integrity, and authentication provides a robust security framework for RESTful API communications over potentially insecure networks.

bottom of page