| ACKNOWLEDGED | 20 | Request successfully received | All the sanity checks for the EAR have passed. |
| MATCH | 22 | EAR is valid and matching MyGate user has been identified | EAR is valid and matching MyGate user has been identified. |
| INITIATED | 21 | Entry approval validation process started | MyGate user approval process has been initiated. |
| APPROVED | 24 | Entry approved by user | EAR approved by MyGate user. |
| CHECKIN | 27 | Delivery executive/cab has checked in | Partner executive has entered the MyGate community for delivery. |
| CHECKOUT | 28 | Delivery executive/cab has checked out | Partner executive has exited the MyGate community after delivery. |
| COMPLETED | 29 | Request completed successfully | EAR handling has been closed successfully. |
| DECLINED | 26 | Entry request denied by user | EAR declined by MyGate user. |
| REJECTED | 40 | Request is Invalid. Please check message for details | Invalid EAR received from partner. |
| DUPLICATE | 42 | Duplicate request received | Non unique delivery identifier send in EAR by partner. |
| NOMATCH | 23 | We were not able to find a matching user record in our system | Unable to find matching MyGate user for valid EAR. |
| FEATUREDISABLED | 43 | This feature is disabled | Express Entry disabled for community or user. |
| LEAVEATGATE | 31 | Entry asked to deliver at gate by user | |
| EXPIRED | 52 | Request expired | EAR request is expired. |
| INITIATIONERROR | 50 | There was a problem with processing the request. Please check the request body | Error in processing request. |