Lead webhooks
Send leads into Bigly automatically from your website, lead vendor or other software using the contacts API.
Generating an API key, the address and header to post leads to, the fields to send, duplicate handling, and checking that leads arrive.
If your leads come from a website form, a lead vendor or your own software, you can send them straight into Bigly as they happen. Your system posts each lead to Bigly's contacts API, and Bigly creates the contact, ready for your AI agent to follow up.
This is the same connection Zapier uses. Lead ads from Facebook and TikTok, and form fills from your landing pages, come in through their own integrations instead.
Before you start
- You need permission to manage account settings to create an API key.
- The person setting up the sending system needs to be able to send an HTTPS request with a header. This is usually a developer or your lead vendor.
1. Generate an API key
- Open the user menu (your initials, top right) and click API keys.
- Click + Generate, enter a name such as leads-prod, and click Generate key.
- Copy the key straight away. It won't be shown again.
See API keys for more.
2. Send leads to Bigly
Give your developer or lead vendor:
| Setting | Value |
|---|---|
| Method | POST |
| Address | Your Bigly address followed by /api/zap/contacts, for example https://yourcompany.biglysales.com/api/zap/contacts |
| Header | Authorization: Bearer followed by your API key |
| Body | The lead as JSON |
Each lead needs at least a phone number or an email. For the full list of fields, open API keys and click View the Public API docs.
User menu › API keys with the View the Public API docs link highlighted in the header text.
3. Check that leads arrive
- Send a test lead.
- Open Contacts and search for it.
- A successful request gets a success response from Bigly. A rejected one returns a message saying why.
How duplicates are handled
Bigly doesn't create a second contact for the same person. If a lead matches an existing contact, the request is rejected with Contact already in the system.
Keep your key safe
- Anyone with the key can add contacts to your account. Don't put it in public web pages or front-end code.
- Use a separate key for each system so you can delete one without affecting the others.
- If API keys shows a warning that some keys are not locked to this tenant, generate a replacement, switch your system to it, then delete the old key.