Difference between revisions of "Yugipedia:API"

From Yugipedia
Jump to: navigation, search
(create)
(No difference)

Revision as of 00:43, 11 November 2019

Yugipedia uses MediaWiki, which offers a powerful API for automated access to our data. This API can be accessed via https://yugipedia.com/api.php, and extensive documentation can be found on MediaWiki.org. When using our API, please observe some points of etiquette, to avoid endangering the site; offending agents may be blocked without warning.

User agent

All automated requests to the API should set a descriptive User-Agent header, including the name of the service and contact information. Requesters who do not do so may be blocked at any time without warning.

Request limit

Please limit requests to no more than one per second. The content of multiple pages can be bundled together into a single request with a pipe (|), e.g. titles=PageA|PageB|PageC.

Caching

Results of requests should be cached wherever possible, and the cache should be used instead of rerequesting the same resources. A good period for caching is 30 days.

Updating data

Certain tasks done via the API, such as automatically building and maintaining a card database, may require information to be updated more often than every 30 days. In these cases, instead of simply rerequesting the entire data set, you should only rerequest those resources that have changed. This can be determined by watching our recent changes feed using list=recentchanges.

Other points

In addition to these, you should assume that the points on the API etiquette page on MediaWiki.org also apply to use of the Yugipedia API; that page also has some advice on how to reduce the potential impact of requests. If you have questions or need help, you can join our Discord server.

What do I do if I've been blocked?

If you've been blocked because of misuse of our API, the first step is to join our Discord server and explain what you were doing with the API. It is very likely that your requests can be changed to meet our usage guidelines here, and we'd be happy to work with anyone who needs help on the matter.