Prioritysoftware Priority REST API
Agent-ready OpenAPI document · curated by JenticFinanceAccountingbasic, bearer13 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Access Priority ERP entities via OData for CRUD operations, subform navigation, batch processing, and metadata management. Supports dynamic form paths across all Priority business modules.
Use for: I need to create a sales order in Priority ERP, I want to batch-update multiple inventory records at once, List all entities from the INVOICES form with a date filter, Get the full metadata schema for Priority forms
Not supported: Does not handle payroll, HR workflows, or CRM pipeline management - use for OData CRUD and batch access to Priority ERP financial and operational entities only.
Jentic publishes the only available OpenAPI specification for Priority REST API, keeping it validated and agent-ready. Priority REST API provides OData-based access to Priority ERP for reading, querying, creating, updating, and deleting business entities across all Priority forms. The API exposes 13 endpoints covering entity CRUD, subform navigation, batch operations with up to 100 operations per request, and metadata management including cache clearing. It supports Basic authentication and Bearer token (PAT) access.
Install Jentic One Beta
Connect the Priority REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Priority REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fprioritysoftware.com%2Fprioritysoftware" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fprioritysoftware.com%2Fprioritysoftware" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Priority REST API.
Query Priority ERP forms with OData filtering, sorting, pagination, and field selection
Execute batch operations combining up to 100 requests in a single API call
Navigate parent-child form relationships through subform entity paths
Clear and rebuild entity metadata cache after form customizations
Create and update business records in any Priority form via dynamic entity paths
Retrieve system version and OData version information for environment validation
Expand related entities inline to reduce round-trip queries
Use Cases
Patterns agents use Priority REST API for, with concrete tasks.
★ Batch ERP Data Operations
Execute multiple Priority ERP operations in a single request using the batch endpoint. The API supports combining up to 100 create, update, or delete operations into one batch call, reducing network overhead and ensuring atomic-like processing. This is critical for high-volume data synchronization between external systems and Priority ERP, such as importing daily sales orders or updating inventory counts across multiple warehouses.
Execute a batch request to create 3 new entities in the ORDERS form, each with a different CUSTNAME and CURDATE value, and verify all return 201 status
Dynamic Form Querying with OData
Access any Priority ERP form using dynamic entity set paths and OData query parameters. The API accepts the form name as a URL path segment and supports $filter, $select, $expand, $top, $skip, and $orderby for precise data retrieval. Agents can construct queries against ORDERS, CUSTOMERS, INVOICES, INVENTORY, or any configured Priority form without hardcoded path knowledge.
Query the CUSTOMERS entity set with $filter 'STATDES eq Active', $select 'CUSTNAME,PHONE,EMAIL', and $top 25 to retrieve the first page of active customers
Subform Data Navigation
Access child entities related to a parent record by navigating subform paths. Priority ERP uses a parent-child form hierarchy where orders contain order items, invoices contain line details, and customers contain contacts. The API exposes these relationships through URL path navigation, allowing agents to drill into related data without separate lookup queries.
Retrieve order 'SO-2026-001' from the ORDERS entity set, then access its ORDERITEMS subform and create a new line item with part number 'WIDGET-A' and quantity 50
AI Agent ERP Automation via Jentic
AI agents can access the full depth of Priority ERP through Jentic without managing OData URL construction or credential rotation. Jentic maps natural language intents to Priority operations, provides request schemas with parameter descriptions, and isolates credentials so agents never see raw Basic Auth passwords or bearer tokens in their context.
Search Jentic for 'batch update priority erp records', load the batchRequest operation schema, and execute a batch containing 2 PATCH operations to update customer phone numbers
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for priority rest api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/
List available entity sets in this Priority instance
GET
/$metadata
Retrieve full OData schema metadata
GET
/{entitySet}
Query entities with OData parameters
POST
/{entitySet}
Create a new entity in a Priority form
PATCH
/{entitySet}('{key}')
Update an entity by key
DELETE
/{entitySet}('{key}')
Delete an entity by key
POST
/$batch
Execute batch of up to 100 operations
POST
/ClearEntityMetadata
Clear and rebuild form metadata cache
GET
/
List available entity sets in this Priority instance
GET
/$metadata
Retrieve full OData schema metadata
GET
/{entitySet}
Query entities with OData parameters
POST
/{entitySet}
Create a new entity in a Priority form
PATCH
/{entitySet}('{key}')
Update an entity by key
DELETE
/{entitySet}('{key}')
Delete an entity by key
POST
/$batch
Execute batch of up to 100 operations
POST
/ClearEntityMetadata
Clear and rebuild form metadata cache
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Priority REST API by hand means choosing Basic auth or a bearer token, assembling the templated OData host with your domain, tabula.ini, and instance, and handling the {entitySet} path and $batch calls yourself. Through Jentic you install once, import the Priority REST API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Priority puts the entity key in the URL path (/{entitySet}('{key}')), so a rule can pin your agent to specific entity records. You choose the operations it may call, so a destructive one like DELETE or a $batch write is not included unless you add it.
Credential isolation
Your Priority Basic auth credentials or bearer token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a sales order in Priority' or 'batch update inventory', and Jentic returns the matching Priority operation with its input schema, including the dynamic entity set path variable, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Priority REST API through Jentic.
Why is there no official OpenAPI spec for Priority REST API?
Priority Software does not publish an OpenAPI specification for this API variant. Jentic generates and maintains this spec so that AI agents and developers can call Priority REST API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Priority REST API use?
The API supports Basic authentication with your Priority username and password, and Bearer token authentication using Personal Access Tokens (PAT) or OAuth2 tokens. Through Jentic, these credentials are stored encrypted in the vault. Agents authenticate without handling raw passwords or token strings.
How many operations can I include in a batch request?
The Priority REST API supports up to 100 operations per batch request via POST /$batch. Each operation in the batch can be a create, update, or delete against any entity set. The batch executes operations sequentially and returns individual status codes for each operation in the response.
Can I access Priority subform data through the API?
Yes. Use the path pattern /{entitySet}('{key}')/{subform} to access child entities. For example, GET /ORDERS('ORD001')/ORDERITEMS returns all line items for that order. You can also POST to the same path to create new subform entities linked to the parent record.
How do I clear the metadata cache after customizing a Priority form?
Call POST /ClearEntityMetadata with an optional JSON body containing the Entity field set to the form name you customized. This rebuilds the REST metadata for that form. If you omit the Entity field, metadata for all forms is rebuilt. This is necessary after adding or removing fields from Priority forms.
How do I query Priority ERP data through Jentic?
Search Jentic for 'list priority erp entities', load the listEntities operation schema, and execute with the entitySet path parameter set to the form name (e.g., 'ORDERS'). Add OData query parameters like $filter, $top, and $select to narrow results. Install with pip install jentic and set JENTIC_AGENT_API_KEY.
Can I limit what my agent is allowed to do with the Priority REST API?
Yes. Because you run Jentic One yourself, your own rules decide which Priority operations the agent may call, so you can grant read-only access to entity sets like ORDERS or CUSTOMERS while withholding a destructive DELETE or a POST /$batch write. Priority puts the entity key in the URL path, such as /{entitySet}('{key}'), so a rule can pin the agent to specific records rather than every entity in a form. Your Basic auth credentials or bearer token stay with your instance and are injected only for the operations you have allowed.
GET STARTED