fusionauth-openapi VS api

I talked to a startup ( https://stainlessapi.com/ ) about a service they provide where they take an OpenAPI spec and build good SDKs on top of it. This included making sure they are idiomatic, included examples, handled exceptions if needed, and some other goodness. I passed for now because they don't have the language support we need and I am not sure if we need their level of sophistication, but others may benefit from talking to them. (I think the founder helped build Stripe's API docs, IIRC.)

As we head down our OpenAPI path (https://github.com/fusionauth/fusionauth-openapi has only been built for the last 9 months), I'm very interested in stories like yours. We're very interested in quality SDKs that are easy to update. But since we control the OpenAPI spec for the product, we might have an easier time than you in some ways.

Thanks for sharing!

As someone who just released an OpenAPI spec for our API and struggled with building client libraries to test that the spec was correctly generated, I'd pay for this, especially if it integrated with the rubygems/packagists/nugets of the world.

Let me know if you want an alpha or beta tester. Our OpenAPI spec is here: https://github.com/fusionauth/fusionauth-openapi and my contact info is in my profile.

I don't use pocketsmith, but Up has a pretty good api, so you could probably hack together something to sync data in.

What you probably want is an Up Bank API interface for a spreadsheet if you want to get real deep with your data. https://github.com/up-banking/api/blob/master/community/EXAMPLES.md

See: https://developer.up.com.au/

(Also to note the one exception to this is UpBank which provides customers with read-only API that an individual can use without ACCC accreditation: https://developer.up.com.au/)

Up has an API: https://github.com/up-banking/api