[API] Endpoints for CRUD of collections [Risolto]

Hello! I'm new to Numista, but not to numismatics. I love the community and the idea of the site, and I'm excited to catalog and add my collection.

Disclaimer: I have searched the forums for discussion on this and couldn't find an answer, so I apologize if this is redundant.

I have large enough collection that I keep in a google sheet (wait, let me finish... I already read about why no csv bulk upload), and I saw that while there is an API for most of the READ operations I could need, there don't appear to be any methods for modifying an individual's collection.

I am assuming that while these methods and endpoints are in planning, they have not been made available yet. I see the OAuth endpoints, so its clear that something like this is being considered.

I feel like the use cases are fairly self explanatory, and I just wanted to open a dialog to see what the current intentions are, possible timelines, etc. I see the site is primarily written in PHP using a handful of js scripts to handle data prep client side.

Why am I asking?

Well, I noticed a lack of an SDK to assist in abstracted development, so I took the liberty of beginning one and populating a python based SDK. https://github.com/namachieli/numista-api-sdk (still a wip, but solidly in Beta)

While I'm sure I could start trying to reverse engineer something, I wanted to start here and at the very least ask permission first if there isn't something for CRUD endpoints in the works.

Glad to be here and glad to find ways to contribute!

Hello,

I would like to add new features to the API. The most urgent for me are extending to banknotes and exonumia, and allowing modifying catalogue data. Modifying the collection (add, modify, delete) could come next, probably within the next 3-6 months.

It could open the door to sharing collection data within different software, websites or personal tools, or bulk changes of collection for example, which would be great, even if it will still be somehow limited by the need to use Numista IDs to identify the coins.

Extending basic capabilities to other aspects of collecting is great and I'm sure lots of people are eagerly looking forward to that, good call!

I want to offer any assistance I can. I do Infrastructure Automation/IT/Development for a living, so I know my way around pretty well. I am primarily python/bash, I have dabbled in golang, JS, and in a former life, PHP... so I can probably contribute at low levels in those languages.

If there is a way that I could deliver on extending your API following the work you have done already, I would be willing. I do understand and appreciate the desire to keep it locked down and in house though, so no hard feelings if you wish to decline said offer.

Perhaps an unpublished/undocumented/unsupported endpoint that I wrap my SDK around in the interim could suffice? Open to any thoughts/willing to help in anyway.

Thank you for building and maintaining such a great community and resource. I wish I knew about Numista when I was actively collecting in 2010-2014.

Hello,
It is now possible to create, view, edit and delete items in a collection.
See the updated API documentation (version 3.1): https://en.numista.com/api/doc/index.php

Wow, fast turn around! Thank you :D

I'll take a look at your documentation and get my stuff updated and test.

If I find issues/bugs, would you like a new thread, or post to this one?

I'll assume new thread for each instance?

Thanks again for the amazingly fast turn around, this is fantastic!

Thanks! A new thread for each bug would be better for me (I hope there are not too many ).