Convert Galaxy Digital to be Open API Compliant

Posted about 4 years ago by Matthew Olson

Post a topic

Matthew Olson

Making the Galaxy Digital API Open API compliant means we could generate all interaction code in any language we want.

We had to spend several days implementing your API client in .NET, and are only part way through the implementation.

It would also provide self-documented API help pages using Swagger UI.

1 Votes

5 Comments

Eli Poulos posted over 3 years ago Admin

Hi Parris,

We don't currently have an endpoint for this, but I have made sure to add your support for this enhancement to our internal review list.

Thanks for writing in, and have a great day!

0 Votes

Parris Lucas posted over 3 years ago

Good morning,

What is the status of creating the OpenAPI compliant and the swagger self-documented?

Does an endpoint exist?

0 Votes

Eli Poulos posted almost 4 years ago Admin

Hi Matthew, thanks for reaching out!

I have added your request here to our enhancement review list, and will make sure to bring this to our product team when I am reviewing our list with them. I'm always for improving our API, and we appreciate feedback from people who are using it to build something robust.

There are a couple of requests here:

Make the API Open API compliant, and update the documentation to use swagger UI for self-documentation, each of which has been added as it's own request.

Have a great day!

0 Votes

Matthew Olson posted almost 4 years ago

Just so I'm clear. I'm talking about making the API Open API compliant: https://www.openapis.org/

https://swagger.io/specification/

1 Votes

Matthew Olson posted about 4 years ago

FYI, I have begun a .NET Client to make interaction with your API easier. Also does the auto-patching for the "extras" array versus not array bug.

https://www.nuget.org/packages/Galaxy.Digital.Api.Client/

1 Votes