CAcardda
SII Key

Sync invoices for a period

Triggers a synchronous sync of the company's electronic documents (DTEs) from the SII for the tax periods in [from, to] (both YYYY-MM, inclusive). The call authenticates with this key, walks each month in the range, and upserts the resulting fiscal invoices.

The range is validated server-side: from and to must both match YYYY-MM, from must be ≤ to, and the span must not exceed 24 months — otherwise the request fails with 422 (sii/invalid-range).

Because CxP payables ingestion relies on the company's own certificate, this is how you backfill or refresh a company's SII inbox/outbox on demand. The call is synchronous and can take a while for wide ranges.

post/v1/sii/keys/{sii_key_id}/sync_invoices

Request

  • Base URL
    https://api.cardda.com
  • URL
    https://api.cardda.com/v1/sii/keys/{sii_key_id}/sync_invoices
  • Auth
    HTTP bearer

Path parameters

sii_key_idstring uuid required

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

Parameters

#/paths/~1v1~1sii~1keys/get/parameters/0 (unresolved $ref)

Request body

fromstring required

First tax period to sync, in YYYY-MM format. Anything that does not match YYYY-MM is rejected with 422 (sii/invalid-range).

tostring required

Last tax period to sync (inclusive), in YYYY-MM format. Must be greater than or equal to from, and the span must not exceed 24 months — otherwise 422 (sii/invalid-range).

Example request

{
  "from": "2026-01",
  "to": "2026-03"
}

Response

The sync completed successfully.

status'synced' required

Always synced on success.

fromstring required

First tax period synced (YYYY-MM).

tostring required

Last tax period synced (YYYY-MM).

last_synced_atstring date-time nullable

The key's last_synced_at after the sync.

Example response

{
  "status": "synced",
  "from": "2026-01",
  "to": "2026-03",
  "last_synced_at": "2026-07-21T14:03:00Z"
}

Changes

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