POST
Set Appointment
https://staging.1800accountant.com/sfapi/schedule/setappointment.php?TID=[will be provided]&WID=00Q3Z00000o9wbLUAQ&Date=11/20/2019&Time=11:30&UID=567abbe3e3963d3e738b47e0&Phone=5555555555&Token=[to be provided]&Topic=[will be provided]
Once you have tested in Staging, we will provide production URLs and keys.
PARAMS
TID
WID
Date
Time
UID
Phone
Token
Topic
[will be provided]
Pass value provided for appointment type
00Q3Z0000o9wbLUAQ
ContactID from Create Call
11/20/2019
Date in MM/DD/YYYY format
11:30
Time in HH:MM format
567abbe3e3963d3e738b47e0
AssignedAccountantID returned from availability call
5555555555
(optional) Phone Number
[to be provided]
the authentication token
[will be provided]
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.