More API Documentation
Google API Group seems inactive. I'm a web developer and am looking to utilize the api to display tournament info on my website.
Although I have a good working knowledge of various apis it would help tremendously if some basic code snippets were given to demonstrate some of the api functionality.
A html example of display tournament bracket would be a great start.
Tommy Hash commented
I would like to add this tool https://apix-drive.com/en/integracia-ip-telefoniia that can help you automate your workflows. You can streamline everything you need to get done for your business in one place and automate processes that would take you hours to get done manually.
max marrie commented
They need to public challonge API for their visitors. I also need their API to embed it on my website that is related to Garden screens https://metalgardenscreen.co.uk/.
The current documentation (and the api itself) is kind of a mess to be honest. What would be needed to be able to easily work with the api is at least a description of every field that any given get request returns together with its type and whether it is nullable. For example: what the heck are the "ham" and "spam" fields of a tournament supposed to mean?
Solid documentation for just about everything on the back end. I'm new to web development and would like to integrate this and twilio's APIs to create something that can help running tournaments easier. I would like to see something for the front end if possible.
Sorry for missing your earlier message. The Google API Group was just introduced recently and is for change and availability notices only.
What language are you writing in? The PHP and Ruby libraries have some good snippets for getting started; not sure about the Python one. Whatever the language, there's likely a solid REST library that will get you started.
As far as _rendering_ the brackets goes, we don't have any samples for that currently. However, we're completely redoing our bracket back-end and renderings this year, and API users will be given more guidance for creating their own.
Mark D. Hulett commented
interesting. no support ....hmm.