📥 Generate Notification Request API – Request Parameters

The generateRVN API expects a JSON request body with the following structure and attributes.
Refer to this section while forming your API call.

🔗 Endpoint

POST https://REL-ID-VERIFY-SERVER:VERIFY-PORT/generateRVN.htm

🔐 Authentication

Use one of the following in the request headers:

• Basic Auth: Authorization: Basic <base64-encoded-credentials>
• OAuth2 Token: Authorization: Bearer <access_token>

🔑 Mandatory Parameters

🧩 Optional Parameters

🧠 Structure: msg (Multilingual Content)

"msg": [
  {
    "lng": "English",
    "subject": "Login Attempt",
    "message": "You are attempting to login to Netbanking Retail",
    "label": {
      "Accept": "Approve",
      "Reject": "Disapprove"
    }
  }
]

📝 label in msg

The label object inside msg defines the localized button labels that the user sees for each action in that language.

• It must have a one-to-one mapping with the label values defined in the actions array.
• The keys in msg.label must exactly match the label fields in the actions array.
• The values are the display names for each action in the selected language.

📌

The number of label entries in each language must match the number of defined actions.

🔘 Structure: actions

"actions": [
  {
    "label": "Accept",
    "action": "Approved",
    "authlevel": "1"
  },
  {
    "label": "Reject",
    "action": "Disapproved",
    "authlevel": "0"
  }
]

• label: Internal identifier used for mapping with msg.label
• action: Response text sent back in action_response
• authlevel: Level of authentication required (0–4)-- 0: No auth-- 1: Password-- 3: Device LDA-- 4: Server Biometric
• Stepup Authentication for Actions

📬 Structure: notification_msg

"notification_msg": {
  "message": "You have a login attempt to review",
  "subject": "Login Notification"
}

💡 Best Practices

• Keep both message and subject short and meaningful.
• Do not include user identifiers, transaction amounts, or account numbers.
• Think of this as a "doorbell" to get the user's attention, not the full message.

📌

The actual transaction details will be securely fetched and shown inside the REL-ID app, not in this notification_msg.

⚙️ controls (OTP & Workflow Config)

OTP Controls

Secure Token Generation

🧩

These parameters define exactly how your notification behaves, looks, and how the user interacts with it.

🔐 Generate Notification Request Samples

This guide provides sample request bodies for generating two types of REL-IDverify push notifications:

• ✅ Approve/Reject Login Request
• 🔢 OTP-based Transaction Approval

🔗 Endpoint

POST https://REL-ID-VERIFY-SERVER:VERIFY-PORT/generateRVN.htm

📤 Request Headers

🔽 Approve/Reject Login Request

{
  "msg_id": "txn-login-20250515",
  "enterprise_id": "YOUR_ENTERPRISE_ID",
  "user_id": "testuser",
  "expires_in": 180,
  "notification_msg": {
    "message": "Login attempt detected",
    "subject": "Login Verification"
  },
  "msg": [
    {
      "lng": "English",
      "subject": "Login Attempt",
      "message": "You are attempting to login to your account. Do you approve?",
      "label": {
        "Approve": "Approve",
        "Reject": "Reject"
      }
    }
  ],
  "actions": [
    {
      "label": "Approve",
      "action": "Approved",
      "authlevel": "1"
    },
    {
      "label": "Reject",
      "action": "Rejected",
      "authlevel": "0"
    }
  ]
}

🔽 OTP-based Transaction Approval Request

{
  "msg_id": "txn-otp-20250515",
  "enterprise_id": "YOUR_ENTERPRISE_ID",
  "user_id": "testuser",
  "msg_type": "OTP",
  "expires_in": 180,
  "notification_msg": {
    "message": "Transaction requires your approval",
    "subject": "Approve Transaction"
  },
  "msg": [
    {
      "lng": "English",
      "subject": "Approve Transaction",
      "message": "Use OTP $$OTP$$ to approve your transaction of ₹5,000",
      "label": {
        "Submit": "Submit"
      }
    }
  ],
  "actions": [
    {
      "label": "Submit",
      "action": "OTP_SUBMITTED",
      "authlevel": "0"
    }
  ],
  "controls": {
    "otp": {
      "attempts": 3,
      "hash_spec": "sha256",
      "otp_spec": "N-6"
    }
  }
}