27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
# QuestionsApi
|
|
|
|
STEP-style question bank service for study games and clients.
|
|
|
|
## Endpoints
|
|
|
|
- `GET /healthz` Health check.
|
|
- `GET /api/questions/systems` List available systems.
|
|
- `POST /api/questions/search` Search or build a block of questions.
|
|
- `GET /api/questions/{id}` Get one question.
|
|
- `POST /api/questions` Create question (SUPER only).
|
|
- `POST /api/questions/bulk` Upsert questions by `externalId` (SUPER only).
|
|
- `PUT /api/questions/{id}` Update question (SUPER only).
|
|
- `DELETE /api/questions/{id}` Delete question (SUPER only).
|
|
- `POST /api/question-reports` Submit a categorized question report (USER or SUPER).
|
|
- `GET /api/question-reports` List and filter reports, newest first (SUPER only).
|
|
- `GET /api/question-reports/{id}` Get a report and its question snapshot (SUPER only).
|
|
- `PATCH /api/question-reports/{id}/status` Resolve or dismiss an open report (SUPER only).
|
|
|
|
Player reads require `USER` or `SUPER` JWT auth. Authoring endpoints require `SUPER`.
|
|
|
|
Questions submitted through authoring endpoints must have authoritative direct
|
|
reference links recorded as described in the repository's **Question
|
|
Verification References** policy. The references must verify the keyed answer
|
|
and the material claims in the explanation; search-result links are not
|
|
acceptable.
|