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.