Leverly API

Name: Leverly API
Brand: Leverly API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMDeal PipelineapiKey4 EndpointsREST

For Agents

Post inbound leads into Leverly's auto-dial workflow, stop reattempts on a number, and retrieve call history for sales follow-up.

Install Jentic One Beta

Connect the Leverly API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Leverly 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Leverly API.

Submit inbound web leads into Leverly's call workflow via POST /inquiries/create.json

Halt automatic call reattempts for a specific lead phone number through /inquiries/stop_reattempts

Retrieve the authenticated user's account profile from /users

GET STARTED

Start building with Leverly API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Leverly API for, with concrete tasks.

★ Speed-to-lead from web forms

When a high-intent visitor submits a contact form on the marketing site, an integration posts the lead immediately to POST /inquiries/create.json. Leverly then dials an available rep and connects them to the prospect within seconds. This compresses the response window that drives most B2C conversion lift and avoids the typical multi-minute lag of CRM-to-dialler hand-offs.

POST a new inquiry to /inquiries/create.json with the prospect's name, phone number, and source campaign id, then confirm a successful response.

Stop reattempts after conversion

Once a lead has been spoken to or has converted, Leverly should not keep dialling. An integration listens for conversion or call-completion events from the CRM and calls POST /inquiries/stop_reattempts with the lead's phone number to halt further auto-dial attempts. This prevents over-contact complaints and keeps reporting accurate.

Call POST /inquiries/stop_reattempts with phone '+15551234567' to halt further outbound dial attempts for that lead.

Call activity reporting

Sales operations teams pull GET /callhistory on a schedule to feed call outcomes into their BI stack. The data lets analysts measure connection rates, time-to-call, and rep productivity over time, complementing CRM-side opportunity tracking with the dialler's view of the funnel top.

Pull GET /callhistory for the previous 7 days, aggregate by rep, and compute connection rate and average talk time.

AI agent inbound lead routing via Jentic

An AI lead-qualification agent screens inbound chat conversations and, when intent is high, hands the lead to Leverly for an immediate phone connection. Through Jentic the agent searches for 'post a lead for callback', loads POST /inquiries/create.json, and executes with the username and token credentials held in the Jentic vault. The dialer fires within seconds and the agent never sees the raw token.

Use Jentic to search 'post a new lead for instant call back', load /inquiries/create.json, and submit the qualified prospect with their name and phone number.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for leverly api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/inquiries/create.json

Post a new lead inquiry into the dial workflow.

POST

/inquiries/stop_reattempts

Stop call reattempts for a lead phone number.

GET

/users

Retrieve the authenticated user's profile.

GET

/callhistory

Pull recent call history.

POST

/inquiries/create.json

Post a new lead inquiry into the dial workflow.

POST

/inquiries/stop_reattempts

Stop call reattempts for a lead phone number.

GET

/users

Retrieve the authenticated user's profile.

GET

/callhistory

Pull recent call history.

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Leverly username and token credentials are held in the Jentic MAXsystem vault and injected as query parameters at request time. Because Leverly auth lives on the URL, keeping these values out of agent context is especially important — Jentic guarantees the raw token never appears in prompts or logs.

Intent-based discovery

Agents search Jentic with phrases like 'post a lead for instant call back' and the platform returns POST /inquiries/create.json with its input schema, so the agent calls the right Leverly path without browsing docs.

Time to first call

Direct integration: half a day for query-parameter auth, lead schema, and reattempt suppression. Through Jentic: under 30 minutes to search, load, and fire the first lead.

FAQs

Specific to using Leverly API through Jentic.

Why is there no official OpenAPI spec for Leverly API?

Leverly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Leverly via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Leverly API use?

Leverly authenticates using a username and token passed as query parameters on every request. Through Jentic these credentials are held in the MAXsystem vault, so the agent never sees the raw token and the values are never exposed in agent-side logs.

Can I push a lead into the Leverly auto-dial workflow with this API?

Yes. POST /inquiries/create.json submits a new lead with phone number and contact details into the Leverly workflow, which then auto-dials a rep and connects them to the prospect. This is the primary speed-to-lead operation in the API.

What are the rate limits for the Leverly API?

Leverly does not publish public rate limits for the v1 API. Because the dialer is real-time, treat /inquiries/create.json as a low-latency hot path: send each lead exactly once, retry only on network errors, and avoid bulk reposts that could trigger duplicate calls.

How do I stop further dial attempts for a lead through Jentic?

Install with 'pip install jentic', search for 'stop dialer reattempts for a lead', and Jentic returns POST /inquiries/stop_reattempts. Load the schema, supply the phone number, and execute. Jentic injects the username and token query parameters automatically.

Leverly API

Connect the Leverly API to your agent

Capabilities

Start building with Leverly API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs