Prioritysoftware Priority REST API

Name: Priority REST API
Brand: Priority REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingbasic, bearer13 EndpointsREST

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.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with Priority REST API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Priority Basic Auth credentials and Bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access per session without seeing raw passwords or PAT values.

Intent-based discovery

Agents search by intent (e.g., 'create sales order in priority' or 'batch update inventory') and Jentic returns the matching Priority operation with its parameter schema, including dynamic path variables for entity set names.

Time to first call

Direct Priority integration: 2-4 days for OData URL construction, auth configuration, and form path discovery. Through Jentic: under 1 hour using pip install jentic, intent search, load, and execute.

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 at https://app.jentic.com/sign-up.

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.

Prioritysoftware Priority REST API

Connect the Priority REST API to your agent

Capabilities

Start building with Priority REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs