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 your Jentic One instance, 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.

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

Yes. Because you self-host Jentic One, your own rules decide which Leverly operations the agent may call, so you can grant only what a task needs, such as POST /inquiries/create.json to post a lead or GET /callhistory to read call activity. Leverly carries its target in the request body and query rather than as an id in the path, so you scope the agent at the operation level and simply leave out operations you have not allowed, like POST /inquiries/stop_reattempts. The username and token are held by your own instance and injected at call time, so the agent only reaches the endpoints you permit.