How do I perform incremental sync with the Priority REST API?

Use the $since query parameter on the GET /{entityCollection} endpoint with an ISO 8601 timestamp value. The API returns only entities modified after that timestamp. For example, GET /ORDERS?$since=2026-06-14T00:00:00Z returns orders changed in the last day. Store the latest sync timestamp after each run for the next query.

Can I execute batch operations with the Priority REST API?

Yes. POST to /{entityCollection}('{entityId}')/$batch with a JSON body containing multiple insert or update operations. This processes them server-side in a single request, reducing network overhead for bulk data changes. Useful for nightly imports or bulk inventory adjustments.

How do I navigate to related subform entities?

Use the path pattern GET /{entityCollection}('{entityId}')/{relatedEntity} to access child records. For example, GET /ORDERS('ORD001')/ORDERITEMS returns all line items for that order. You can also POST to the same path to create new related entities, or PATCH /{entityCollection}('{entityId}')/{relatedEntity}('{relatedEntityId}') to update a specific child record.

How do I query Priority ERP forms through Jentic?

Search Jentic for 'query priority erp orders' or any intent describing your data need. Load the getEntityCollection operation schema which includes the entityCollection path parameter and all OData query options. Execute with your form name and filters. Install with pip install jentic and set JENTIC_AGENT_API_KEY.

What entity collections are available in the Priority REST API?

Call GET / (the service root) to retrieve a list of all available entity collections in your Priority instance. Each entry has a name (the form name like ORDERS, CUSTOMERS, INVOICES) and a URL. The full schema is at GET /$metadata which returns an XML document describing all entity types, properties, and relationships.

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 read-only work like GET on an entity collection can be allowed while a write such as PATCH or a POST batch insert stays off unless you add it. Since Priority puts the entity id in the URL path (/{entityCollection}('{entityId}')), you can pin the agent to specific entity records rather than a whole collection. Your Basic auth, OAuth2 token, or Personal Access Token is injected only at execution time under those rules, so the agent never sees the raw credentials.