It is possible to publish event information through different channels. An obvious channel is your own website. But you can also share your events with a local online newspaper or national marketing channels. This all goes through a feed, or a publication channel. In Event - Publicity you indicate which information may be published where.
There are two publishing options:
Publication channels. Custom publishing channels controlled by you through Settings.
Partner channels. Stager offers a number of options for publishing to regular (Netherlands-based) third parties, such as Podiuminfo.nl. Stager manages these links.
Step 1. Create an access token
Decide for yourself which publication channels you want to create. We've already created one for you, called 'Feed'. The name can be changed to, for example, 'Website', which is nice and clear if you want to link directly to the CMS of your own website. New channels can also be created.
Ask your web developer to make the actual link, at the bottom of the page you will find technical documentation. You give the developer an access token. These are secret keys that are required to request the feed. You create these tokens yourself in Settings - Integrations - Publication Channels.
Indicate which permissions a publication channel receives. There are two options:
Limited: All event information entered in the Publicity tab, plus basic ticketing info, such as which tickets are for sale and how much the tickets cost.
Extended: All event information as entered in Publicity plus all ticketing information, including the sales start and end time, and which link members should use.
If you no longer want to use an access token, set it to disabled and create a new access token.
Step 2. Publish information
At Event - Publicity - Publication channels you can see the access tokens you created. Select your checkbox and the event information including (limited) ticket information will be published in the chosen feed.
Show performance dates and times and tickets for recurring events on your site
All events in a series have the same ID in the feed, which identifies and links all events in that series. So it is possible, for example, to have a page on your website about a certain film screening, and your web developer can list on that page all the dates, times and ticket links of the screenings of that film screening.
That way you don't have to load separate events into your calendar for every film screening, exhibition day or dance, or theatre performance. Instead you have a clear, informative page and the visitor can choose which particular show they want to visit. The key to building this is with the Series ID in the feed.
In the feed, the Series ID is easy to extract as:
"seriesId":
Publish information about multi-day events
If events are linked together by means of a multi access event (recognizable by an umbrella icon), you request information from two endpoints:
/eventgroup/{ID}
Eventgroup is the old name of a multi acces event and is currently still called that in the feed. Through this endpoint you will also find EventsIDs when you request information about a multi-day event. These are the IDs of the individual events that are linked to the multi-day event. This way you can link the multi-day event with the individual events./events/{ID}
When you request event information via this endpoint and the event is part of a multi access event, you will find an ID at the NonPrimaryEventgroupID in the feed. This is the ID of the multi-day event. This way you can link the separate events to the multi-day event.
Technical explanation for your website developer
We set up a Swagger environment in which you can play around with the output of the feed. Go to https://feeds.stager.nl and use the token from your Stager account to log in. There are several endpoints you can use.
Request made to the feed will be send from the backend of your website. The request can not be send directly form the browser of your website visitor, because 1) the token will be shared with the browser of your website visitor and 2) because browsers don't allow (CORS) access to a third party API.
Authentication
Each HTTP request should contain an access key to the feed in the Authorization header, formatted like:
Authorization: Bearer {token}
For example:
Authorization: Bearer bbdeebf34fad12412b0a194cb03cc
Do not delete the word 'Bearer'. This is part of the authorization token.
In case of a valid key, the feed should return its content with a 200 Ok. Missing authentication should result in a HTTP 401 Unauthorized. This happens for example when you delete the word 'Bearer' or use a wrong token.
The feed renews every minute. So if changes have been made in the Stager backstage, this can take up to a minute before it's visible in Swagger.
Versioning
A versioned request should contain a version identifier in the HTTP Accept header, formatted like:
Accept: application/json;version=1
In case of a missing or invalid version, the feed always returns the most recent version. We will communicate by e-mail to the account holder when a new version is released and when the old version will be deprecated. Older versions will always be supported for at least 6 months after a new version is released.
Pagination
Pagination support should be configurable to the number of entities per page per endpoint (page size). The page number should be a param in the request.
Modified since
Every change in Main, Publicity and Tickets tab per event, triggers a new time stamp for ModifiedSince. If you only want to request the feed when changes have been made, use the ModifiedSince stamp. Whenever something has been changed in the event on one of the above tabs, your website will be updated.