This documentation will explain iVvy notifications. In our system, it is referred to as a subscription and each event type is a notification.
For terminology, you subscribe to an endpoint. There are several endpoints available and will provide the changes related to that specific endpoint.
iVvy offers notifications that will send you details of a specific object that you wish to subscribe to. There are several notifications available and you may subscribe and unsubscribe to whichever notification is necessary for your development.
You can test using this fantastic website:
This website will assist you in receiving webhook information during your testing.
Following on the instructions we have available on our website:
You can use the following subscription endpoints:
The request body to be provided to the endpoints is a JSON body with the key being the name of the notification endpoint you wish to subscribe to / unsubscribe from. And the value being the URL you are using to receive our notification.
"[ENDPOINT NAME]": "YOUR WEBHOOK URL"
/api/1.0/account?action=subscribeToNotifications - POST
This endpoint will allow you to subscribe to a new notification type.
The response that you will receive will be very similar to this. It will show you the current status of all of the notifications that you currently subscribe to. In the example below, this is a response when subscribed to the companies notification.
When you have subscribed to a notification, the endpoint you have provided will receive a message containing specific information about the notification you have subscribed to. Below is an example of a message from the iVvy API.
"Message": "You have chosen to subscribe to the topic arn:aws:sns:ap-southeast-2:232528047142:iVvy_Account5_d7336c818a0bf60d087_NotifCompanies.\nTo confirm the subscription, visit the SubscribeURL included in this message.",
In the JSON object above, you’ll notice that there is a message and it will say something similar to the below:
To confirm the subscription, visit the SubscribeURL included in this message
There is a SubscribeURL attribute. You will need to contact this endpoint which will complete the registration of the subscription for that URL. You will not receive any notifications until you have contacted this endpoint.
/api/1.0/account?action=unsubscribeFromNotifications - POST
Note: Use the body request that you used in the subscribe endpoint.
Should you wish to no longer receive notifications of a particular type.
The response example above shows the result of unsubscribing each endpoint. The integer value will be one of the following: