canonical: https://jentic.com/apis/tellyourwholestory.com/tellyourwholestory

# Tellyourwholestory WholeStory Zapier API

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.

## For AI agents

Programmatically create a session token, validate a session token. Covers 3 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create a session token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/sessions` | Create a session token |
| GET | `/sessions` | Validate a session token |
| POST | `/invitations` | Create a candidate invitation |

## Key resources

- **Sessions** — Session token management
- **Invitations** — Candidate invitation management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 71 / 100
- **View full report:** https://jentic.com/apis/tellyourwholestory.com/tellyourwholestory/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the WholeStory Zapier API?

Yes. Because you run Jentic One yourself, you decide which WholeStory Zapier API operations your agent may call, and only the ones you name are available to it. This API carries its targets in the request body rather than the URL path, so you can allow just what a task needs, such as validating a session token while blocking candidate invitation creation. Your own rules govern both the permitted operations and the credentials the agent may use.