PMS / POS (design-partner choice)

Quick-start for the PMS / POS (design-partner choice) connector.

In this demo build the PMS / POS (design-partner choice) connector uses a recorded-fixture transport: payloads have the platform's public API shape, but nothing leaves the server and no credential exists.

At a glance

Connector id

pms_pos

Kinds

booking

Capabilities

booking, webhooks

Authentication

oauth2

Rate limits

Per vendor

Mechanism

BookingSystemConnector (candidates: Opera Cloud/Mews, SevenRooms/Lightspeed)

Quick-start

1. Choose the connector and authorise AGORA on the platform's consent screen. AGORA stores only a credential reference in the vault.
2. Run the first import. Records are staged first; review the validation summary and any conflicts with your own overrides.
3. Keep it current: re-import on a schedule or when the source changes.
4. Publish. Every projection is validated before it goes live.

curl -s https://app.fondaq.ai/v1/merchants/$MID/connections -H "Authorization: Bearer $AGORA_API_KEY" \
  -H "Agora-Version: 2026-10-25" -H "Idempotency-Key: connect-pms_pos-001" -H 'Content-Type: application/json' \
  -d '{ "method": "pms_pos" }'

Notes

Interface implemented against a fixture in the demo

Source: connector registry (platform/connectors listConnectors())