Upload a contract

Endpoint to upload a contract. Currently supports .pdf, .docx and .txt.

A base64 encoded byte string for the document data is required as the POST body.

To upload multiple documents, POST with the primary document, retrieve the returned contract-id then repeat the same step for each new document, including the contract_id in the subsequent requests to associate multiple documents with the same contract.

If submitted without a contract-id, will create a new contract and return a new contract-id and a document-id.

If submitted with a document-id, will replace that document with the new document

post/contracts

Request

Query parameters

document-namestring required

Name of submitted document

template-idstring required

ID of template

defined-termstring

Defined term

urlstring

URL of hosted public contract

contract-idstring

ID of contract. If supplied, will update existing contract with new document

party-b-defined-termstring

Name of the party B entity (customer, receiver, investing entity)

document-idstring

ID of document. Include if replacing document

party-a-defined-termstring

Name of the party A entity (vendor, discloser, issuing entity)

contract-position-idstring

Party that drafted the contract: Use '1' for vendor form and '2' for customer form

review-levelstring

Review level of the contract review: Use 'verified' for human-in-the-loop and 'predicted' for AI only

is-publicstring

Use '1' for public contracts and '0' for private contracts

Response

200 response

contract_idstring

ID of newly created contract

document_idstring

ID of document created

Changes

No recorded changes to this operation across all 1 revision of this API.