Improvements for the API

5 posts • viewed 141 times

This message aims at: suggesting an idea to improve Numista

Status: Opened
Upvotes: 0
Downvotes: 0
As discussed in https://en.numista.com/forum/topic102760.html, here are some propositions to improve the API.
  1. Allow name of collection(s) and/or a "in-/exclude swap" parameter to be added to the /users/{user_id}/collected_coins call in order to decrease the number of coins returned

  2. Create way to authenticate without having to use oauth_authorize.php. For desktop applications, this won't work. I want to be able to authorize my application once in my profile. In the current situation, I need to make my collection public to be able to use the API and I would rather keep it private.

  3. In Coin -> Value -> Currency, please add the range of years that entire currency is/was active. At the moment, I only get the min_year and max_year for a specific coin, not for the currency.



  4. Add the date and time a coin was added to the collection in the API. That way, it's possible to sort the coins by date added and that helps with finding the coins that are not in my binders yet.

  5. Recently, Nagorno-Karabach was changed to Artsakh and Swaziland was changed to Eswatini. Please see if you can include the previous names of a country in the response. I did change Swaziland to Eswatini in my binders, but I didn't change Nagorno-Karabach to Artsakh.
They say "Pecunia non olet", but I know better...
Hello,

Point #2 is implemented. See the documentation: https://en.numista.com/api/doc/index.php
This works only to authenticate yourself, as I would like to avoid third-party application to store the Numista credentials of other Numista users. Desktop applications like OpenNumismat are able to use the current "authorization code" authentication.
Feel free to share feedback.

Point #1 is definitely interesting to implement in the future.

Point #3 would be nice to have, dates could be added both for the currency and for the ruling authorities.

I don't intend to implement points #4 and #5.
Hi Xavier,

Thanks for implementing point #2, I'll try that out soon. I understand you won't implement #5, but I don't understand why you don't want to implement #4. Can you explain your decision? I feel it would be a minor change, as you already use it in the Journal of my collection. Is there technical reason not to implement it, or is it more difficult than I think it would be?

Thanks!
They say "Pecunia non olet", but I know better...
Quote: "Xavier"​Point #2 is implemented. See the documentation: https://en.numista.com/api/doc/index.php
​This works only to authenticate yourself, as I would like to avoid third-party application to store the Numista credentials of other Numista users. Desktop applications like OpenNumismat are able to use the current "authorization code" authentication.
​Feel free to share feedback.
Hi Xavier, when I try to authenticate, I get the following error: The remote server returned an error: (400) Missing mandatory parameter 'code'. According to the documentation, it should not be mandatory when using the grant_type client_credentials. Would you please look into this?

Thanks!

They say "Pecunia non olet", but I know better...
Hello,
The point #1 is implemented in the API version 3, with the new parameter "collection" of /users/{user_id}/collected_items
Note that version 3 requires some changes in comparison to the version 2 (https://en.numista.com/forum/topic111088.html#p970338).

Used time zone is UTC+2:00.
Current time is 09:54 pm.