Leadboxer API Documentation

This is the complete API documentation for connecting to the Leadboxer API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Leadboxer: LeadBoxer is a lead data platform for lead identification, qualification, website visitor intelligence, and lead management across website, email, and enrichment data. Keep reading to get started.

Quickstart

Before you run your first Leadboxer request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Leadboxer connection — create or choose one in Connections. Note its connectionId.

Every Leadboxer action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/leadboxer/latest/actions/{actionSlug}

You need a MindCloud API Key and a Leadboxer connection. Then call an action such as Fetch User Datasets:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/leadboxer/latest/actions/fetch-user-datasets" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Leadboxer account that should run the action. MindCloud stores and refreshes the Leadboxer credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Leadboxer actions

All 34 published actions for this Leadboxer version. Each page documents the endpoint, arguments, and response controls.

• POSTAdd Custom Tracking Domain
• POSTAdd Dataset
• POSTAdd User Dataset
• PUTAssign Leads
• POSTCreate Or Associate User
• POSTCreate Segment
• DELETEDelete Custom Tracking Domain
• DELETEDelete Segment
• DELETEDelete User
• GETFetch User Datasets
• GETGet Custom Tracking Domain
• GETGet Default Segment Users
• GETGet User Datasets
• GETLookup Domain
• GETLookup IP Address
• DELETERemove Dataset
• DELETERemove Default Segment
• DELETERemove User Dataset
• GETResend User Invitation
• GETRetrieve Lead Details
• GETRetrieve Lead Events
• GETRetrieve Lead Sessions
• GETRetrieve Leads
• GETRetrieve Leads CSV
• GETRetrieve Segments
• PUTSave Default Segment
• PUTUpdate Custom Tracking Domain
• PUTUpdate Dataset Name
• PUTUpdate Form Tracking
• PUTUpdate Lead Tags
• PUTUpdate Segment
• PUTUpdate Segment User
• PUTUpdate User Name
• POSTValidate Custom Tracking Domain

Related apps

More apps on the Universal API, behind the same REST shape. Or browse all apps.

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms