# Settlement Feed {% content-ref url="/pages/pCOsbPzku2QUbexzwct0" %} [Settlement Feed](/odds88-client-api/odds88-feeds/settlement-feed.md) {% endcontent-ref %} * Establish connection. * Process message. Message schema * Apply settlement results to the ticket in DB, update player balance accordingly. * Every message has ticket level `settlementTime`, that shows at what time settlement happened. Normally messages are pushed to feed 0.5-2 seconds after settlement happens. * Multiple settlement messages can be sent for one ticket. If `settlementTime` of ticket received in message is smaller than previously received in settlement message for this ticket, message should be ignored and no changes should be made. Especially important during reconnect/recovery to prevent resettlements of tickets. * Reconnection should be automatically handled by integration. Automatic Reconnection should happen with **correct** **revision**. * `revision` is a UNIX timestamp seconds. In case of reconnection it should have a timestamp of 1 minute before the last settlement message received. Duplicated messages expected and should be ignored. Maximum recovery period is 3 days. * There are endpoints that can be used to get the latest result/status of specific tickets. We recommend implementing these endpoints in your backend/backoffice to get results manually if needed. * Settlement of tickets, without interaction with Odds88 endpoints should be possible from your backoffice in case it is not possible to do it any other way. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.odds88.io/integration-process/recommended-integration-flow/settlement-feed.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.