The Check Notification Status API (getRVNStatus) allows an enterprise to poll the REL-ID server for the status of a previously triggered notification using the notification_uuid.
Related : Notification Callback
This is useful if:
No callback_url was provided in the generateRVN request.
You want to verify whether the user responded, rejected, or ignored the notification.
You require JWT or digital signature verification results post-action.
GET https://<REL-ID-VERIFY-SERVER>:<VERIFY-PORT>/getRVNStatus.htm/<notification_uuid>Supports Basic Auth or Bearer Token:
Authorization: Basic <base64(username:password)>or
Authorization: Bearer <access_token>Parameter Type Required Description notification_uuidstring ✅ UUID received from generateRVN API response. Used as a path parameter.
No body is needed for this GET request.
JSON
{
"user_id": "testuser",
"notification_uuid": "03f67f9e-ec4f-11e6-b006-92361f002671",
"response_code": 0,
"status": "UPDATED",
"delivery_status": "NOTIFIED",
"action_response": "Approved",
"is_ds_verified": true,
"msg_id": "txn12345",
"verification_mode": "REL-ID",
"original_verification_mode": "REL-ID",
"create_ts": "2024-10-11T13:00:00Z",
"update_ts": "2024-10-11T13:00:15Z",
"expiry_timestamp": "2024-10-11T13:03:00Z",
"client_ip_address": "192.168.1.2",
"jwt": "<jwt_token_if_any>"
}JSON
{
"response_code": 1,
"error_code": 3558,
"error_message": "Notification Identifier is not found"
}Attribute Type Always Present Description user_idstring ✅ REL-ID user who received the notification. notification_uuidstring ✅ UUID for this specific notification. response_codeint ✅ 0 for success, 1 for failure. statusstring ✅ One of: ACTIVE, UPDATED, EXPIRED, CANCELLED. delivery_statusstring ✅ Notification delivery status. action_responsestring ❌ Only present if user responded. is_ds_verifiedboolean ❌ Only present if digital signing is enabled. msg_idstring ✅ Message ID originally sent in generateRVN. verification_modestring ✅ Mode of verification used. original_verification_modestring ❌ Included if fallback/escalation occurred. create_tsstring ✅ When the notification was created. update_tsstring ❌ When the user took action. expiry_timestampstring ✅ When the notification will expire. client_ip_addressstring ❌ IP of device used to respond. jwtstring ❌ Only included if GENERATE_JWT workflow was used.
Value Meaning ACTIVENotification is still active and awaiting user response. UPDATEDUser has acted on the notification (e.g., Approved or Rejected). EXPIREDNotification was not acted on within the expires_in duration. CANCELLEDNotification was cancelled via the Cancel Notification API.
Value Meaning NONEPush was not initiated (e.g., test mode or failure). PARTIALLY_NOTIFIEDDelivered to some of the user's devices. NOTIFIEDDelivered to all registered devices successfully. FAILED_TO_NOTIFYDelivery failed on all targets (e.g., device not reachable).
Value Meaning Approved, Rejected, etc.Based on your actions[] configuration during notification creation. NONENo action was taken by the user before expiry.
Value Meaning trueThe user's response was signed and successfully verified. falseSignature verification failed or not applicable. (absent) User hasn't responded yet or digital signing was disabled.
Value Meaning REL-IDVerification was done via REL-ID secure app flow. OTPVerification fallback to OTP. SMSFallback via SMS if mobile app was unavailable. (others) Custom enterprise-specific verification types if supported.
Code Message Reason 2600 INVALID URI Incorrect endpoint format 2607 Invalid HTTP request Request format is not valid 3593 Regex validation failed Malformed UUID 3557 Internal Server Error Issue during server processing 3558 Notification Identifier not found UUID not found or expired 7002 Invalid method Method must be GET 7019 IPAddress is not whitelisted Calling IP is unauthorized
Use this API if callback_url is not available.
Safe to poll at regular intervals.
JWT (if included) should be validated on your backend.
Signature and IP fields are only returned if user has responded and signing is enabled.
📌 