Fac-360
Summaries

Durably request void communication (RA) dispatch

Builds the VoidedDocuments UBL from the stored canonical payload, signs it, packages it and dispatches it with sendSummary inside the same private durable Workflow as the daily summary, with the same ticket cycle and the same non-resendable ambiguity fence.

POST
/api/v2/voided/{id}/submissions

Builds the VoidedDocuments UBL from the stored canonical payload, signs it, packages it and dispatches it with sendSummary inside the same private durable Workflow as the daily summary, with the same ticket cycle and the same non-resendable ambiguity fence.

Authorization

bearerAuth
AuthorizationBearer <token>

Tenant-bound, scoped and expiring Apifact credential. Migrated legacy credentials are accepted only on deprecated v1 writes and tenant-scoped v2 read, poll and download routes. Each operation names the single scope it requires in x-required-scope; the scope array of the security requirement itself is empty because OpenAPI 3.0 requires it to be for a non-oauth2 scheme.

In: header

Path Parameters

id*string
Formatuuid

Header Parameters

Idempotency-Key*string
Length1 <= length <= 200

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/api/v2/voided/497f6eca-6276-4993-bfeb-53cbbbba6f08/submissions" \  -H "Idempotency-Key: b6a2f0e4-1c3d-4a5b-8e7f-9d0c1b2a3e4f" \  -H "Authorization: Bearer apf_v2_tu_credencial"
{  "schemaVersion": "2.0",  "requestId": "d385ab22-0f51-4b97-9ecd-b8ff3fd4fcb6",  "operationId": "3051932a-fdd2-48fa-b330-7e7d41535969",  "resourceId": "026d60bb-63a8-407e-bf67-01dcfc6022e6",  "summaryType": "RC",  "documentName": "string",  "state": "VALIDATED",  "replay": true,  "deadline": {    "status": "WITHIN_DEADLINE",    "elapsedDays": 0,    "limitDays": 0  }}

Get a tenant-owned void communication (RA) and its ticket operation GET GET

Reports the durable operation behind the summary, including the SUNAT ticket once it exists. The ticket is the only handle that can resolve a dispatch out of band, so it is published rather than hidden.

Validate and durably create a comprobante de retención (CRE, 20) POST POST

A comprobante de retención declares the documents an agente de retención is settling, the payment made against each one, the amount withheld and the net handed over. Every monetary figure in the response is DERIVED from the payments and the declared rate; none may be supplied. Creation is capability-gated per tenant (retention_issuance_enabled, off by default) and does not contact SUNAT.