You can easily publish event information from Stager to external marketing platforms and event apps. By using our partner publication channels, your event data is pushed directly to these platforms to help you reach a wider audience.
Activating Partner Channels
Stager has an automatic link with a number of marketing platforms. Sometimes you have to agree on a fee with the platform to post your content, and in some cases, it is free.
To activate a partner channel:
Go to Settings - Integrations - Partner publication channels.
Click on a channel to read how it works and to activate it for your account. If a partner platform uses a whitelist for incoming connections, we can add this to their setup page.
Choose your visibility settings. You can set the channel to be visible on the event's Publicity tab so you can select it manually per event.
Alternatively, choose 'Upon event creation' to automatically send event information to this channel the moment you set an event status to Confirmed.
What data is shared?
When publishing to partner channels, sensitive ticketing information—such as exactly when sales go online or offline, and how many tickets have been sold—is never shared. Partners only receive public ticketing details, like ticket prices and where visitors can buy them.
Please note: Each platform has its own rules for displaying event information. Checking the publication box in Stager does not guarantee publication on the partner's platform. Stager facilitates the data transfer, but the partner decides what is shown.
Developer Guide: For Partner Channels
Unfold
Unfold
If you are a developer for a partner platform, you can implement our push feed to receive real-time event updates from Stager. Stager uses a webhook to push structured event data triggered by actions like creating or updating events.
Follow these five steps to connect to the push feed:
Step 1: Set up your webhook
Prepare a webhook endpoint (URL) that accepts HTTP POST requests. Ensure your server can handle relatively large payloads and increase your default maximum request size if necessary.
Step 2: Use a queue system
Stager sends messages in real-time, which means high volumes during peak ticket sales. We strongly recommend setting up an asynchronous queue system (like Redis, Amazon SQS, or RabbitMQ). This prevents your server from getting overwhelmed, avoids timeouts, and keeps your platform fast and responsive.
Step 3: Validate the messages
To guarantee messages are truly from Stager, they are signed using the HMAC-SHA256 hashing algorithm. Each message includes an X-Signature HTTP header. Generate your own signature using the same algorithm, your authentication key, and the full request body. Compare it to the signature we provide. If they match, continue processing. If not, reject the message with a 401 Unauthorized response. Implement this with a mock token first.
Step 4: Process the messages
Every message includes a messageType (e.g., UPDATE_EVENTS) and messageContent.
Check the message type to see if it is relevant to your system.
Deserialize the content based on our JSON schemas.
Always return the correct HTTP status code to confirm successful delivery.
Messages are pushed immediately in a simple 'fire and forget' mechanism. We do not retry failed deliveries. Instead, we send a nightly ORGANIZATION_SYNC at 2:00 AM CET with a full update of all upcoming events per organization to catch anything that might have gotten lost.
As a partner, you receive limited data fields. For a complete overview of the schemas and data fields, check our documentation:
Step 5: Test and go live
Once your endpoint is ready, send us your webhook URL and technical contact email.
We will grant you access to a dedicated organization in our staging environment for testing.
Your implementation will be added as a temporary partner channel, and you will receive your actual authentication token.
After successful testing, we will move your connection to production and stop sending staging messages.