{% extends "orga/schedule/base.html" %} {% load compress %} {% load i18n %} {% load static %} {% block extra_title %}{% translate "Export schedule data" %} :: {% endblock extra_title %} {% block schedule_content %}
{% blocktranslate trimmed %} The event schedule can be exported to a static HTML dump, so you can upload it to a normal file-serving web server like nginx. {% endblocktranslate %} {% if request.export_html_on_release %} {% blocktranslate trimmed %} This is done automatically on schedule release, but you can also trigger that action here. {% endblocktranslate %} {% endif %}
{% translate "You can also use the API to export or use data." %}
{% blocktranslate trimmed %} Some of the general exports are only accessible for organisers, or include more information when accessed with your organiser account. If you want to access the organiser version in automatic integrations, you’ll have to provide your authentication token just like in the API, like this: {% endblocktranslate %}
curl -H "Authorization: Token {{ request.user.auth_token.key }}" {{ request.event.urls.frab_xml.full }} curl -H "Authorization: Token {{ request.user.auth_token.key }}" {{ request.event.api_urls.submissions.full }}