# Priority ERP OData REST URL Builder for Orders, Customers and Parts

> Source: https://netray.co/tools/priority-erp-odata-rest-url-builder
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Build Priority ERP OData URLs with host, tenant, company, entity, $filter, $select, $expand and $top, ready to paste into a REST client.

## Category

developer

## Erp

Priority

## Region

Israel and Europe

## Audience

- Priority developer
- Integration engineer
- ERP consultant

## Tool

**Kind:** template

**Output:** code

**Language:** http

**Fields:**

#### Server host

**Key:** host

**Type:** text

**Default:** priority.example.com

#### Tenant file

**Key:** tenant

**Type:** text

**Default:** tabula.ini

**Help:** The environment configuration name used in the URL path.

#### Company

**Key:** company

**Type:** text

**Default:** demo

#### Form (entity)

**Key:** entity

**Type:** select

**Options:**

- ORDERS
- CUSTOMERS
- LOGPART
- SUPPLIERS
- PORDERS

**Default:** ORDERS

#### $select fields

**Key:** select

**Type:** text

**Default:** ORDNAME,CUSTNAME,CURDATE

**Help:** Use the column names shown in the form's field list.

#### $filter

**Key:** filter

**Type:** text

**Default:** CURDATE ge 2026-01-01T00:00:00+02:00

**Help:** Dates use the ISO date time offset format.

#### $expand subform

**Key:** expand

**Type:** text

**Default:** ORDERITEMS_SUBFORM

#### $top

**Key:** top

**Type:** number

**Default:** 50

#### User name placeholder

**Key:** user

**Type:** text

**Default:** api_user

**Blocks:**

#### Read request

**Body:** GET https://{{host}}/odata/Priority/{{tenant}}/{{company}}/{{entity}}?$select={{select}}&$filter={{filter}}&$expand={{expand}}&$top={{top}}
Authorization: Basic BASE64({{user}}:PASSWORD_OR_APP_TOKEN)
Accept: application/json

#### Single record by key

**Body:** GET https://{{host}}/odata/Priority/{{tenant}}/{{company}}/{{entity}}('KEY_VALUE')?$expand={{expand}}
Authorization: Basic BASE64({{user}}:PASSWORD_OR_APP_TOKEN)
Accept: application/json

#### Create a record

**Body:** POST https://{{host}}/odata/Priority/{{tenant}}/{{company}}/{{entity}}
Authorization: Basic BASE64({{user}}:PASSWORD_OR_APP_TOKEN)
Content-Type: application/json

{ "FIELD_NAME": "VALUE" }

**Notes:** Entity, field and subform names depend on your Priority version and customizations, and the authentication scheme depends on how your installation is configured, so verify them in your own system and in the Priority REST API documentation. Test writes in a non-production company. Never hard code credentials.

## Content

**Intro:** Priority exposes its forms through an OData REST interface. Each form such as ORDERS or LOGPART becomes an entity, and subforms are reached with $expand. This builder assembles the URL parts so integration engineers can try a call quickly and then move it into code.

**Sections:**

#### How to use the generator

**Body:** Enter the server host, tenant file and company that identify your Priority environment. Choose a form, list the columns to return, add a filter and an optional subform to expand. The output includes a read request, a request for a single record and a create request skeleton. Paste them into a REST client, replace the credential placeholders and run them against a test company first.

#### How the URL is structured

**Body:** After the host, the path starts with odata/Priority, followed by the tenant configuration name and the company, then the form name. Query options follow the standard OData pattern: $select limits the columns, $filter limits rows, $expand pulls in a subform and $top limits the count. Priority fields have short upper case names, which you can find in the form's column list in the application.

**Bullets:**

- Use $select to avoid pulling every column of wide forms such as LOGPART.
- Use $expand for line items rather than separate calls per order.
- Keep date filters in ISO format with an offset.
- Prefer filtering on indexed key columns.

#### Reading versus writing

**Body:** Reading is straightforward; writing goes through the same business rules as the application, so required fields, triggers and authorization apply. A POST to a header form with nested subform arrays can create a document and its lines in one call. Because forms can be customized per installation, treat the field names in this tool as examples and confirm every name in your own environment before an integration goes live.

#### Common mistakes

**Body:** Typical issues are a wrong tenant file or company in the path, field names copied from another installation, filters on non-indexed columns that make the call slow, and missing paging for large result sets. Also check that the API user has rights to the form and the company, because Priority enforces form level privileges for API users as well.

**Cta:** If you want natural language questions over Priority data without sending it to a public cloud, Netray can build a read-only private layer on your own infrastructure.

**Faq:**

#### What is the tenant file in a Priority URL?

**Answer:** It is the configuration name that identifies the Priority environment on the server, commonly an ini name. Together with the company name it selects the data set that the request will read or modify. Ask your Priority administrator for the exact values.

#### Can I use these URLs for subforms like order lines?

**Answer:** Yes. Use $expand with the subform name on the header form, or address the subform path under a specific header key. Names vary by form and version, so check the form definition in your system.

#### Is the builder tied to a specific Priority version?

**Answer:** No. It follows the general OData pattern. Your installation may differ in forms, columns and authentication, so confirm names and security settings with your administrator or Priority partner before relying on the output.

#### Does the tool send my credentials anywhere?

**Answer:** No. All text is assembled in your browser and nothing is transmitted. Use placeholders in the generated text and keep real secrets in your client or a secret store.

## Search terms

priority erp odata, priority erp rest api, priority software api example, priority odata filter, priority erp orders api, priority erp logpart api, priority web sdk, priority erp integration

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json