expand_less To

If getyou're thehere, WikiRateyou're dataprobably asaware JSONthat responsesan viaAPI [[https://app.swaggerhub.com/apis-docs/Decko/WikiRate/0.20.3|swaggerhub]]is youan Application can:Programming

setInterface, theor httpa accessway headerfor one software application to application/jsontalk into youranother. request
A appendlittle .jsoncontext
WikiRate's toAPI, thelike requestits urls,underlying ordata (3)structure, addis format=jsona tolittle unconventional. But if you understand why and how the querystructure params.is unusual, the API design will make sense. So let's start there.


First,
WikiRate is, as it's name implies, a wiki. It is built with Decko,an andopen-sourced iswiki thusplatform constructedcalled fromDecko, cards.which
Everythinguses inwiki-inspired Deckobuilding blocks called cards to create complex web systems. Pretty much everything you interact with on WikiRate is a card,card: includingCompany, images,Metric, accounts,Answer, searches,Project, fields,Data Set, Topic, etc. So–– everythey're requestall cards. forWhat's particularly unusual is that the substructures of these pages are cards, too. The logo of a webpagecompany, onthe WikiRate.orgformula orof viaa itsmetric, RESTthe APItopic istags foron a card.data set... it's cards all the way down.
The documentationembrace of this wiki card concept helps WikiRate live up to its values of transparency. Since everything is divideda intocard, genericand Deckoevery card documentationstored (underhas Decko)a revertible revision history, the WikiRate platform is deeply transparent, and moreit WikiRate-specificexposes cardtypesnot (underjust WikiRate).current data but also data histories to its API.
 
Read the latest [[https://wikirate.org/Use_the_API|WikiRate API User Guide]] to learn more about:

Formats and view
Sorting and filterin
Authentication and authorization
Python support tool



Contact the developer
Licence GPL-2.0
Find out more about Decko