Transmit an e-reporting report
POST/api/v1/workspaces/:workspace_id/e_reportings/:id/submit
Builds the report for its period, validates it against the reform's conformance rules and deposits it. The transmission itself is asynchronous: a 201 means the deposit was registered and is being carried, not that the administration has answered - the verdict arrives later on deposit_outcome. Re-posting a report that is already in the administration's hands answers 200 with transmitted=false and deposits nothing, so a retry is safe. A report the administration has already accepted is refused: what was declared can only be changed by a rectificative transmission. A 409 means another process is depositing this report right now, or that a rectificative transmission found a row of the period held by another writer - nothing was transmitted and the call can be retried. A 422 carries two different situations apart on code: validation_failed is a verdict about the declaration and the remedy is to fix it, while schematron_engine_unavailable means the conformance engine could not run - nothing was judged, and the same report is re-posted unchanged once it is back.
Request
Responses
- 200
- 201
- 401
- 403
- 404
- 409
- 422
The report was already in the administration's hands; nothing was deposited again. Every retry answers this.
The report was built, validated and deposited. The administration's verdict arrives later and is read from deposit_outcome.
The request did not include a valid OAuth 2.0 bearer token.
The authenticated OAuth client does not have access to this workspace, no such workspace exists, or its token does not carry the write scope this endpoint requires.
No e-reporting report with this id exists in the workspace.
Another process is depositing this report right now and this call could not converge on it, or a rectificative transmission found a row of the period held by another writer. Nothing was transmitted; retry shortly.
The report cannot be transmitted. With code=validation_failed this is a verdict about the declaration - it carries no data for its period, a party carries no accepted identifier scheme, it fails a conformance rule, or the administration has already accepted it - and it is fixed before re-posting. With code=schematron_engine_unavailable the conformance engine could not run: nothing was judged and nothing is wrong with the report, so the same request is retried unchanged.