API · v1 · stabil
CODEMETA OSDeveloper Center
Konsole öffnen
Entity · ticket_queries

Ticket Query Schema

Schema-ID
ticket_query
Collection
ticket_queries
Permissions
  • Lesenticket_query_view
  • Anlegenticket_query_create
  • Ändernticket_query_edit
  • Löschenticket_query_delete
Beziehungen

Felder

Ticket Query Schema

ticket_queries4 Permissions

Schema for validating technician→dispatch ticket queries (Rückfragen)

ticketIduuiderforderlich→ ticket

UUID of the parent ticket the query belongs to

read-only
reasonstringerforderlich

Structured reason why dispatch had to be asked back (drives the KPI breakdown)

Werte
MISSING_INFOMISSING_ACCESSSCHEDULINGWRONG_ASSIGNMENTAPPROVAL_BUDGETOTHER
questionstringerforderlich

The technician’s question to dispatch

1–4000 Zeichen
statusstringoptional

OPEN until dispatch answers, then ANSWERED (set via the /answer route)

Werte
OPENANSWERED
Default: "OPEN"read-only
assignedToIduuidoptional

Dispatcher expected to answer. Defaulted server-side on create from the ticket; may be reassigned via generic PATCH.

nullable
answerstringoptional

Dispatch’s answer to the query

max 4000 Zeichenread-onlynullable
answeredByIduuidoptional

UUID of the dispatcher who answered (set server-side from session)

read-onlynullable
answeredAtdatetimeoptional

Timestamp the query was answered; null while OPEN

read-onlynullable

Standard-Endpoints

Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:

  • GET /api/v1/ticket_queries — Liste, paginiert + filterbar
  • GET /api/v1/ticket_queries/<id> — Einzelne Entity
  • POST /api/v1/ticket_queries — Anlegen
  • PATCH /api/v1/ticket_queries/<id> — Teil-Update
  • DELETE /api/v1/ticket_queries/<id> — Soft-Delete
  • GET /api/v1/ticket_queries/<id>/timeline — Audit + Aktivitäten

Suche