Skip to main content

Contract Manipulation


Depending on the flow, it may be necessary to make some calls to complete the contract flow.


Manager Approval


If the contract is proposed by a consultancy, after document generation, manager approval will be required before it is sent for signature.

Request

ENDPOINT
/assignment_contract/assignment_contract/ASSIGNMENT_CONTRACT_KEY
MÉTODO
PUT
Request Body
{
"status": "denied",
"denial_reason": "Documentação do cedente insuficiente",
}

Body Params

FieldTypeDescriptionCharacters
status *stringManager's Decision. denied or approved--
denial_reasonstringDescription with the reason for refusal.1 to 500

*Required fields

Response

STATUS
202


Manual Signature Submission


If the template configures manual submission for signature, it's possible to group multiple contracts, as long as they have the same manager, assignor and guarantors, for the same signature batch.

Request

ENDPOINT
/assignment_contract/signature_batch
MÉTODO
POST
Request Body
{
"assignment_contract_keys": ["assignment_contract_key", "assignment_contract_key"],
}

Body Params

FieldTypeDescriptionCharacters
assignment_contract_keys *arrayList of contracts to be sent in the same batch--

*Required fields

Response

STATUS
202


Contract Cancellation


At any stage, except in the case of an already signed contract, it's possible to cancel it. If it's in signature, the signature event is also canceled

Request

ENDPOINT
/assignment_contract/assignment_contract/ASSIGNMENT_CONTRACT_KEY
MÉTODO
PUT
Request Body
{
"status": "canceled"
}

Body Params

FieldTypeDescriptionCharacters
status *stringcanceled--

*Required fields

Response

STATUS
202