> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/transaction30api/api-description/ticket-json-format-description/manual-review-response.md).

# Manual Review Response

<table><thead><tr><th width="114.609375" align="center">Destination</th><th width="54.75262451171875" align="center"></th><th width="115.19964599609375" align="center">Source</th></tr></thead><tbody><tr><td align="center"><strong>Client</strong></td><td align="center"><strong>←</strong></td><td align="center"><strong>MTS</strong></td></tr></tbody></table>

A Manual Review response is sent in response to a [Manual Review request](/transaction30api/api-description/ticket-json-format-description/manual-review-request.md). It contains the current status of the manual review for the ticket in question.

**Envelope and Content table:**

The Envelope provides the content's (Manual Review response) context and contains the following fields (besides Content):

* correlationId
* timestampUtc
* operation
* version

<table data-full-width="true"><thead><tr><th width="350.5572509765625">Example</th><th width="147.7447509765625">Field Name</th><th>Field Description</th><th width="100">Mandatory/ Optional</th><th width="100">Data Type</th></tr></thead><tbody><tr><td><pre><code>  "content": {
       .........
       .........
   },    
</code></pre></td><td>content</td><td>See Content object description below</td><td>M</td><td>Object</td></tr><tr><td><pre><code>  "correlationId": "jw9dn1qlus",
</code></pre></td><td>correlationId</td><td>Same string as submitted by the client in the Manual review request</td><td>M</td><td>String</td></tr><tr><td><pre><code>  "timestampUtc": 1778499644000,
</code></pre></td><td>timestampUtc</td><td>Timestamp of the response placement (Unix time in milliseconds format),<br>minimal: 1,<br>maximum: 9223372036854776000</td><td>M</td><td>Integer</td></tr><tr><td><pre><code>  "operation": "manual-review",
</code></pre></td><td>operation</td><td>Should be "manual-review" in the case of a Manual Review response</td><td>M</td><td>String</td></tr><tr><td><pre><code>  "version": "3.0"
}
</code></pre></td><td>version</td><td>Indicates the ticket format version</td><td>M</td><td>String</td></tr></tbody></table>

### Content object (Manual review response) <a href="#mtsmaxstakeresponse-v3.0-contentcontentobject-maxstakeresponse" id="mtsmaxstakeresponse-v3.0-contentcontentobject-maxstakeresponse"></a>

The Content object includes the following fields:

* type
* status
* signature
* code
* message<br>

**Please note** that in the case of major ticket errors or internal system errors, the content object has a different structure and contains "type": "error-reply" instead of "type": "max-stake-reply". For description, see [Error-reply Response](/transaction30api/api-description/ticket-json-format-description/error-reply-response.md).

**Content object table**

<table data-full-width="true"><thead><tr><th width="351">Example</th><th width="111.091064453125">Field Name</th><th>Field Description</th><th width="100">Mandatory/ Optional</th><th width="100">Data Type</th></tr></thead><tbody><tr><td><pre><code>"content": {
</code></pre></td><td><br></td><td><br></td><td><br></td><td>Object</td></tr><tr><td><pre><code>  "type": "manual-review-reply",
</code></pre></td><td>type</td><td><p>Declaration of the content type, should be "manual-review-reply" in the case of a Manual review response</p><p>or "error-reply" in the case of major ticket errors or internal system errors (see also <a href="/pages/GY3OQHnyZI8vYXBbPRN4">Error-reply Response</a>).</p></td><td>M</td><td>String</td></tr><tr><td><pre><code>   "status": "pending",
</code></pre></td><td>status</td><td><p>Enumerator:</p><ul><li>"pending" - The ticket is still under manual review, and no final decision has been made yet.</li><li>"rejected" - Manual period review has expired. The ticket is finalized as rejected.</li><li>"accepted" - The ticket has been accepted after a manual review.</li></ul></td><td>M</td><td>String</td></tr><tr><td><pre data-overflow="wrap"><code>   "signature": "Tq72kl+2GvXu3kg0QL
DB0AIB6fUZVFOvmGKm6Rcvxm0=",
</code></pre></td><td>signature</td><td>String calculated and sent by MTS to be used as proof that the response has actually been provided by MTS,<br>minimal string length = 1,<br>maximum string length = 128</td><td>M</td><td>String</td></tr><tr><td><pre><code>   "code": 0,
</code></pre></td><td>code</td><td>Manual review response code,<br>see the list of <a href="/pages/oNiQgEAqWI4RQnhMuOP8">validation codes</a></td><td>M</td><td>Integer</td></tr><tr><td><pre data-overflow="wrap"><code>   "message": "Transaction processed"
 },
</code></pre></td><td>message</td><td>Readable Max stake response,<br>minimal string length = 1,<br>maximum string length = 128</td><td>M</td><td>String</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.sportradar.com/transaction30api/api-description/ticket-json-format-description/manual-review-response.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.