Developer & API

Last reviewed: 2026-06-01Reviewed by KickoffLabs SupportApplies to: Developers and technical marketersPlan: Paid plans; feature availability varies

Use this section when you are wiring KickoffLabs into your own site, app, CRM, analytics stack, or backend workflow.

Developer API reference

The legacy developer docs from dev.kickofflabs.com are now available inside this support site so API, webhook, and embed answers show up in the same navigation and search as the rest of the help center.

• Developer API reference
• Common API behavior
• Embed widgets
• Campaign API
• Leads API
• Tags API
• Webhooks

Choose your integration path

I want no-code lead sync

Start with Zapier or Make if you want to send KickoffLabs leads into another app without writing code.

I want KickoffLabs to send data to my endpoint

Use outbound webhooks when a lead event in KickoffLabs should notify your application or automation service.

• Send leads to a webhook
• Use Zapier webhooks

I want my app to send lead data into KickoffLabs

Use inbound webhooks or API workflows when another system is the source of the lead, purchase, tag, or action event.

• Receive inbound webhook lead data
• Build advanced workflows with the KickoffLabs API

I want to install KickoffLabs on an external site

Use the embed, popup, or AnyForm docs depending on how much of the signup experience should live outside KickoffLabs.

• Install AnyForm
• Install a popup box
• External-site integrations

I want custom front-end behavior

Use custom CSS, HTML, scripts, and social metadata carefully. Test in a private browser and keep scripts minimal so you do not break page loading, referral tracking, or form submission.

• Custom CSS, HTML, and scripts
• Social share tags on external pages
• Default tracking codes

Implementation checklist

Before launch:

• Confirm you are using IDs, keys, snippets, and endpoints from the correct campaign.
• Test with a fresh lead email.
• Verify the lead appears in KickoffLabs.
• Verify the destination app receives the expected fields.
• Remove or redact secrets from screenshots and support requests.
• Confirm custom redirects preserve referral query parameters.
• Test in a private/incognito browser to avoid stale cookies.

What to include when asking for help

Technical issues are easiest to debug when support can see the exact path you tested.

Include:

• Campaign URL or campaign name.
• Page URL or endpoint URL.
• Test lead email.
• Integration type: API, inbound webhook, outbound webhook, embed, popup, AnyForm, Zapier, Make, or custom code.
• Error message or failed response.
• Payload examples with API keys and secrets removed.
• Screenshots or a short screen recording.

Need help? Email support@kickofflabs.com. Include your campaign URL, endpoint or page URL, payload examples with secrets removed, and screenshots of any errors.