This PUT operation utilizes the same resource path as the initial upload, but its function is to confirm and finalize the state of the documents associated with the specified transaction.
It acts as a status update, signaling to the backend that the upload process initiated by the POST request is complete and proceed with the transaction process. This step is crucial for moving the transaction forward and making the uploaded document(s) official and permanent.
Header Parameters
X-Auth-User-IDstring
MatchMove provided ID for the user.
Authorizationstring
Path Parameters
idstring Required
Transaction ID
Response
200
Object
OK
400
Object
Bad Request
| **Code** | **Title** | **Detail** |
| ---------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| invalid_user_id | Invalid User ID | User does not exist. Please provide a valid user id. |
| user_not_active | User Not Active | User is not active. |
| invalid_transaction | Invalid Transaction | Transaction not found. |
| invalid_state | Confirm With No Files | No required document has been uploaded. Please upload the required document and try again. |
Response Attributes
idstring Required
Unique hash-id for the error message
statusinteger Required
Error response status code
codestring Required
Error response code
titlestring Required
Error response title
detailstring Required
Error response detail
sourcearray,string
Source defines the multiple error messages
Show child attributes
timestampstring Required
Response timestamp
401
Object
Unauthorized
| **Code** | **Title** | **Detail** |
| ---------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| token_required | Token Required | Access denied due to invalid token on header. |
| invalid_tenant | Invalid Tenant | Access denied due to invalid tenant code. |
Response Attributes
idstring Required
Unique hash-id for the error message
statusinteger Required
Error response status code
codestring Required
Error response code
titlestring Required
Error response title
detailstring Required
Error response detail
sourcearray,string
Source defines the multiple error messages
Show child attributes
timestampstring Required
Response timestamp
403
Object
Forbidden
| **Code** | **Title** | **Detail** |
| ---------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| restricted_resource | Restricted Resource | Access denied to the resource. If your access key and source IP is correct, it would be because of `X-Auth-User-ID` is not passed on header. |
| unauthorized_access | Unauthorized Access | Transaction does not belong to user. |
| upload_not_required | Upload Not Required | No additional document required for this transaction. |
