Update one

Rotates the credentials of an SII key. All fields are optional; send only what
changes. When the update touches a key that is not already approved, Cardda
re-runs the company sync asynchronously afterwards. The response omits
company_ids (it includes can_issue?).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

UUID of the SII key (digital-certificate credential).

Body Params

Fields to update (all optional).

All fields are optional; send only what you want to change. Note the SII portal
RUT (rut) can be re-pointed, and either credential can be rotated.

string

New RUT for the credential (digits plus verifier digit, no dots).

string

New SII portal password. Stored encrypted; never returned.

string

New digital-certificate password. Stored encrypted; never returned.

Headers
uuid
required

UUID of the company on whose behalf the request is made. Fiscal-invoice endpoints
authorize the caller against this company (and read/write its data). SII-key
endpoints never filter their results by this header. On the SII-key list,
however, belonging to the header company is one of the ways a caller is authorized
to make the call (alongside being Cardda staff or passing their own user_id), so
the header is not merely ignored there. On the other SII-key endpoints the header
plays no part in authorization. See The company-id header
for details on how to obtain a value for this header and the error responses to
expect when it is missing or invalid.

Responses

401

Unauthorized — missing/invalid token, or the caller lacks sii_keys_manage
and does not own the key. Auth is by key ownership or sii_keys_manage
permission; the company-id header is not used to scope this operation.
Empty body.

404

SII key not found. Body: { "message": "Resource not found" }.

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json