Access a community of over 900,000 Shopify Merchants and Partners and engage in meaningful conversations with your peers.
Hi @agaonkar,
We don't use swagger to document our APIs, but our own in-house documentation which you can view here: https://help.shopify.com/en/api/reference.
Ryan | Shopify
- Was my reply helpful? Click Like to let me know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit the Shopify Help Center or the Shopify Blog
@Ryan Please consider using Swagger/OpenAPI. A REST client can easily be 80% of the development effort in an integration, so the ability to generate it automatically has enormous value. Developers increasingly view OpenAPI docs as a hard requirement for a minimum viable product.
Not only is it a gigantic waste of time to hand-write API documentation and consumers based on that documentation, but human error inevitably creeps in. I've just spent about six hours writing DTOs for Order and its related types. That should have been done in five seconds. I made some assumptions about scalar types and nullability, so I probably made some mistakes. There are mistakes in the documentation, too. For example, the field descriptions for line_items describe several fields that aren't in the example JSON. Which is correct, the JSON or the descriptions? I can't tell without testing. Auto-generating an OpenAPI spec would save you the trouble of maintaining the documentation.
Completely agree @TMIA. We personally faced this issue and figured out it is better to develop a tool. So we created a community free tool - API Shark - https://www.cloudvector.com/api-shark/. It allows to auto-generate OpenAPI Specs. Check it out.
Shopify OpenAPI Spec is up to date.
I tried it and it worked in Go. The page shows support for TypeScript and Python.
It even supports OpenAPI 3 and appears to be well maintained (as of Dec 2020).
I am going to update this. Please help if you can.
https://github.com/allengrant/shopify_openapi/issues/2#issuecomment-910221774