A matching contract approval rule returns HTTP 202 with contract_id and approval_request_id instead of the contract.
This is a proposal, not a created contract: nothing is created until the request is approved, and the contract then keeps contract_id.
To check on it, retrieve-a-draft-contract with contract_id shows a FULL contract waiting as a draft and its approval.status
(WAITING, REJECTED, CANCELLED or WITHDRAWN); once approved, retrieve-a-contract returns it.
Pass idempotency_key on the first call and keep it across retries: a retry with the same key answers with what the first call made
(the contract, or the request it waits on) instead of making a second contract. The key is optional; each call without one makes a new contract.
A key whose request was rejected or cancelled is closed; send the contract again with a new key.

Rillet supports two contract scope types: FULL and REVENUE_RECOGNITION_ONLY. The selected scope determines how the invoices are created and what information the user needs to provide.

The FULL scope is used when contract invoices are generated and sent directly from Rillet. In this case, Rillet automatically assigns the invoice numbers.

The REVENUE_RECOGNITION_ONLY scope is intended for situations where contracts and invoices are issued from another system and only need to be recorded in Rillet for accounting purposes. In this workflow, users must provide the invoice numbers manually. Other fields can be populated based on the data imported from the external system.

For example, if your organization issues invoices through an external billing platform but tracks financials in Rillet, you should select REVENUE_RECOGNITION_ONLY. If Rillet handles the entire invoicing and sending process, choose the FULL scope.