These instructions are used to embed a 1-800Accountant scheduled in a partner website or i-frame.
Parameters that should be added by Partners:
TID=1on1
Source=The Lead Source of the Partner
Type=Lead Type (Default. Type=TSA)
EmailCampaignID=Email Campaign ID for Tracking (Default. Type=EmbedSched)
Frame=1 (only pass if embedding scheduler in iFrame)
Will create a lead with Lead Source = LeadSourceGoesHere and Lead Type = TSA
Staging Version:
https://staging.1800accountant.com/sfapi/schedule/index.php?TID=1on1&Source=LeadSourceGoesHere&Type=TSA&EmailCampaignID=EmailCampaignIDGoesHere
Production Version:
Add the following parameters:
email (set to email if email address is available)
phone (set to phone if phone number is available)
first_name (set to first name if available)
last_name (set to last name if available)
TCL (set to 1)
If all values above are sent, lead will be created and scheduler view will be presented, if any are missing form will be pre-populated with any values passed.
Sample Staging Version with all params:
https://staging.1800accountant.com/sfapi/schedule/index.php?TID=1on1&Source=LeadSourceGoesHere&Type=TSA&EmailCampaignID=EmailCampaignIDGoesHere&email=test120722@test.com&phone=5555555555&first_name=test&last_name=last&TCL=1
Sample Production Version with all params:
https://1800accountant.com/sfapi/schedule/index.php?TID=1on1&Source=LeadSourceGoesHere&Type=TSA&EmailCampaignID=EmailCampaignIDGoesHere&email=test@testtest.test123&phone=8777770450&first_name=test&last_name=last&TCL=1
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.