API feature request - Forums

Ultrawide	16:9	16:10	4:3	5:4
2560 × 1080	1280 × 720	1280 × 800	1280 × 960	1280 × 1024
3440 × 1440	1600 × 900	1600 × 1000	1600 × 1200	1600 × 1280
3840 × 1600	1920 × 1080	1920 × 1200	1920 × 1440	1920 × 1536
	2560 × 1440	2560 × 1600	2560 × 1920	2560 × 2048
	3840 × 2160	3840 × 2400	3840 × 2880	3840 × 3072

Wide	Ultrawide	Portrait	Square
All Wide	All Portrait
16 × 9	21 × 9	9 × 16	1 × 1
16 × 10	32 × 9	10 × 16	3 × 2
	48 × 9	9 × 18	4 × 3
			5 × 4

lucasshiva – 1 year ago27928

As I am currently developing a Python wrapper for the API, I've came across two things that, in my opinion, could be improved to make the development and the user's experience a bit nicer.

When fetching a collection, we can do so in two ways: public collections by passing an username; or all collections (public and private) by passing an API key. The problem lies in viewing the listing of a collection. To access the listing of a collection, both the username of the collection's owner and the ID of the collection is required. The problem is that, in my wrapper, if the user uses an API key to fetch collections, they would have to manually input the username to view the listing of collections they've fetched already. The easiest solution, in my opinion, would be to return the username of the collection's owner in the response, inside the collection object. That way, my collection models will have access to both the ID and the username. Another solution, albeit one that is harder to implement and more bug-prone, would be to simply remove the username from the URL, therefore allowing us to fetch collections by only supplying the collection's ID. However, since there should be reasons for the API to not have been designed this way, I think the first solution would be preferred.
When searching for wallpapers, it's quite a chore finding out exactly which search parameters were used. My biggest problem is that, if an API key is present and no additional parameters were supplied, then the only way for me to know exactly which parameters were used is to send another request to access the user's browsing settings. That is not ideal. The simplest solution would be to add these parameters to the response, more specifically inside Meta. Since I provide a way for the users to interact with the search parameters, this would help me and the users quite a lot, more so when interacting with said parameters to filter the listing to their liking.

In conclusion, returning the username and the search parameters in the response should not require any major restructuring of the API, yet these changes would bring quite a lot of benefits, I would say.