Problem you are facing
We (State of the Map 2019) use our schedule renderer to build the programme for the website (table and detail pages) because we prefer a different layout than the one provided by Pretalx. The renderer uses various endpoints of the Pretalx API. Unfortunately, the API does not expose resources (the file uploads) which are useful to attach slides to the talks after the conference.
I would like to get URLs to download the resources using an API call.
Possible Solution
There are two possible solutions. I prefer the first option because it is simpler but it does not matter whether I add another API call in my toolchain or not.
- extend
/talks endpoint
- add new
/resources endpoint
@rixx What do you prefer?
Problem you are facing
We (State of the Map 2019) use our schedule renderer to build the programme for the website (table and detail pages) because we prefer a different layout than the one provided by Pretalx. The renderer uses various endpoints of the Pretalx API. Unfortunately, the API does not expose resources (the file uploads) which are useful to attach slides to the talks after the conference.
I would like to get URLs to download the resources using an API call.
Possible Solution
There are two possible solutions. I prefer the first option because it is simpler but it does not matter whether I add another API call in my toolchain or not.
/talksendpoint/resourcesendpoint@rixx What do you prefer?