Skip to content

Latest commit

 

History

History
87 lines (70 loc) · 4.72 KB

README.md

File metadata and controls

87 lines (70 loc) · 4.72 KB
Raw

API & Challenges available at food{hacks}

For more information on the event please check out the event description at our event page

We use Devposts as our hackathon management system! Please also register there: food{hacks} Devposts page

APIs & Datasets with a related challenges

We will announce challenges soon. There will be a dedicated prize for this challenges, dedicated for the best solution of the problem described in the challenge.

APIs provided by our API Partners

For this APIs there is no special API prizes.

Challenge & API Workshops at food{hacks}

This is prelimenary workshop schedule.The workshop will be hold in the workshop room at the Rainmaking Loft. The times and order are subject to change.

Time Workshop Topic Presenter
11:00 HelloFresh API Challenge Workshop Pedro Carvalho
11:30 Metro Challenge Workshop Vahid Gharavi
12:00 Lidl Challenge Workshop Dr. Philipp Götting
12:30 Minodes Challenge Workshop Alexander Mueller
13:00 Imagga API Workshop Chris Georgiev
13:30 Spoonacular API Workshop David Urbansky
14:00 P2PKit API Workshop Samuel Schläpfer
14:00 Discounto API Workshop Jan Dreger (Alex Mueller)

Information for API and Challenges Sponsors and Partners

A description should include the following:

Format of an API a description

  1. General API description
  • What is the content of data that can be retrieved
  • Give an introduction to the general datamodel
  1. Goal of the challenge (if you are a challenge sponsor)
  • This should include the problem that you want to tackle.
  • Do you want them to use your data in a specific way or should the challenge be more open.
  1. Authentification
  • Describe the way users should authentificate against the api, but do not provide credentials here if you don't want to let them be public.
  • If your API is closed bring the api keys or logins to the event
  1. API Route description
  • Describe all routes of your api
  • We suggest that you provide a postman collection of all api endpoints with example parameters
  1. Coding examples
  • One might include python, javascript and java as example languages

Format for the dataset description

  1. General Dataset description
  • What is the content of data that can be retrieved
  • Give an introduction to the general datamodel
  1. Goal of the challenge (if you are a challenge sponsor)
  • This should include the problem that you want to tackle.
  • Do you want them to use your data in a specific way or should the challenge be more open.
  1. Detailed dataset description
  • If you provide a csv or json, please describe what each fields means and what datatype it has
  • When you plan to provide a database dump, describe possibilities to play it back in

Timeline

You want feedback on your challenge/API from us:

    1. March 2016: Hand in challenge/api description including access to the dataset and or the API (or at least a description)
    1. March 2016: Announce the challenge/api price to Hackerstolz Team
    1. March 2016: Hand in a first version of workshop presentation
    1. March 2016: Hand your job postings
    1. March 2016: Tell organisation team who will act as corporate contact at the event and hand in the final presentation
        1. April: Enjoy the Hackathon

You don´t want feedback:

    1. March 2016: Announce challenge/api price to Hackerstolz Team
    1. March 2016: Hand in challenge/api description including access to dataset and or API (or at least a description)
    1. March 2016: Hand your job postings
    1. March 2016: Hand workshop presentations
    1. March 2016: Tell organisation team who will act as corporate contact at the event and hand in the final presentation
        1. April: Enjoy the Hackathon