YepCode REST API

Setup

Wiring YepCode by hand means running its OAuth2 client-credentials flow against the YepCode realm, substituting your team id into the cloud.yepcode.io host, and handling token refresh and retries yourself. Through Jentic you install once, import YepCode from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

YepCode puts the schedule and execution ids in the URL path (/schedules/{id}, /executions/{id}), so a rule can pin your agent to one schedule or execution: it can pause or resume that schedule and nothing else. You choose the operations it may call, so disruptive ones like killing an execution are not included unless you add them.

Credential isolation

Your YepCode 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 'resume a scheduled process' or 'create a variable', and Jentic returns the matching YepCode operation with its input schema so the agent calls the right endpoint without browsing the reference docs.