WordPress Help

We call the following endpoints from Wikimedia Commons: https://commons.wikimedia.org/w/api.php?action=query&generator=allimages&prop=imageinfo&gailimit=40&gaisort=timestamp&gaistart=YYYY-MM-DDT00:00:00Z&gaiend=YYYY-MM-DDT00:00:00Z&iiprop=url|user|dimensions|extmetadata&iiurlwidth=300&format=json https://commons.wikimedia.org/w/api.php?action=query&generator=allimages&prop=imageinfo&gailimit=40&gaisort=timestamp&gaistart=YYYY-MM-DDT00:00:00Z&gaiend=YYYY-MM-DDT00:00:00Z&iiprop=url|user|dimensions|extmetadata&iiurlwidth=300&format=json&gaicontinue=SOME_PICTURE.jpg For both of these, we replace YYYY-MM-DD with dates (we only pull data for images uploaded/updated between these dates). We use the second query if there are more than 40 images between the specified dates, giving a continue location as the next picture (represented by SOME_PICTURE.jpg). These requests each…

Read guide

The Thingiverse API is queried in a number of different ways. First, to get a list of ‘things’ to retrieve, and then in a series of steps for each ‘thing’ in the list. Initial API Query The initial query sends a GET of the form https://api.thingiverse.com/newest?access_token=REDACTED&per_page=30&page=1 This returns the following JSON: [ { “id”: 4002927,…

Read guide

We call the following endpoint from rawpixel.com: https://api.rawpixel.com/api/v1/search?freecc0=1&html=0&page=X Here X is a page offset. Such a request returns a JSON of the following form: { “html”: “”, “spellcheck”: [], “total”: 20586, “uid”: 0, “context”: { “context”: “”, “masterContext”: “” }, “results”: [ { “sort”: “[739,154,1,1571387376]”, “nid”: 1232608, “id”: 1232608, “view_mode”: “photo_grid”, “attributes”: “”, “keywords_raw”: “antique, art, arts, artwork,…

Read guide

We call the Phylopic API in two different ways: http://phylopic.org/api/a/image/list/modified/YYYY-MM-DD http://phylopic.org/api/a/image/ITEM_UUID?options=credit+licenseURL+pngFiles+submitted+submitter+taxa+canonicalName+string+firstName+lastName We extract a list of UUIDs from the response to the first request, which we then use to construct subsequent requests (of the form shown second above filling in an extracted UUID for ITEM_UUID). The response to a UUID-specified request is a JSON with the…

Read guide

We call the objects endpoint from the Met Museum’s API in two ways: https://collectionapi.metmuseum.org/public/collection/v1/objects/?metadataDate=YYYY-MM-DD https://collectionapi.metmuseum.org/public/collection/v1/objects/XXXXX The only information we use from the first type of call is a list of object IDs, which we use in the second call in place of XXXXX. The second type of call returns a JSON of the following form: { “objectID”: 786829,…

Read guide

Flickr API We run an hourly job to pull the last hour’s uploads from Flickr. You can find the documentation for Flickr API here. We currently use the flickr.photos.search method to query the API. Here is an example showing the type of query string we use: https://api.flickr.com/services/rest/?method=flickr.photos.search&api_key=REDACTED&min_upload_date=2019-11-22%2017:10:00&max_upload_date=2019-11-22%2017:15:00&license=1&media=photos&content_type=1&extras=description,license,date_upload,date_taken,owner_name,tags,o_dims,url_t,url_s,url_m,url_l&per_page=500&format=json&nojsoncallback=1&page=1 Such a call to the flickr.photos.search method produces a result of…

Read guide

Cleveland Museum API We call the following endpoint from the Cleveland Museum of Art: http://openaccess-api.clevelandart.org/api/artworks/?cc0=1&limit=X&skip=Y Here, X and Y are replaced with offset information (e.g., we request only 1000 pieces at a time, and move the offset by 1000 for each request). Such a request returns a rather large JSON of the following form: { “info”: { “total”: 34911,…

Read guide