Terminal49 API Reference

Setup

Wiring the Terminal49 API by hand means learning its token-based Authorization header auth against the api.terminal49.com/v2 host and handling shipment and tracking-request calls yourself. Through Jentic you install once, import the Terminal49 API from the API Directory, store the API token once, and your agent calls it.

Permission scoping

Terminal49 puts the shipment id in the URL path (/shipments/{id}), so a rule can pin your agent to one shipment: it can read and update that shipment and nothing else. You choose the operations it may call, so stopping or resuming tracking is not included unless you add it.

Credential isolation

Your Terminal49 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 'list shipments' or 'create a tracking request', and Jentic returns the matching Terminal49 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.