Xchange Trimble Trimble Vista AP API

Setup

Wiring the Trimble Vista AP API by hand means setting up its bearer auth and resolving the subscriber code that appears in every path across its cached invoice and vendor data yourself. Through Jentic you install once, import the Trimble Vista AP API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Trimble Vista AP API puts the subscriber code and record id in the URL path (/direct/subscribers/{subscriber_code}/vistaap2/data/invoices/cache/{id}), so a rule can pin your agent to one subscriber and its cached records. You choose the operations it may call, so search posts can be left out unless you add them and the reads can stand alone.

Credential isolation

Your Trimble Vista AP API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get all invoices from cache' or 'search cached vendors', and Jentic returns the matching Trimble Vista AP API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.