Use a full key for your own systems

A full key reads and changes every lead in your account. Use it for your own systems: reports, Zapier, your website's back end. Keep it on servers you control, never in a web page.

Make one

Account admins: Team, API keys, New full key. Copy it straight away: it's shown only once.

What it can do

All calls are under https://leadvault.com/api/v1, with the key in an Authorization: Bearer lv_full_... header.

• GET /leads: find leads by phone, email, reference_id, type, stage, source or status, or those received or changed since a time, a page at a time.
• GET /leads/{id}, PATCH /leads/{id}: read a lead, or change its details, answers, source, stage and who has it in one call.
• POST /leads/{id}/stage, /assign, /notes, /callbacks: move it, give it to someone, add a note (with how a call went) or a callback.
• GET and POST /leads/{id}/appointments, GET /appointments: book appointments and keep another calendar in step.
• GET /lead-types, /sources, /users: the lists you'll need for names and ids.
• POST /leads: add a lead, with source, assigned_to and stage if you like.

Changes made with a key show on the lead's timeline as API · the key's name. A key never reads SSNs, dates of birth or recordings.

The API reference has every call, with examples. It imports into Postman and Insomnia.

Limits

120 calls a minute per key, and 64 KB a call. See API errors and how to fix them.

Want LeadVault to tell your system when something happens, instead of asking? Use webhooks.

Didn't answer it? Ask us.