Skip to main content

Documentation Index

Fetch the complete documentation index at: https://partner-docs.nuwebgroup.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Integration settings manage the third-party services that are available across a reseller’s portfolio. Some integrations require API keys or credentials to be configured at the reseller level before companies can enable them — the reseller provides the platform-level credentials, and companies configure their own integration-specific settings. This two-level approach means:
  • Reseller administrators set up shared credentials and API keys (e.g. a Google Maps API key) once
  • Company administrators enable individual integrations from their admin settings and configure company-specific options
Integrations also depend on feature flags — the relevant feature flag must be enabled on both the reseller and the company before an integration can be activated.

​
Available Integrations

​
Event & Compliance Integrations

These integrations sync event and ticket data with external regulatory or government systems.
Dubai Tourism and Commerce Marketing — company event data is automatically synced with DTCM performance data.Reseller setup: No reseller-level credentials required.Company setup: Enable the integration and provide DTCM API credentials (API key, token API key, client ID, client secret, seller code). Supports live and test modes.Feature flag: DTCM

​
Refund Protection Integrations

Refund Protect Group — enables the Protect Group integration for refund protection during checkout. Customers can opt in to refund protection when purchasing tickets.Reseller setup: Provide Protect Group credentials (client ID, client secret, API key, and vendor code) for both live and test environments.Company setup: Enable the integration, configure opt-in requirements, set minimum order values per currency, assign a tax band, and set a deadline (hours before event) after which protection is no longer available.Feature flag: Refund Protect Group Integration. Modes: Standard or Anonymous. Conflicts with Manual Refund Protection.

​
Platform Service Integrations

These integrations are configured at the reseller level and provide shared services across all companies.
IntegrationReseller SettingPurpose
Google MapsGoogle Maps JavaScript API keyEnables dynamic maps on event pages, custom map themes, and multi-marker event browse pages. Without dynamic maps, the platform uses static map images
what3wordswhat3words API keyEnables what3words address format as an alternative to traditional addresses
Misr SMSMisr SMS credentials (API key + sender name)Companies can use the reseller’s Misr SMS account for order approval/rejection notifications
VATstackVATstack secret keyProvides VAT compliance validation for EU transactions

​
Social Login Integrations

Social login credentials are configured at the reseller level to enable customers to sign in using third-party accounts.
ProviderCredentials Required
FacebookClient ID, client secret
GoogleClient ID, client secret
TwitterClient ID, client secret
AppleClient ID, private key, private key ID, team ID
When social login credentials are configured on the reseller, companies under that reseller can offer social login to their customers during checkout and account registration.

​
Email Settings

New in Release 45
Reply-to email addresses can be configured at both the reseller and company level. When set, all outgoing platform emails (order confirmations, refund notifications, etc.) include this address as the Reply-To header, so customer replies are directed to the correct inbox.
LevelSettingEffect
ResellerReply-to emailSets a default reply-to address for all companies under the reseller
CompanyReply-to emailOverrides the reseller-level reply-to for this specific company
These settings are optional. When no reply-to email is configured, customer replies go to the platform’s default sending address.

​
How Integrations Flow from Reseller to Company

Integration enablement follows a three-step chain: 
1. Reseller provides credentials / API keys (where required)

2. Feature flag enabled on reseller → then on company
   └── Company can now access the integration

3. Company administrator enables and configures the integration
Each step must be complete before the next is available. A company cannot enable an integration unless:
  • The reseller has provided any required credentials
  • The relevant feature flag is enabled on both the reseller and the company
  • The company has the necessary permissions
If a child company has global transactions enabled with its parent, integration settings that relate to payment processing are managed through the parent company’s configuration.

​
Integration Conflicts

Some integrations are mutually exclusive and cannot be active on the same company at the same time:
IntegrationConflicts With
SzamlazzConditional tax bands
Refund Protect GroupManual Refund Protection
Manual Refund ProtectionRefund Protect Group
These conflicts are enforced through the feature flag system. Enabling one automatically prevents the conflicting option from being enabled.

Feature Flags

Enable integration-related feature flags at the reseller and company level.

Gateway Settings

Payment gateway configuration, which is separate from integration settings.

Parent-Child Companies

How global transactions affect integration settings for child companies.