SYNDUIT API

Setup

Wiring the SYNDUIT API by hand means implementing its OAuth2 authorization-code flow against api.synduit.com, exchanging codes for tokens and refreshing them, then shaping the contact and tag requests yourself. Through Jentic you install once, import SYNDUIT from the API Directory, store the OAuth2 credentials once, and your agent calls it.

Permission scoping

SYNDUIT puts the contact id in the URL path (/contacts/{id}), so a rule can pin your agent to one contact: it can read and update that record and nothing else. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.

Credential isolation

Your SYNDUIT 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 contact' or 'verify the OAuth token', and Jentic returns the matching SYNDUIT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.