Connect game-history requests to the exact session and round.
ALHICA routes Detailed Game History requests through the correct connector while preserving the identifiers required to relate the result to a session, game cycle and transaction timeline.
- Provider-aware DGH routing
- Session and round correlation
- Operational request evidence
Resolve the correct provider context
The gateway uses controlled catalogue, session and round mappings to select the provider-specific history flow.
Identifiers are validated so an unrelated or malformed request cannot be routed silently.
- Catalogue and provider mapping
- Session and round validation
- Controlled error responses
Translate without losing source meaning
Connector logic adapts provider response formats to the platform-facing contract while retaining source references for investigation.
Availability and detail depend on the provider protocol and the approved operator integration.
- Provider response translation
- Source identifiers retained
- Explicit capability boundaries
Observe and support the request
Correlation IDs connect the DGH request, connector call, response and errors in Aggregator Admin.
Operational metrics expose latency and failure patterns without treating a successful transport response as proof of complete source content.
- End-to-end trace
- Latency and error metrics
- Support diagnostics
Map DGH into the same operational evidence chain.
Review the platform and provider contracts required for the intended history experience.