Configure Webhook listeners
Configure webhook listeners (also known as HTTP push API) to enable your microapps to provide near real-time data to your end users. Configuring a webhook allows your apps to deliver data to other applications at a much quicker rate than synchronization from the Microapp platform side. The maximum size of a webhook request body that can be handled by MA server is 64 kb.
Adding webhook listeners requires you to be familiar with your target application System of Record and have the necessary tools and administration privileges set up to configure your webhooks in those locations.
Configure your webhooks after you have set up your integration via Data Loading and follow these steps:
Click Webhook Listeners on the left hand bar of the HTTP Integration screen:
- Enter your desired webhook name.
- Select Copy to copy the webhook URL for use in your target System of Record administration interface.
You can select either the Token authorization method or None when configuring your authorization method. To configure the token method follow these steps:
- Select Token in the Authorization method menu.
- Select Generate token and then select Copy to add the token to your clipboard for use in your target System of Record administration interface.
Select read token from to choose from:
- Custom header
- Query parameter
- Authorization header
- Define either the Name or the Prefix depending on your selected read method.
The token is now set up.
When configuring your Webhook listeners, use the following definitions to build your calls:
- PUT is used to update existing resource.
- POST creates new subordinate resources, therefore, POST methods are used to create a new resource in the collection of resources. Both PUT and POST deletes data from child tables using the primary key info from of root table. It then replaces an existing record or inserts a new one.
DELETE is used to delete resources.
DELETE has two endpoints:
recordIdis the value of the primary key of the record in the root table to be deleted. Records in the child table are deleted accordingly.
id2represent the values of the composite primary key of the record in the root table to be deleted. Records in the child table are deleted accordingly.
- PATCH requests are used to make partial updates on a resource.
Define data structure
You can define your data structure in a similar method described when you Fetch data structure during Data Loading configuration. For more information see Configure the integration.
To define your webhook data structure follow these steps:
- Set your desired data retention period. All entries that are older than this date are deleted. Each saved entry contains its date and time of modification. That is
lastModified. This date and time is used to decide which entries to delete.
Select Generate Tables.
The Generate Tables screen opens.
Paste your JSON sample request from your target application System of Record here.
- Set your base name of created tables.
- (Optional) set the root path if necessary.
- Select Generate.
With this process complete alongside the configuration measures completed in your target application System of Record administration, select Add.
Your webhook is now configured.
Webhook listeners support custom scripts configured in the HTTP integration scripting feature.
You can find additional information on developing and implementing your own scripts at the Citrix Developer Portal.
Show Webhook logs
Use Webhook logs to view a history of requests and errors from all webhook endpoints. You can filter by webhook name and state, such as success, error, or all. For the purposes of performance, only the last 10 webhook log entries are kept for review in the webhook logs screen.
- From the Manage Microapps page, select the menu next to the integration that you want to view integration logs for.
- Select Webhook logs.
- Review the entries, and select from the menu to filter as required.