Triggering an Notification Event

A notification event that has been successfully created and saved can be run or executed by hitting the cURL request.

From the Notification Events section:

  1. Find the Notification Event you want to trigger or implement from the landing page or create a new event by clicking on "Create+"
  2. Once created and promoted to live, you can trigger a notification event:
    1. Within the Notification Event creation page, click on the "<>" icon in the top right corner. This will open up the Notification Event Playground page.
    2. From the landing page, click on the "<>" on the top right corner of the corresponding Notification Event card. This will open up the Notification Event Playground page.

Notification Event Playground

The notification playground allows you to visualize, trigger and view logs of the test notification that you have triggered from Fyno's application. This makes your testing and visualization simple and easily accessible, all in one place!

Let's have a look at the Notification Playground and how to use it most efficiently.

On clicking on the "<>" icon for any notification event from the Notification Event landing page, you will see the following:

  1. Notification Event: Gives you the option to select a notification event from the ones you have created, in a drop-down. Select the one you would like to trigger. You can also open the notification event in a separate browser by clicking on the icon next to the Event name.
  2. Trigger using: Select one of the destination options:
    1. Distinct ID - Distinct ID is the user profile identifier unique to that recipient.
    2. Manual: On selecting manual you would be able to add one of the below details for the recipient.
    3. Both: The API will understand to accept either the Distinct ID or the recipient details directly.
  3. Additional data: This allows you to provide the data for testing the "Placeholders" with dynamic values, which would have to be written in JSON.
  4. Preview: The Preview tab shows the details of the notification that is about to be triggered. You can take it to the next level and see how it looks for each channel by clicking on the respective icon. For Email, you can preview both Desktop and Mobile views.
  5. Preview with Conditional Templates : If you have used conditional templates in the notification event, you will see the Preview, as shown below. The template will be selected based on the satisfaction of a particular condition.
    1. Using Template: "Template_name" (template version)
    2. because "placeholder" matches the condition
  1. Command: The command tab displays the cURL command that has been generated for this Notification Event and can be copied and placed into your code easily.
  2. Logs: When the notification event is triggered, the logs that would be generated can be seen on the logs tab as well for a quick overview of the status.
  3. Template: Displays the name of the template that is being used for the respective Notification Event. Click on the pop-out icon to revisit the template and make edits.

Copy your All-In-One API

In the pop-up that comes when clicking on "<>" for the Notification Event, you will be able to copy the API by clicking on the Copy button on the top right corner of the cURL window.

Test your All-In-One API

From the same notification event's pop-up, find the "Send" button on the bottom left. This button will be available to click once the API Key and the To fields are filled in.

Use Batch Send

Batch Send or Batching allows you to use the same Notification Event API to send information to multiple users, like a campaign.

When creating a Notification Event, if the check box is marked for Use Batch Send, then this Event API can be used like a campaigning or bulk send API.

📘

Notice that your API will also be appended with "Bulk" when you select the Batch Send option.


How to receive delivery reports

If you want to receive delivery reports in your system or any third party tool, you need send callback object in the API call as shown below

{
   "event": "YOUR_EVENT_NAME",
   "to": { // you channel destination },
   "data": {  // your template placeholders  },
   "callback": {
       "custom_id": "YOUR_CUSTOM_ID_VALUE",
       "custom1":"YOUR_CUSTOM_VARIABLE_1",
       "custom2":"YOUR_CUSTOM_VARIABLE_2"
       "allowlist_url": ["DynamicWebhookSite", "Mixpanel"]
    }
}

ParameterType and Value
enableDefault: true,
true: enable delivery status over callback.
false: disable delivery status over callback
custom_idstring; an alpha-numeric unique identifier of your notification.
Length: 200 characters
OR
number; numeric unique identifier of your notification.
Length: 20 digits
custom1string; (Optional) additional information that you want to tag your notification.
Example: order-id
Length: 50 characters
custom2string; (Optional) additional information that you want to tag your notification.
Example: Category
Length: 50 characters
allowlist_urlstring; (Optional) Allowlist url name where you want to receive delivery reports. Can be array of allowlist url names if you want the delivery reports in multiple URLs.
Example: ["DynamicWebhookSite", "Mixpanel"] . If you have only 1 allowlist URL, it will be automatically will be sent to that URL.