Client acceptance log upload

This endpoint attaches a PDF holding the client acceptance log to an operation — the record of the evidence that the end client accepted the operation's terms. It exists for the auto signature flow: when QI Tech signs the Termo Constitutivo on the issuer's behalf using the private certificate released in CertifiQI, no signature link is generated for the client, and the acceptance log is what documents their consent.

Optional upload

The upload is not mandatory and no issuance step depends on it. The operation moves through analysis, signature and issuance normally without an acceptance log — the document is kept as evidence attached to the operation.

Requires an issuer enabled for auto signature

The upload is only accepted when the operation's issuer has the auto signature enablement in enabled on the issuer system. An issuer with no enablement, or with an enablement in any other status (pending_term_generation, pending_signature, reproved, canceled), is refused with COM000077 and nothing is stored.

The upload is also only accepted while the operation is in the in_filling status; outside that status the request is refused with COM000010.

---

Client acceptance log upload (POST)

Request

ENDPOINT

/commercial_paper/operation/OPERATION-KEY/acceptance_log

METHOD

POST

Path Params

Field	Type	Description	Max Characters
OPERATION-KEY *	string	Unique operation key (UUID v4).	36

Request Body

{
    "document_base64": "JVBERi0xLjQKMSAwIG9iago8PAovVHlwZSAvQ2F0YWxvZwo..."
}

Request Body Params

The body accepts no fields beyond the one listed (additionalProperties: false) — an unknown field, or a missing document_base64, returns QIT000001.

Field	Type	Description	Max Characters
document_base64 *	string	Client acceptance log PDF, base64-encoded, with no data: prefix and no line breaks.	—

Response

STATUS

201

Response Body

{
    "document_key": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "operation_key": "a846cc4a-b542-4f66-9823-b6d5458bd127",
    "created_at": "2026-09-10T14:30:00.000000+00:00"
}

Response Body Params

Field	Type	Description
document_key *	string	Unique document key generated by this upload (UUID v4).
operation_key *	string	Unique key of the operation the document was attached to.
created_at *	string	Upload date and time, in UTC.

How to confirm what was attached

The operation starts exposing the acceptance_log_document_key field on the operation retrieval by key, filled from the most recent upload. Before the first upload the field returns null.

A new upload replaces the previous document

A new upload for the same operation generates a new document_key and becomes the current acceptance log — the previous reference stops being pointed at by the operation. There is no partial update and there is no deletion endpoint.

---

Errors

The codes below are also described in the error catalog.

Code	HTTP	Description
QIT000001	400	Schema failure — document_base64 missing or unknown field in the body.
COM000010	400	Operation cannot be updated outside the in_filling status.
COM000077	400	The operation's issuer is not enabled for auto signature.
COM000007	404	Operation not found.
COM000008	403	Operation does not belong to the requesting tenant.