What does the Priority REST API give you?
Priority's REST API is built on OData, a data access protocol over HTTP. Every form in the system is exposed as a resource you can read, filter, create in and update, subforms included. It is the common way to work with records: customers, orders, invoices, items.
What you need: an API user in Priority with the right permissions, and the server's address. When Priority is installed on your premises behind a firewall, access from the connecting addresses has to be allowed too.
When do you need the Web SDK?
Some work in Priority is not a form record but an action: running a procedure step by step, producing a report, printing a document such as an invoice. Priority's Web SDK does that. It opens forms and subforms, runs actions, attaches files and runs procedures and reports. It is meant for apps that run in the browser.
And when Priority has to tell another system?
The API and the SDK answer when called. When Priority has to start the conversation, for example to announce that an order moved to "shipped", you use a webhook: it is defined on a BPM status or a business rule, and it sends the record's details to an outside address, such as a Make scenario. That needs Priority's Webhooks module.
How do you integrate without code?
LeonAI Priority adds modules to Make.com that read, create, update and delete in Priority, subforms up to three levels included, plus running procedures and producing printed documents through EProg. Any system with a Make app connects to Priority the same way: stores, CRMs, forms, email and spreadsheets.
Your Priority credentials are kept in Make's connection vault. Our relay leaves from fixed IP addresses you can add to the ERP firewall's allow-list, and authentication headers and bodies are scrubbed from the logs.
Which fits what?
| REST API | Web SDK | LeonAI Priority in Make | |
|---|---|---|---|
| What it does | Reads and writes records | Procedures, reports, documents | Both, as ready modules |
| Code | Yes | Yes | No |
| Who maintains it | Your team | Your team | We maintain the connector, you own the scenario |
| Fits | A system you develop yourselves | An action with no record to match | Connecting Priority to systems you already have |
How it works
- REST APIReads and writes records, with code
- Web SDKProcedures, reports and documents, with code
- Priority ERPCustomers, orders, invoices, items
And when what connects is an AI?
When what connects to Priority is an AI assistant or an agent, the connection goes through an MCP server. MCP for Priority gives the AI tools for reading, analytics and writing with approval, and n8n has a dedicated endpoint in it, so the same tools are available to an automation scenario. An automation that runs with no person in front of it, such as n8n, skips the approval step only with an API key that was given write access and explicit permission to skip it, and that is off by default.
Common questions
- What is a Priority ERP integration?
- A connection between Priority ERP and another system, so information moves between them without typing it twice: a store order that opens in Priority, a lead that opens as a customer, a signed document that returns to its record.
- Does Priority have an API?
- Yes. Priority has a REST API built on OData, plus a Web SDK for running forms, procedures and reports, and webhooks that tell an outside system about an event.
- Can you integrate with Priority without a developer?
- Yes, through Make.com with the LeonAI Priority connector. You build a scenario by drag and drop, and Make runs it. LeonAI Priority has a Tester plan at no cost, up to 250 transactions a month; Make is priced separately.
- How do you keep an integration secure?
- Credentials are kept in Make's connection vault, our relay leaves from fixed IP addresses you can allow-list, and authentication headers and bodies are scrubbed from the logs. The API user in Priority gets only the permissions it needs.
- Which Priority versions can be connected?
- The LeonAI Priority connector supports Priority 18 and above, in the cloud and on-premises. An on-premises server behind a firewall allow-lists the fixed IP addresses our relay leaves from.