Sourcewhale App SourceWhale API

Setup

Wiring the SourceWhale API by hand means passing its api-key header on every call, pointing at the sourcewhale.app/public-api host, and handling paging and retries across its campaign and candidate calls yourself. Through Jentic you install once, import the SourceWhale API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The SourceWhale API carries its candidate and campaign targets in the request body and query parameters rather than resource ids in the URL path, so limit the agent to the operations it needs, such as listing campaigns or searching candidates. You choose the operations it may call, so write operations like adding or modifying a candidate are not included unless you add them.

Credential isolation

Your SourceWhale API key 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 campaigns' or 'search candidates', and Jentic returns the matching SourceWhale API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.