

Events displayed in calendar view with date filtering and venue selection.
UrVenue Web Services connects your WordPress site with the UrVenue platform, allowing you to display and manage hospitality events, venue maps, and bookable inventory directly on your website.
[urvenue_ws_events] – Events calendar, agenda, and list views.[urvenue_ws_event] – Single event page with details and inventory.[urvenue_ws_map] – Interactive venue map with inventory.[urvenue_ws_inventory_item_page] – Individual inventory item page.[urvenue_ws_inquiry] – Reservations / inquiry form.[urvenue_ws_packages] – Packages listing with booking.[urvenue_ws_itinerary] – Guest itinerary view.This plugin connects to the UrVenue platform to retrieve event data, venue information, and inventory. All event and booking data is fetched from and processed through UrVenue servers. See the “External Services” section below for full disclosure.
This plugin connects to the following external services to provide event display, inventory management, checkout, reservation, and optional cache-purge functionality. Below is a full disclosure of each service: what it does, what data is sent, when it is sent, and links to its terms of service and privacy policy.
Service: UrVenue API (UvTix) — the core data platform that powers this plugin.
URL: https://uvtix.com/api/ and https://{env}.urvenue.me/v1/ and https://{env}.urvenue.me/v2/
Purpose: Retrieve venue, event, and inventory data displayed by the plugin shortcodes; manage cart and checkout operations; submit inquiry and reservation forms.
Data sent: API key (configured by the site administrator), source code (sourcecode), source location identifier (sourceloc), venue/item identifiers, and — for inquiry form submissions — visitor-entered contact information (name, email, phone, party size, and marketing opt-in flag).
When: On every page where a plugin shortcode is active; and when a visitor interacts with cart, availability, or inquiry forms. The API key and source identifiers are sent on every request. Visitor contact information is only sent when a visitor explicitly submits an inquiry or reservation form.
Service: Booketing, UrVenue’s hosted checkout platform.
URL: https://booketing.com/
Purpose: Redirect visitors to cart review, checkout, payment, and booking-confirmation pages hosted by Booketing.
Data sent: Cart code, sourcecode, sourceloc, manageentid, resellerid, providerid, language preference, and optional environment parameters — transmitted as URL query parameters during the browser redirect. No data is transmitted server-to-server by the plugin; the visitor’s browser is redirected to Booketing where payment and personal information is collected directly.
When: When a visitor clicks “Proceed to Checkout” from an inventory item or cart view.
Service: SevenRooms — hospitality reservation and guest management platform.
URL: https://www.sevenrooms.com/reservations/
Purpose: Display an embedded reservation iframe for venues that use SevenRooms as their reservation provider.
Data sent: Venue identifier (SevenRooms venue ID) and the visitor-selected reservation date, transmitted as URL parameters when the iframe loads. All reservation data entered by the visitor (name, party size, contact details) is submitted directly to SevenRooms, not through this plugin.
When: Only when a visitor views a venue item that has been configured by the site administrator to use SevenRooms as its reservation vendor.
Service: OpenTable — online restaurant reservation platform.
URL: https://www.opentable.com/restref/client/
Purpose: Display an embedded reservation iframe for venues that use OpenTable as their reservation provider.
Data sent: Restaurant identifier (rid/restref), default party size, selected date and time, and display preferences (language, color scheme) — transmitted as URL parameters when the iframe loads. All reservation data entered by the visitor is submitted directly to OpenTable, not through this plugin.
When: Only when a visitor views a venue item that has been configured by the site administrator to use OpenTable as its reservation vendor.
Service: Google Maps and Google Calendar.
URLs: https://www.google.com/maps/search/ and https://www.google.com/calendar/render
Purpose: Generate a “Get Directions” deep link to a venue address on Google Maps, and an “Add to Google Calendar” deep link for event pages. This plugin does not make any server-side requests to Google.
Data sent: For Maps — venue name and address, encoded as URL query parameters in the link. For Calendar — event name, start/end dates, and venue location, encoded as URL query parameters in the link. Data is only transmitted to Google when the visitor explicitly clicks one of these links in their browser.
When: When a visitor clicks the “Get Directions” or “Add to Google Calendar” link on a venue or event page.
Service: WP Engine API — hosting platform cache management.
URL: https://api.wpengineapi.com/
Purpose: Purge the server-side page cache for sites hosted on WP Engine after inventory data is refreshed.
Data sent: WP Engine install identifier and administrator-configured API credentials (username and password) transmitted in the HTTP Authorization header; cache type (page, object, or CDN) in the request body. No visitor data is sent.
When: Only triggered by an administrator action in the plugin settings panel, or automatically after a feed cache refresh — and only if the WP Engine integration has been configured by the site administrator. This feature is completely inactive if no WP Engine credentials are configured.
Service: User-defined webhook endpoint (e.g., Slack, Microsoft Teams, or any custom HTTP endpoint).
URL: Configured freely by the site administrator in the plugin settings. The plugin developer has no control over or visibility into the destination.
Purpose: Send alert notifications when plugin conditions occur (e.g., an inventory feed returns empty results).
Data sent: Alert message text and optional error details or API response snippets, sent via HTTP POST to the administrator-provided URL. No visitor personal data is included.
When: Only if notifications are enabled and a webhook URL has been configured by the site administrator; throttled to a maximum of one notification per alert type every 30 minutes.
Service: Meta (Facebook) — advertising and analytics platform.
URL: https://www.facebook.com/
Purpose: Push ecommerce events to a Facebook Pixel that the site owner has independently installed, enabling inventory interaction tracking in Meta Ads Manager.
Data sent: Ecommerce event name (“AddToCart”), item identifier, item name, price (USD), and quantity — relayed to the Facebook Pixel JavaScript already loaded on the page by the site owner. This plugin does not load or inject the Facebook Pixel script.
When: When a visitor adds an item to the cart. This event only fires if a Facebook Pixel script is already present on the site; it is entirely the site owner’s responsibility to ensure the Pixel is installed in compliance with Meta’s terms and applicable privacy regulations.
This plugin does not use any build tools (such as webpack, gulp, or composer) to generate its production code. All custom JavaScript and CSS files included in this plugin are human-readable, non-minified source code located in the uvcore/assets/js/ and uvcore/assets/css/ directories.
The full source code for this plugin is publicly available at:
https://github.com/urvenue/wp-urvenue-web-plugin
This plugin includes the following third-party libraries in their minified/compressed form. The original source code for each library is available at the linked repositories:
No build steps are required to use or modify this plugin. Simply edit the source files directly.