Oysterhr Endpoints

Setup

Wiring the Oyster HR API by hand means minting a bearer token through /oauth2/token and carrying it on every expense, company, and department call. Through Jentic you install once, import the Oyster HR API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Oyster HR puts the expense id in the URL path (/v1/expenses/{id}), so a rule can pin your agent to one expense for the reads and actions you allow. You choose the operations it may call, so approving or declining an expense is not included unless you add it.

Credential isolation

Your Oyster HR bearer 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 'create an expense' or 'list departments', and Jentic returns the matching Oyster HR operation with its input schema so the agent calls the right endpoint without browsing the reference docs.