Settings

Manage API Tokens, Webhooks, Connectors and Analytics

Integrations decide what can touch shop data from outside: tokens say who, webhooks say where signals go, analytics says what page visits are measured.

Menu path
Manage -> Integrations
Verified from
Posnic demo and current POS source reviewed on 2026-09-08
Technical source evidence

frontend/modules/settings_write.html Integrations tabs, frontend/static/script/js/modules/js/settings.js PosnicPro.integrations, frontend/static/script/js/modules/js/settings.js analytics_save handler

API TokensTokens are standing credentials and the plain secret is shown only once.
WebhooksWebhooks send change signals for selected entities and keep delivery history.
AnalyticsAnalytics uses the shop owner's own Google Analytics measurement id.

Integration Safety Rule

An integration can read, write or delete shop data if its token allows it. Create one token per integration, grant only the scopes it needs and revoke tokens that are no longer used.

  • Never reuse one all-powerful token for many tools.
  • The plain token is shown once; store it immediately in the external system.
  • Token lists show hints and last used dates, not the secret.
  • Use revoke when a vendor, script or employee no longer needs access.
  • Check integration access after staff role or vendor changes.

Create an API Token

  1. Open Manage -> Integrations.
  2. Stay on API Tokens.
  3. Click New Token.
  4. Enter a clear name such as Accounting sync or Ecommerce stock sync.
  5. Grant only the required read, write or delete scopes.
  6. Create the token.
  7. Copy the token immediately from the reveal box.
  8. Paste it into the external system and test the smallest safe action.
  9. Return to the token list later and confirm Last used changes.

Register a Webhook

A webhook is a change signal, not a full data dump. The receiver verifies the signing secret and then fetches details using its own token.

  1. Open Webhooks.
  2. Click New Webhook.
  3. Enter an HTTPS endpoint URL.
  4. Select only the entities the receiver needs.
  5. Register the webhook.
  6. Copy the signing secret immediately; it is shown once.
  7. Trigger a safe change such as a test customer update.
  8. Review Recent deliveries for status and attempts.

Webhook Entities

The source exposes webhook entities for sales, items, receivings, customers, suppliers, categories, registers, expenses, shifts and easytables. Do not select all entities unless the receiver is designed to handle all of them.

Enable Google Analytics

  1. Open Analytics.
  2. Switch on Enable Google Analytics.
  3. Paste the Measurement ID from Google Analytics Data streams.
  4. Use a value like G-XXXXXXXXXX from the shop owner's own Google account.
  5. Save.
  6. Reload the relevant shop page and verify visits in Google Analytics.

Desktop Connectors

The Connectors tab is shown only when the desktop till bridge is available. Connectors run beside the till, not inside the web dashboard. Enabling one mints a scoped token for that connector and the desktop supervises whether it is running, off or parked after failures.

Related Manual Pages

Settings Feature Switches Feature switches hide or show modules without deleting existing data. They are the operator's control panel for workflows. Settings Messaging Messaging powers digital receipts, credit reminders and campaigns. Provider setup must be tested before cashiers rely on it. Settings Kiosk and Sales Channels Kiosk and sales channels let customers place or review orders away from the cashier screen. Operators configure account, images, payment and print settings, then review channel orders in Kiosk Reports. Reports Reports and Export Reports are the owner's review surface for sales, purchases, stock, customers, payments, tax and close evidence.