Public GraphQL API

Provide GraphQL access to Catalogs, Orders, Payments, and other square objects. Through this, developers can quickly integrate Square into their microservice architecture. This should include the ability to query, mutate (update), and subscribe to changes on the Square platform.

Why should people use this category? What is it for?

As a tech startup, we want to quickly build a custom online shopping experience using the square platform. However, integrating with Square’s REST API requires a lot more code compared to newer eCommerce platforms that use GraphQL.

For example, we’ve built a microservices architecture using Hasura. Hasura allows us to “stitch” together multiple external GraphQL services and present those as a unified API to our App.

How exactly is this different than the other categories we already have?
Square’s REST API is powerful, but working with it requires custom code. GraphQL provides the same level of functionality and is standards-based, reducing the amount of required code.

What should topics in this category generally contain?
Backend-as-a-Service (BaaS)

Do we need this category? Can we merge with another category, or subcategory?
Yes, this is needed for modern development.

1 Like

:wave: We’re constantly working to improve our features based on feedback like this, so I’ll be sure to share your request to the API product team. :slightly_smiling_face:

Hi @simplyscapes

We recently released a public alpha of our GraphQL API

Please try it out and send any feedback to [email protected]