[API][v3] Some inconsistencies in schema

2 posts • viewed 32 times

This message aims at: reporting a bug

Status: Solved
Upvotes: 0
Downvotes: 0
I'm in the middle of the process of migrating my unofficial JavaScript SDK to API v3.

Looking at the "POST /types" parameter, I see that the "obverse", "reverse", "edge" and "watermark" fields has the "coin_side_update" schema, while the new "type_side_update" seems unused.

Is this a problem with documentation, or the endpoints haven't still upgraded to the new schema? I expected that the old "POST /coins" implemented "coin_side_update", while the new "POST /types" implements "type_side_update".

By the way, Numista seems to use Swagger to document its API. Do you intend to expose the Swagger YAML in the future? I'd be interested in experimenting with Swagger-based code and type generations, as keeping track of the changes manually can be bug prone.
Hello,

Thanks for reporting this. I fixed the error in the documentation (you may need to refresh your browser cache).

The Swagger YAML file is available at https://api.numista.com/api/doc/swagger.yaml
Status changed to Solved (Xavier, 30-Mar-2022, 05:08 pm)

Used time zone is UTC+2:00.
Current time is 08:26 pm.