Start

APRO is the modular point-of-sale platform for restaurants, hotels, food trucks and system gastronomy — built to connect. Hotel software, accounting, payments, delivery services, reservation systems, access control, digital signage: APRO plugs into your existing stack for end-to-end processes and maximum automation.

This site is the developer documentation for teams building on that surface: partners wiring up reservation or inventory systems, delivery marketplaces routing orders into the POS, BI tools reading the ledger, or in-house teams automating reports.

What you will find here

• REST APIs. Stable, JSON-over-HTTPS endpoints for the domains below. Every endpoint is authenticated with a single API key — no SDK required, no OAuth dance to orchestrate.
• SQL views. Read-only views for direct database access, useful for BI pipelines and data warehouses.
• Payload samples. Every example on this site is backed by a standalone JSON file under /samples/ that you can download and replay.
• Full API reference. The machine-readable contract is published at api-docs.apro.at.

Pick your starting point

Status and versioning

Endpoints under /api/v1/… are considered stable. Breaking changes are announced in the release notes on apro.at. New optional fields and non-breaking response additions can land at any time — parsers should tolerate unknown keys.

Support

• Commercial & onboarding: apro.at/support
• Integration questions: reach out through your APRO account manager.

All APRO REST endpoints use a single API key, passed in the x-api-key request header. There is no OAuth flow and no token refresh — keys are long-lived and scoped to either a tenant or a single location.

Header

POST /api/v1/external/order HTTP/1.1
Host: my.apro.at
x-api-key: sk_live_pLpXZq8S…
content-type: application/json

Key scope

Every APRO REST key is scoped to a single location. A request succeeds only if the location derived from the endpoint matches the location bound to the key.

A location-scoped key fails closed if reused against another location and is safe to hand to a partner or a single deployment.

Obtaining a key

Keys are issued by the APRO account team. Contact your account manager or apro.at/support to request one. Rotation is supported; the retired key is kept valid for a grace period so you can roll over without downtime.

Storing keys

• Never commit a key to source control.
• Store keys in a secret manager (Azure Key Vault, 1Password, HashiCorp Vault, GitHub Actions / Azure DevOps secrets).
• Inject them at runtime as environment variables (APRO_API_KEY).

Error responses