Fac-360
Companies

Download what SUNAT proposes, and stop

ADMIN and above. This LOOKS: it asks SUNAT for the proposal and does not accept it. It is a separate route from generation, and not the same route with a flag, for the reason the machine surface gives at length: the difference between looking and committing cannot live in a JSON field, because the day somebody leaves that field set a period is closed and there is no inverse operation. Answers 202 and hands the period to the durable cycle; poll the period listing for the outcome. A period fenced as AMBIGUOUS is refused with 409 and never retried automatically.

POST
/console/v1/companies/{companyId}/sire/periods/{book}/{period}/proposal

ADMIN and above. This LOOKS: it asks SUNAT for the proposal and does not accept it.

It is a separate route from generation, and not the same route with a flag, for the reason the machine surface gives at length: the difference between looking and committing cannot live in a JSON field, because the day somebody leaves that field set a period is closed and there is no inverse operation.

Answers 202 and hands the period to the durable cycle; poll the period listing for the outcome. A period fenced as AMBIGUOUS is refused with 409 and never retried automatically.

Authorization

consoleSession
__Host-apf_console<token>

Set by POST /console/v1/sessions. HttpOnly, Secure, SameSite=Strict, Path=/, __Host- prefixed. It is never readable by JavaScript and there is no header alternative: accepting both carriers would let an attacker choose the weaker one.

In: cookie

Path Parameters

companyId*string
Formatuuid
book*string

Value in

  • "rvie"
  • "rce"
period*string
Match^[0-9]{4}(0[1-9]|1[0-2])$

Response Body

application/json

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/console/v1/companies/497f6eca-6276-4993-bfeb-53cbbbba6f08/sire/periods/rvie/string/proposal" \  -H "Authorization: Bearer apf_v2_tu_credencial"
{  "schemaVersion": "console.1",  "requestId": "d385ab22-0f51-4b97-9ecd-b8ff3fd4fcb6",  "book": "rvie",  "period": "string",  "status": "RUNNING",  "statusPath": "string"}

Open a period, which sends nothing to SUNAT POST POST

ADMIN and above. Opening a period is a row in our ledger saying somebody intends to work on this month; nothing leaves for SUNAT and nothing is committed. A company still issuing in BETA is refused by the database, by the trigger migration 000080 installs, and this route only translates that refusal. Keeping the check in the database means the second entry point cannot forget it.

Accept the proposal and generate the registry, which has no inverse POST POST

ADMIN and above. This COMMITS: it accepts the SUNAT proposal and generates the registry for a real taxpayer real period, and no route on this platform can withdraw one. SUNAT publishes no rehearsal environment for SIRE, so the first exercise of this route is on a real period. A console offering it must show what is about to happen and ask. Answers 202 and hands the period to the durable cycle. A period already REGISTERED is refused with 409, and one fenced as AMBIGUOUS is refused with 409 and never retried: it cannot be established whether SUNAT applied the last act, and generating twice is not recoverable.