About Contract Live

Contract Live is a contract managing platform entirely based on the cloud. Contract Live allows you to manage simply every type of contract; HR, supplier, clients, etc. Creating, negotiating, signing and managing contracts becomes simple. Working like a mail box, all your contracts are located in the same place and everything is automatic.

More information on http://www.contract-live.com/.

Don’t hesitate to contact us at customersuccess@contract-live.com.

Authentication

Contract Live uses HTTP headers for authentication. There are 3 headers:

• cl_uid - API unique ID
• cl_timestamp - Unix time in milliseconds (GMT)
• cl_hash - a hash

cl_hash is a String calculated from the API secret key, the API unique ID and the timestamp. These 3 values are joined with underscore ("_") and hashed with SHA-256.

Your API unique ID and API secret key are available on Contract Live, in the settings.

Authentication Example

• Unique ID : e665b888-15ce-464c-aa04-ff993a5a214b
• Request Date : 1398868871349
• Secret Key : 985b07501ddf45aeb7942457292c0e41

HTTP headers :

• cl_uid : e665b888-15ce-464c-aa04-ff993a5a214b
• cl_timestamp : 1398868871349
• cl_hash : c9d28ae3b24dfab93e001b4ed6b93f44711988aa5c890b832308fbf41ebc047a

Hash calculation in Bash, using shasum.

printf "%s_%s_%s" "$API_KEY" "$timestamp" "$API_UID" | shasum -a 256

Hash calculation in Java, using DigestUtils (apache commons).

import org.apache.commons.codec.digest.DigestUtils;
DigestUtils.sha256Hex(String.format("%s_%s_%s", API_KEY, timestamp.toString(), API_UID));

Hash calculation in Python, using hashlib.

import hashlib
hashlib.sha256('%s_%s_%s' % (API_KEY, timestamp, API_UID).hexdigest()

Environment

The environment is a resource that allows you to obtain information on the environment used.
This can be useful to test the authentication.
The environment is a global non editable data.

Negotiation

A negotiation, or a contract in progress, is a contract being created, negotiated but not yet signed by all parties. It can be shared with several users of different companies. A negotiation has an editable content that corresponds to the contract.

Once all parties have signed the negotiation, this process is ended. It becomes a signed contract, and each signatory has it’s own version of it.

The negotiation goes through different stages as followed:

1. NEGOTIATION, the contract in progress is in negotiation. This is the first step of a contract in progress.
2. BROKEN, the contract in progress has been interrupted and/or ended. One of the contributors has interrupted and left the negotiation or simply left the negotiation without interrupting it.
3. SIGNING, the contract in progress is being signed. The content of the contract is no longer editable as soon as one of the contributors has signed the contract.
4. SIGNED, the contract in progress has been signed by all parties. It’s the final stage of the contract in progress that seals and validates the content. It’s the creation of a signed contract.

Template

A template is a contract template saved online in order to gain in mobility and in productivity. It allows you to create negotiations from existing models. Use a template allows you to create contracts in progress from this model on line.

Automated template

An automated template is a specific template that has the particularity of containing variables. These variables are automatically replaced with the ones set up by the user when the contracts are created.

For example, for an automated employment contract, it would be wise to define variables such as the first name, the family name, the address of the future employer or even the wage. Each variable has it’s own technical key and a name viewable by humans.

In the Contract Live API, it is not possible yet to modify the content of an automated template. It is, however, possible to change the automated template into a regular one, modify it, and go back to automated template. The process will delete the variables in the automated template.