Webshipper API

Setup

Wiring Webshipper by hand means running its OAuth2 token flow, resolving the per-account host in the {account_name}.api.webshipper.io base URL, and handling retries yourself. Through Jentic you install once, import Webshipper from the API Directory, store the OAuth2 credentials once, and your agent calls it.

Permission scoping

Webshipper takes order and shipment details in the request body rather than in the path, so limit the agent to the operations it needs, such as creating orders or requesting rate quotes. You choose the operations it may call, so shipment creation is not included unless you add it.

Credential isolation

Your Webshipper OAuth2 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a shipping order' or 'get a rate quote', and Jentic returns the matching Webshipper operation with its input schema so the agent calls the right endpoint without browsing the reference docs.