Priority Gateway

Procedures, reports, actions, smart filters — WebSDK only

Running procedures, reports, form actions, and smart filters is limited to the Priority WebSDK. Python, .NET, and mobile stacks can't reach those surfaces directly.

No MCP layer for AI tools

Connecting Lovable, Base44, or any LLM to Priority requires an MCP layer — and Priority doesn't ship one.

Read and write Priority from anything that speaks HTTPS

The customer's portal, mobile app, n8n flow, Python script, .NET service — all hit the same REST endpoint. Forms, procedures, reports, document activations, file uploads. WebSDK and OData both sit behind it, and the gateway picks between them per call. One URL covers it.

POST /api/v1/query/form
{ "form": "ORDERS",
  "filter": { "STATDES": "Open" } }

Ask questions that cross forms

Real SQL over Priority's own query engine: joins between tables, GROUP BY, aggregates — over plain HTTPS, with no driver installed on any machine. Read-only by construction: mutating verbs are rejected before the call leaves the gateway. Dates, shifted decimals, and Hebrew right-to-left text come back decoded, not as raw Priority integers.

POST /api/v1/sqli/query
SELECT ORDERS.ORDNAME, CUSTOMERS.CUSTDES
  FROM ORDERS, CUSTOMERS
 WHERE ORDERS.CUST = CUSTOMERS.CUST FORMAT;

Talk to Priority in plain language

Plug Claude.ai or Claude Desktop into the gateway and the customer's IT manager asks live questions of their Priority. Or build the customer's own AI assistant on top of the same MCP surface.

▸ You     Show open orders for ACME.

  Claude  priority_action(query, ORDERS,
            { CUSTNAME: "ACME" })

Sign in once — the app never holds a password

Server-side callers post credentials once to /auth/login and get back a bearer token with an idle window, an absolute expiry, and a per-user cap. Browser apps embed the hosted Connect popup instead: the user signs in to Priority inside it, and the app receives a revocable token. The password never reaches the calling page.

POST /api/v1/auth/login
→ { "token": "gws_…",
    "expiresAt": "2026-08-08T18:20:00Z" }

Ask business questions in plain language

The gateway builds a scoped schema context out of the customer's own Priority — the tables a question touches, the filters that give them meaning, the join paths between them — and hands it to the model before it writes a line of SQL. "How much did we sell last month" comes back right the first time. Off by default; needs the BI schema graph on the same host.

Serve concurrent callers

The Priority WebSDK allows one login per process, so simultaneous calls used to queue behind one another. Turn on the worker pool and the gateway spreads them across a pool of worker processes, each holding its own Priority login.

The gateway teaches its callers

/api/v1/sqli/syntax returns the SQLI dialect. /api/v1/guide answers which technology fits a given job. /api/v1/n8n-guide is the n8n node's own authoring spec. A model fetches what it needs mid-conversation instead of guessing.

Order intake automation

Orders from e-commerce, EDI, or email flow through n8n into Priority — validated, enriched, and booked.

Mobile stock count on the floor

Single-file PWA on warehouse phones, generated from one prompt. Subform writes, finalize activation, survives a closed tab.

Ask the ERP in plain English

"Which orders shipped late this month?" Claude reads live Priority data and answers — no custom report.

Customer self-service portals

Orders, invoices, and delivery status — built in Lovable or Base44, served by the gateway.

Nightly invoice exports

Python CLI on a cron pulls AINVOICES to CSV, drops it on S3, SFTP, or FileSmile. Generated from one sentence.

Document generation on demand

Account ledgers and statements triggered from external systems — full document-activation flow over HTTP.