For Agents
Programmatically create a session token, validate a session token. Covers 3 operations.
Use for: I need to a session token, I want to validate a session token, Search for a candidate invitation, List all records from WholeStory Zapier API
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
WholeStory is a technology platform for employers that integrates the candidate's pivotal life experiences into the screening and interview process. This API provides Zapier integration endpoints for session management and candidate invitations. The API exposes 3 endpoints.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WholeStory Zapier API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftellyourwholestory.com%2Ftellyourwholestory" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftellyourwholestory.com%2Ftellyourwholestory" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with WholeStory Zapier API.
Create a session token
Validate a session token
Integrate WholeStory Zapier API into automated workflows
Query and filter WholeStory Zapier API records by parameters
Monitor WholeStory Zapier API operational status and events
Patterns agents use WholeStory Zapier API for, with concrete tasks.
★ Identity and Authentication Operations
Use the WholeStory Zapier API to perform identity auth operations programmatically. The API provides 3 endpoints covering core functionality including create a session token, validate a session token, create a candidate invitation.
Call POST /sessions to create a session token
Automated Sessions Management
Automate sessions operations by combining multiple WholeStory Zapier API endpoints. Agents can validate a session token and then create a candidate invitation in a single workflow.
Call GET /sessions to validate a session token, then verify the result
AI Agent Integration via Jentic
AI agents discover and call WholeStory Zapier API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'create a session token', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — wholestory is a technology platform for employers that integrates the candidate's pivotal life experiences into the screening and interview process.
METHOD
PATH
DESCRIPTION
/sessions
Create a session token
/sessions
Validate a session token
/invitations
Create a candidate invitation
/sessions
Create a session token
/sessions
Validate a session token
/invitations
Create a candidate invitation
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the WholeStory Zapier API by hand still means writing the HTTP client, response parsing, and retry handling for its sessions and invitations endpoints yourself. Through Jentic you install once, import the WholeStory Zapier API from the API Directory, and your agent calls it.
Permission scoping
The WholeStory Zapier API carries its targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as listing sessions or creating an invitation. You choose that allowed set, and only the operations you name are available to the agent.
Credential isolation
Any WholeStory credential 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 sessions' or 'create an invitation', and Jentic returns the matching WholeStory Zapier API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using WholeStory Zapier API through Jentic.
What authentication does the WholeStory Zapier API use?
The WholeStory Zapier API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create a session token with the WholeStory Zapier API?
Yes. Use the POST /sessions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the WholeStory Zapier API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a session token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a session token'. Jentic returns the matching WholeStory Zapier API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the WholeStory Zapier API have?
The WholeStory Zapier API exposes 3 endpoints covering sessions, invitations operations.
GET STARTED