# OpenQloud

> OpenQloud is the GDS (Global Distribution System) for the restaurant industry: an open operational standard plus headless infrastructure. POS systems, marketplaces, delivery companies and restaurant software share one data model, one identity per entity (OQID) and role-based APIs, so each system connects once and interoperates with all the others.

Key facts:

- OpenQloud is not a restaurant app and not a middleware. It has no restaurant applications or operational screens; it provides APIs, events, a common model and a low-level infrastructure console.
- Software integration, restaurant authorization and payment responsibility are independent.
- A middleware is another integrated software type, like a POS, marketplace or delivery product. It is not an OpenQloud distributor or necessarily the payer.
- An enabled customer account onboards restaurants and assumes their usage. Any authorized company can hold that account, independently of the APIs its software uses. Restaurant data access and event subscriptions require separate permissions.
- The **OpenQloud Manifest** is the portable operating declaration of a restaurant: catalog, availability, sales rules, payments, fulfillment, channel permissions and order handoff.
- An **OQID** (OpenQloud ID) is the shared identifier of a restaurant, brand, location, product, order or user, e.g. `rst_01kmj9fw7q`. Each system keeps its own ids and stores the OQID next to them.
- OpenQloud is operated by SINQRO TECHNOLOGIES, S.L. (Viladecans, Barcelona, Spain). Contact: info@openqloud.com.
- The site is available in Spanish, English, Catalan, Portuguese, French, Italian, German, Arabic and Chinese.

## Pages

- [Home](https://www.openqloud.com/en/): what OpenQloud is, why a GDS, building blocks, how it works, FAQ
- [Integrate your software](https://www.openqloud.com/en/integrate-with-openqloud/): integration variants (direct API or via your API) and role directory
- [Middlewares](https://www.openqloud.com/en/middlewares/): middleware software integration, independently of customer billing and provisioning
- [Integrations directory](https://www.openqloud.com/en/integrations/): products already connected to the ecosystem
- [OQID](https://www.openqloud.com/en/oqid/): how OpenQloud identifiers work
- [Manifesto](https://www.openqloud.com/en/manifesto/): principles behind OpenQloud
- [Contact](https://www.openqloud.com/en/contact/)

## Public APIs (OpenAPI)

- [POS App API](https://www.openqloud.com/en/docs/pos-app-api/): for POS systems. Spec: https://www.openqloud.com/openapi/pos-app-api.json
- [Market Platform API](https://www.openqloud.com/en/docs/market-platform-api/): for marketplaces and ordering channels. Spec: https://www.openqloud.com/openapi/market-platform-api.json
- [Delivery Platform API](https://www.openqloud.com/en/docs/delivery-platform-api/): for delivery companies. Spec: https://www.openqloud.com/openapi/delivery-platform-api.json
- [Data Reporting API](https://www.openqloud.com/en/docs/data-reporting-api/): read-only reporting and BI data. Spec: https://www.openqloud.com/openapi/data-reporting-api.json
- [Public API](https://www.openqloud.com/en/docs/public-api/): discovery and reference data. Spec: https://cdn.openqloud.com/openapi/openqloud-public-api.json
- [Middleware API](https://www.openqloud.com/en/docs/middleware-api/): the current authenticated integration contract. Customer, management and provisioning separation is being developed without breaking existing routes. Public documentation does not imply unrestricted access or a deployed backend. Spec: https://cdn.openqloud.com/openapi/openqloud-middleware-api.json

## Optional

- [Full text for LLMs](https://www.openqloud.com/llms-full.txt)
- [Sitemap](https://www.openqloud.com/sitemap.xml)