Daniel F

Theming has been a core component of Invision Community since its inception, and this continues with Invision Community 5, but in a very different way.
If you haven't already seen Ehren's blog on the new Theme Editor, please do take the time to watch it. The all-new theme editor reduces the complexity of theming by taking complex concepts like HSL CSS variables into a pretty slick UI that almost any Invision Community owner can use to personalise or brand match to any existing properties.
Ehren will talk more on the technology behind the theme editor in another developer blog soon, but the short version is that the CSS framework has been completely rewritten from scratch with a new approach to how CSS classes interact with page elements.
Of course, if you're reading this, you'll want to know what tools you have for more advanced theming in v5.
Custom templates and template hooks
Invision Community 5 merges the concepts of custom templates and template hooks into a single feature. In the past, you could edit templates directly and create theme hooks. With Invision Community 5, these features are replaced with the new custom template system.

You can create new templates, which you can use in other custom templates via the short tag: {customtemplate='key'}. 
You can also hook into specific areas with a custom template allowing you to insert code before the opening tag, after the opening tag, before the closing tag or after the closing tag.
 
CleanShot 2023-10-19 at 13.17.16.mp4
For example, if you wanted to add something custom before the reply editor when viewing a topic, you would target that area like so:

The result, when viewed on the front end, is as follows:

These hookable areas are defined by a special tag that we add to the core templates. We would expect a lot of requests through the beta release and will likely create a request form so we can process them. We will try and accommodate as many areas as possible.
While direct template editing is no longer possible in Invision Community v5, the new custom template and hook system allows you to add new functionality, while the new CSS framework makes it easier to target and change elements without the need to edit templates.
We also added a suite of new development tools to enable you to target menus, data attributes and other areas where developers commonly had to edit templates before.
The good news is that now custom templates are not built on top of our 'master' template engine; they are virtually upgrade-proof and do not require manual merging.
Theme Designer Mode
Those who create themes for others have some extra tooling to enable them to build truly custom themes.
Even though the theme editor has space for custom CSS, there is always a need for CSS that your customers cannot edit, and Invision Community 5 has a special area for that once Theme Designer Mode has been enabled.

You also can add any ad-hoc javascript for when you want to hide elements or provide custom interactions.
As direct CSS editing and direct template editing are no longer possible with Invision Community 5, there is no need for a 'sync' tool to copy from the filesystem.
Conclusion
The new front-end theme editor is now the primary way to manage themes. This is where you upload logos and toggle settings.
As you can see, theming may look different in Invision Community v5. Still, the new custom templates, theme designer tools and UI extensions provide a lot of functionality that means you can do nearly everything you did in v4, but often in an easier way.
I'm sure you'll have many questions, so please add them below, and we'll do our best to answer them for you.

Welcome to our October developer's update!
After a frantic few months of working on the PHP8 transition, we made it across the line with our November release (4.7.4), which requires PHP8 as the minimum version.
Reminder: Invision Community 4.7.4 will disable plugins and applications that are not compatible with PHP8, and the only way to re-enable them is to upload a new version. Hopefully, you've had time to get your apps updated and through our review system. Thank you again for your patience throughout this process. The next big change will be PHP8.2, which changes how DateTime is overloaded, but that's a headache for 2023.
Make sure you use PHP8 with your local development environments and set your IDE to PHP8 if it has this feature.

