Tim Lane, Software Developer at ACME Corporation
I do. I started using it to generate redoc documentation, and now I'm using it to generate SDKs.
I think I've also imported them into Postman to generate Postman collections. I've even begun hand editing them to improve on them. I wouldn't say I'm designed first as I depend on the Amazon API gateway to generate my open API for me, but I do spend a lot of time cleaning it up and improving the design of it.
So it looks better in documentation. It is handy for, for also sharing with people who use my APIs. Like I said, most of my API consumers are internal in my company, and I find it really useful for answering their questions. I just give them an open API most of the time and, and they go away.
Kin Lane, API Evangelist at API Evangelist LLC
I do. It's central to defining all my relationships with API technology. OpenAPI describes the surface area of my digital resources and capabilities. OpenAPI makes sure I have a plan and I'm in alignment with everyone I work with. I know most people see OpenAPI simply as a configuration for documentation, but it's really much more than that.
OpenAPI is one of the most important things to happen to the world of APIs and technology in years, and it isn't for the reason most technologists believe. OpenAPI helps us see APIs by documentation, SDKs, mock servers, and sandboxes, but also as YAML or a JSON contract, with the YAML really being a [00:06:00] critical olive branch that we're extending to business stakeholders.
I use OpenAPI as the technical contract for any API relationship I'm engaged in at the producer or at the consumer level.
Daniel Kocot, Head of API Consulting at codecentric AG
Yeah, we, we use with the, with the customers we do projects around. It's, it's really about open API when we have request reply APIs or interfaces that need to be available. It's always that we really think about in the context of open API. So we do a lot of stuff at the moment with, with SAP customers. So the developers are doing ABAP and very related stuff to SAP. So they don't really know the new stuff in software development. So it's really on them to learn how to write an open API specification and bring it into the run, which is sometimes hard because when I say that for me, it's a text document. So there is no real purpose. I need a lot of software running in parallel to get this. YAML file, which is still a text file, actually into action and see what is really happening there. And it is sometimes hard. And that's why I'm switching more in, into a direction, looking at These things from a more programmatically side. So using something like, which is coming up type spec from Microsoft to, to, to really bring more, because this is my, my, my background, the developer side into it and say, okay, I want to program. I want to use stuff I know from, from my days as a developer to, to reuse things and not hoping that a reference is working because I just set a reference tag. And when it's not working, I get in trouble because. I had to do things on my own or find stuff, or I'm totally heavily relying on having operation pipelines available and everything else in the context so that the things are. Running smoothly there.
