Partner Callback Event

Once the EAR is triggered, partner is informed of the request's transitions across different states via registered callback events. These callback events are sent out for all status transitions for a particular EAR to the URL shared by the partner.

Callback Event

{
  "message": "String",
  "delivery_id": "String",
  "request_id": "String",
  "status": "Enum",
  "type": "Enum",
  "status_code": "Integer",
  "time": "Long",
  "passcode": "Integer"
}

Status

Value	Description
ACKNOWLEDGED	All the sanity checks for the EAR have passed.
MATCH	EAR is valid and matching MyGate user has been identified.
INITIATED	MyGate user approval process has been initiated.
APPROVED	EAR approved by MyGate user.
CHECKIN	Partner executive has entered the MyGate community for delivery.
CHECKOUT	Partner executive has exited the MyGate community after delivery.
COMPLETED	EAR handling has been closed successfully.
DECLINED	EAR declined by MyGate user.
REJECTED	Invalid EAR received from partner.
DUPLICATE	Non unique delivery identifier send in EAR by partner.
NOMATCH	Unable to find matching MyGate user for valid EAR.
FEATUREDISABLED	Express Entry disabled for community or user.

Geofence

Partner Match