ticket-service - API Contract

Field	Value
Port	9010
Mode	CQRS + Mediator
Base path	/api/v1
Owning sprint	Sprint 12
Build status	TODO
Requirements	FR-31, FR-32, FR-33

Bounded context: customer requests/complaints with SLA-based auto-assignment and breach detection.

Authentication and Authorization

All endpoints require a valid JWT. Assignment and resolution require an agent role.

Endpoints

Method	Path	Auth	Idempotency	Summary
POST	/api/v1/tickets	JWT	optional	Open a ticket; SLA auto-assigned.
GET	/api/v1/tickets/{id}	JWT	-	Fetch a ticket with comments.
GET	/api/v1/tickets	JWT	-	List/search tickets (paged).
POST	/api/v1/tickets/{id}/comments	JWT	-	Add a comment.
POST	/api/v1/tickets/{id}/assign	RBAC agent	-	Assign to a team/agent.
POST	/api/v1/tickets/{id}/resolve	RBAC agent	-	Resolve the ticket.

Events

Direction	Event
Publish	ticket.opened.v1, ticket.assigned.v1, ticket.resolved.v1, ticket.sla-breached.v1
Consume	invoice.overdue.v1 (may open a follow-up ticket), fraud.case-opened.v1 (auto-opens a linked FRAUD_REVIEW ticket, Sprint 23 Feature 23.4.2)

Notes

• Tickets are SLA-auto-assigned on open and notify the customer.
• SLA-breach detection emits ticket.sla-breached.v1 for escalation.
• fraud.case-opened.v1 (fraud-service, ADR-029 Section 5) is consumed by FraudCaseOpenedEventConsumer, which auto-opens a FRAUD_REVIEW ticket through the existing OpenTicketCommandHandler/SlaPolicy path (no parallel ticketing logic) with the originating fraud caseId carried in the ticket's externalRef (retrievable via GET /api/v1/tickets/{id}). Detect-and-alert only: opening the ticket triggers no subscription-service call and no suspension.

Reference: service-catalog, event-catalog, ADR-015.