If you need a refresher on the new functionality that comes with PHP8, then I recommend this blog or this video.
Impacting Code Changes
We've been very careful to avoid adjusting any parameter signatures this month, and we will endeavour to get you plenty of notice if we need to change things on a central method.
The main change to look out for this month is the change to IPS\<app>\extensions\core\ContentRouter
/** * @brief    Can be shown in similar content */ public $similarContent = TRUE; We added a public method variable to note if this content type can be used in the similar content widget. This change fixes a bug where some content types, like Commerce packages, appeared in the widget but with incompatible metadata.
Holiday Release Schedule
It's that time of year when we start planning releases around the Thanksgiving and Christmas holidays. We try and avoid larger releases at this point in the year to reduce the stress levels on our support and development teams. No one wants a crisis during what should be a relaxing time with family and friends.
The current schedule looks like this:
2 November: November release (4.7.4) First week of December: Smaller bug-fixing release (4.7.5) Early January: Patches or a very focused bug-fixing release (4.7.5.1/4.7.6) February: Full monthly releases as usual. Deprecations
This month, we removed the older guest page caching. Those looking for a better replacement are having success with a free plan from Cloudflare.
We also removed the Facebook promotion tool as Facebook keeps raising the bar for approval, and we want to focus on a Zapier replacement coming soon. Finally, we also removed Vigilink, which no longer works.
Other News
The November release features commits from @HeadStand, who is working with us part-time to chew through the backlog and work on feature improvements. She is a coding machine and has filled my inbox with GitHub pull request notifications which I'm very happy to receive!
That's all for this month, happy developing!

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Welcome to our May developer's update!
May has been a bit of a whirlwind as we worked through the cloud platform feature set along, the backlog of existing issues reported to us and a new feature coming to all platforms.
Along with the usual bug fixes in the backlog, we also worked on a few popular requests, such as adding hCaptcha as a new CAPTCHA option. We've seen this battle spam bots much more effectively than the existing methods, so if you're being hit by a lot of spam, consider upgrading to 4.7.0 and enabling hCaptcha.
Jordan announced the new alerts feature here. It's a new way to reach out to members (or entire groups) and ensure they read and act on the alert. Many configuration options make it a very flexible feature useful for one-off alerts to a single member. It can also be used as a welcome message as part of your onboarding process.
Invision Community 4.7.0 (also known as the June release) will have tentative support for PHP 8.1. While we have tested the core apps extensively, you should check with any third party developers to ensure their apps are PHP 8 ready. We intend to move to PHP 8.0 as the minimum version later this year (and our dev team is excited about this, they can't wait to use mixed return types, which is as exciting as it gets for us most days).
Here is the full change log for the June release.
Core - Added alerts functionality. - Added hCaptcha support. - Added a setting to exclude groups from search logs. - Added support for PHP 8.1. - Increased minimum PHP version to 7.4 and recommended version to 8.0. - Added a solved/unsolved filter for activity streams. - Changed Marketplace search to 'AND' mode for more accurate results. - Changed 'member download' to output comma-separated values instead of tab-separated values to be consistent with member import. - Changed the poll behaviour to allow everybody to view the poll result of closed polls. - Improved the email editor to show the full email name while editing it. - Updated CKEditor to 4.19.0. - Moved the stream subscription links to an own menu item. - Fixed an issue that may prevent attaching audio files to content. - Fixed a minor typo in the forms.css template. - Fixed upload area not showing on minimized editors for guest users. - Fixed an issue where post counts were incremented even when a new item was held for approval via the profanity filters. - Fixed an issue where filters and sort options do not persist between deleting members in the Admin CP. - Fixed an issue where sitemap may show entries from offline applications. - Fixed an issue where support account may show as the latest registered member. - Fixed an issue where the upgrade process would fail to finish because of duplicate DB queries. - Fixed an issue where the default streams had a broken time period. - Fixed an issue where widgets may not be available even with enabled apps. - Fixed an issue where status updates where appearing as search results even if the user had no permissions to view profiles. - Fixed some issues with the online status indicator in account settings. - Fixed an issue with deleting bulletins when deleted remotely. - Fixed an issue where clicking on the reorder-menu link in clubs can add multiple reorder icons. - Fixed an issue where managing Widgets via the AdminCP > Applications > Dev Center meant that Yes/No toggles could fail to work. - Fixed an issue where the block submission filter failed to catch loose matches when in the middle of a word and/or using non latin characters. - Fixed an incorrect link on a modal popup when trying to follow a member when the member hasn't configured their preferences. - Fixed an issue fetching Clubs via the REST API when they have custom fields. - Fixed an issue when viewing a list of awarded badges if one was earned by a rule in a deleted application. - Fixed a missing `</ul>` in the poll template. - Fixed an issue where the 'approved content' notification (and any newly added notifications) might not have valid default options until edited via AdminCP. - Fixed missing padding on the AdminCP file locations modal. - Fixed some UX issues when revoking an OAuth access token. - Fixed an issue where non-image attachments inserted via the editor may not download. - Fixed a missing language string in member history when spam defense system applies moderation to a new member. - Fixed an issue with 'solved' push notifications linking to a non-existent page. - Fixed an issue with the Zapier Extension when PHP was running in CGI mode. - Fixed an issue where rank progress would still show in profiles when no ranks exist. - Fixed an issue using the ban filters in member group promotion rules. - The Editor Preview Button was removed from ACP Editors. - Removed the deprecated FX Country code from the Geolocation class. - Removed the ability to rebuild existing attachment thumbnails due to an incompatibility with content attributes required for lazy-loading. - Removed the SQL Toolbox. Forums - Improved the fluid-mode per forum filters to remove a page reload, and to reverse the filter checkbox status to make it clear which are being viewed. - Fixed an issue where checking an archived topic for new replies when you ignore other members may always show a 'new' post has been created. - Fixed an issue where top posters in the topic statistics section may show in the wrong order. Gallery - Fixed an issue with the followed Gallery Images page. - Fixed an issue with rebuilding thumbnails on legacy communities where the original image may no longer exist. Pages - Added the missing `__indefart_cms_page` language string. - Added copy buttons on the modal that displays the HTML to copy to embed blocks elsewhere. - Improved search indexing speed of comments when Elastic Search is used. - Fixed an issue where sorting by a numerical field could duplicate the option with an incorrect label. - Fixed issue with 'image upload' block carousels not working in the sidebar - Fixed an issue where custom Yes/No fields when used as a database filter were ignored when further sorting. - Fixed an issue where categories could have broken breadcrumbs. - Fixed an issue where entering a blank value for a required decimal field would save the value as 0. - Fixed an issue where using a Yes/No field as a database filter may cause the custom sort form display to not allow toggling of the Yes/No field. - Fixed an issue that allowed duplicate template group names in some circumstances. - Fixed an issue where who's online widget blocks would throw an error while creating or editing them in the ACP. Converters - Fixed an issue rebuilding some profile photo images. - Fixed an issue where vBulletin `[video]` tags would not be parsed if the video ID contained a hyphen. Commerce - Added ability to require an active subscription to use community. - Added support for Stripe - Apple Pay Domain Verification Files on Cloud. - Improved Subscriptions including up/downgrading to other subscriptions and offering limited free subscriptions. - Improved performance when updating a large number of existing purchases. - Removed deprecated Amex Express checkout options. - Fixed some issues that can occur when requiring a subscription or product to be purchased during registration. - Fixed an issue where a card would not be auto-billed if the customer did not have an address. - Fixed a niche issue where a renewal invoice (for manual payment) would not be generated if a PayPal Subscription was cancelled on an active purchase. - Fixed an issue where account credit would not be used for an invoice if the credit remaining was the exact value of the invoice. - Fixed an issue calculating the next renewal date when upgrading between Subscriptions that may use a different renewal period (i.e. monthly vs annually). Calendar - Fixed an issue where the day view wouldn't show todays events when it's being used as the default calendar view. Downloads - Fixed an issue where change logs may show the wrong published date if the file description had been edited since the last update. - Fixed an issue where creating a downloads category with the "Keep previous versions?" Setting being disabled would result in a DB error. Platform - Added real time and historic trending data in sidebar blocks and leaderboard. REST, Webhooks and Zapier - Fixed an issue where the 'hidden' content item filter would be ignored for any content type except topics. - Fixed an issue where the date parameter for the 'Edit a topic' endpoint was not updating topic/post post date. Key points for developers are as follows:
Added PHP 8.1 support; however, we have silenced deprecation errors for core applications and system directory as we work through those in the following releases. Updated Whoops to 2.14.5 Fixed an issue where managing MFA in the Account Settings would result in an IN_DEV CSRF key warning. Fixed an issue where you could not pass variables to the {hextorgb} theme plugin. Fixed an issue where creating or editing a forum with IN_DEV being enabled would return an error. Fixed an issue with ips.ui.infiniteScroll.js when using FURLs. Fixed a syntax error in the core unsubscribeStream.txt email template. Member filters will only be processed/visible for group promotions if they have a matches() method. That's it for now; see you on the forums!

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.
 

Webhooks allow other services and applications to stay in sync with your community data or to perform an action after a specific event occurs in your community.
Webhooks are a performant alternative to continuously polling for changes to the IPS REST API.

For example, a webhook can notify your service when a new topic is created so that your app can perform then any further actions.
Webhooks can also be used to connect your community with Zapier, IFTTT or Integromat, so that any event which is covered by webhooks can trigger any further actions.
Common webhook use cases
Sync your member base with 3rd party newsletter lists Sync your Event RSVP with your Online Ticketing System Update your inventory after a purchase was made You can find the webhook functionality in the AdminCP, under the API section. There is also a useful webhook reference built in.


Setting up a webhook
Setting up a webhook is straightforward. Log into your AdminCP, then navigate to System > API.
The target URL would be defined by the application you wish to fire events to. For example, in Zapier, you can set up a trigger to listen for a webhook event via a custom URL.

Once you have entered the URL, simply check which events you'd like to fire to that URL. Zapier will ask you to test the URL, so to do this simply invoke the action which fires the webhook event, such as creating a test topic.
Documentation
If you are looking to add webhook events into your own custom code and applications, please see our documentation here.
Webhooks will be implemented in 4.6.10 and will be enhanced frequently.