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

# WhatConverts API

WhatConverts lead tracking and analytics API. The API exposes 9 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create lead, list leads. Covers 9 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Create lead
- List leads
- Get lead
- Update lead
- Delete lead

## Use cases

### Analytics Operations

Use the WhatConverts API to perform analytics operations programmatically. The API provides 9 endpoints covering core functionality including create lead, list leads, get lead.

Example prompt: Call POST /leads to create lead

### Automated Accounts Management

Automate accounts operations by combining multiple WhatConverts API endpoints. Agents can list leads and then get lead in a single workflow.

Example prompt: Call GET /leads to list leads, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call WhatConverts 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 apiKey tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/leads` | Create lead |
| GET | `/leads` | List leads |
| GET | `/leads/{id}` | Get lead |
| PUT | `/leads/{id}` | Update lead |
| DELETE | `/leads/{id}` | Delete lead |
| GET | `/accounts` | List accounts |
| GET | `/accounts/{id}` | Get account |
| GET | `/profiles` | List profiles |

## Key resources

- **Accounts** — Operations related to Accounts
- **Leads** — Operations related to Leads
- **Profiles** — Operations related to Profiles

## Why Jentic

- **Setup:** Wiring the WhatConverts API by hand means placing its API key in the Authorization header on every lead and account call and handling retries yourself. Through Jentic you install once, import WhatConverts from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** WhatConverts puts the lead id in the URL path (`/leads/{id}`), so a rule can pin your agent to one lead: it can read or update that lead and nothing else. You choose the operations it may call, so deleting a lead is not included unless you add it.
- **Credential handling:** Your WhatConverts 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a lead' or 'read a lead's details', and Jentic returns the matching WhatConverts operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the WhatConverts API use?

The WhatConverts API uses an API key passed in the `Authorization` header. 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 lead with the WhatConverts API?

Yes. Use the POST /leads endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the WhatConverts 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 lead through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create lead'. Jentic returns the matching WhatConverts API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the WhatConverts API have?

The WhatConverts API exposes 9 endpoints covering accounts, leads, profiles operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which WhatConverts operations and credentials the agent may use. Since the lead id sits in the URL path (`/leads/{id}`), you can pin the agent to a single lead so it can read or update that lead and nothing else, and you choose exactly which operations it may call. Read-only access to leads, accounts, and profiles is easy to grant while destructive calls like DELETE `/leads/{id}` stay off unless you add them.