Manual Review Response
Client
←
MTS
A Manual Review response is sent in response to a Manual Review request. 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
content
See Content object description below
M
Object
correlationId
Same string as submitted by the client in the Manual review request
M
String
timestampUtc
Timestamp of the response placement (Unix time in milliseconds format), minimal: 1, maximum: 9223372036854776000
M
Integer
operation
Should be "manual-review" in the case of a Manual Review response
M
String
version
Indicates the ticket format version
M
String
Content object (Manual review response)
The Content object includes the following fields:
type
status
signature
code
message
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.
Content object table
Object
type
Declaration of the content type, should be "manual-review-reply" in the case of a Manual review response
or "error-reply" in the case of major ticket errors or internal system errors (see also Error-reply Response).
M
String
status
Enumerator:
"pending" - The ticket is still under manual review, and no final decision has been made yet.
"rejected" - Manual period review has expired. The ticket is finalized as rejected.
"accepted" - The ticket has been accepted after a manual review.
M
String
signature
String calculated and sent by MTS to be used as proof that the response has actually been provided by MTS, minimal string length = 1, maximum string length = 128
M
String
message
Readable Max stake response, minimal string length = 1, maximum string length = 128
M
String
Last updated
Was this helpful?