🔄 Check Notification Status API Documentation

The Check Notification Status API (getRVNStatus) allows an enterprise to poll the Ditto 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.

🔗 Endpoint

GET https://<REL-ID-VERIFY-SERVER>:<VERIFY-PORT>/getRVNStatus.htm/<notification_uuid>

🔐 Authentication

Supports Basic Auth or Bearer Token:

Authorization: Basic <base64(username:password)>

Authorization: Bearer <access_token>

📥 Request Parameters

Parameter	Type	Required	Description
`notification_uuid`	string	✅	UUID received from `generateRVN` API response. Used as a path parameter.

No body is needed for this GET request.

✅ Sample Success Response

{
  "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>"
}

❌ Sample Failure Response

{
  "response_code": 1,
  "error_code": 3558,
  "error_message": "Notification Identifier is not found"
}

🧾 Response Attribute Table

Attribute	Type	Always Present	Description
`user_id`	string	✅	Ditto ID user who received the notification.
`notification_uuid`	string	✅	UUID for this specific notification.
`response_code`	int	✅	0 for success, 1 for failure.
`status`	string	✅	One of: `ACTIVE`, `UPDATED`, `EXPIRED`, `CANCELLED`.
`delivery_status`	string	✅	Notification delivery status.
`action_response`	string	❌	Only present if user responded.
`is_ds_verified`	boolean	❌	Only present if digital signing is enabled.
`msg_id`	string	✅	Message ID originally sent in generateRVN.
`verification_mode`	string	✅	Mode of verification used.
`original_verification_mode`	string	❌	Included if fallback/escalation occurred.
`create_ts`	string	✅	When the notification was created.
`update_ts`	string	❌	When the user took action.
`expiry_timestamp`	string	✅	When the notification will expire.
`client_ip_address`	string	❌	IP of device used to respond.
`jwt`	string	❌	Only included if `GENERATE_JWT` workflow was used.

📖 Response Values Explained

🔄 `status` – Notification Lifecycle

Value	Meaning
`ACTIVE`	Notification is still active and awaiting user response.
`UPDATED`	User has acted on the notification (e.g., Approved or Rejected).
`EXPIRED`	Notification was not acted on within the `expires_in` duration.
`CANCELLED`	Notification was cancelled via the Cancel Notification API.

🚚 `delivery_status` – Push Notification Delivery

Value	Meaning
`NONE`	Push was not initiated (e.g., test mode or failure).
`PARTIALLY_NOTIFIED`	Delivered to some of the user's devices.
`NOTIFIED`	Delivered to all registered devices successfully.
`FAILED_TO_NOTIFY`	Delivery failed on all targets (e.g., device not reachable).

🧾 `action_response` – User Action

Value	Meaning
`Approved`, `Rejected`, etc.	Based on your `actions[]` configuration during notification creation.
`NONE`	No action was taken by the user before expiry.

✅ `is_ds_verified` – Digital Signature Validation

Value	Meaning
`true`	The user's response was signed and successfully verified.
`false`	Signature verification failed or not applicable.
(absent)	User hasn't responded yet or digital signing was disabled.

🧪 `verification_mode` and `original_verification_mode`

Value	Meaning
`REL-ID`	Verification was done via Ditto ID secure app flow.
`OTP`	Verification fallback to OTP.
`SMS`	Fallback via SMS if mobile app was unavailable.
(others)	Custom enterprise-specific verification types if supported.

⚠️ Error Codes

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

🧠 Notes

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.

📌
ThegetRVNStatus API is ideal for transaction state monitoring, fallback to async callback, or audit logging of user responses.

🔄 Check Notification Status API Documentation

🔗 Endpoint

🔐 Authentication

📥 Request Parameters

✅ Sample Success Response

❌ Sample Failure Response

🧾 Response Attribute Table

📖 Response Values Explained

🔄 status – Notification Lifecycle

🚚 delivery_status – Push Notification Delivery

🧾 action_response – User Action

✅ is_ds_verified – Digital Signature Validation

🧪 verification_mode and original_verification_mode

⚠️ Error Codes

🧠 Notes

ThegetRVNStatus API is ideal for transaction state monitoring, fallback to async callback, or audit logging of user responses.

🔄 `status` – Notification Lifecycle

🚚 `delivery_status` – Push Notification Delivery

🧾 `action_response` – User Action

✅ `is_ds_verified` – Digital Signature Validation

🧪 `verification_mode` and `original_verification_mode`

The`getRVNStatus` API is ideal for transaction state monitoring, fallback to async callback, or audit logging of user responses.