All problem types

V.ap problem type · HTTP 404 Not Found

/api/docs/problems/digg/report-not-found

report-not-found

Type URI /api/docs/problems/digg/report-not-found
HTTP status 404 Not Found
Endpoint GET /api/digg/v1/reports/{id}

No retrievable DIGG report exists under this id for your API user. The cases:

  1. Not yet submitted — the memento was created, but the end user has not (yet) dispatched the form. This is the normal state between memento creation and user action.
  2. Unknown id — no memento/report with this id was ever created.
  3. Different API user — reports are only visible to the API user whose memento created them.
  4. Not a DIGG report — the id belongs to a report of a different module.
  5. Sending failed — the user sent the form, but the submission was rejected before it reached the Standesamt (the form shows the error). Nothing is recorded; the id stays 404 until the user sends successfully.
{
  "type": "/api/docs/problems/digg/report-not-found",
  "title": "Not Found",
  "status": 404,
  "detail": "No DIGG report 'DIGG-2026-00123' for this user — not yet submitted, unknown id, or not a DIGG report",
  "instance": "/api/digg/v1/reports/DIGG-2026-00123"
}

What to do

If you are polling for a result: keep polling — a 404 before the user dispatches the form is expected. Note that DIGG delivery is asynchronous: once dispatched, the report appears with status PENDING and resolves to SUCCESS or FAILURE later.