LeadBoxer integration: operations for AI agents
LeadBoxer connects to Type.com as an integration. This page lists the 43 operations documented for Claude and Codex in Type.com: 17 read, 15 write, 11 destructive.
About LeadBoxer
LeadBoxer vendor API references, subject to account permissions.
Categories: Analytics & Data
How to connect LeadBoxer to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
43 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
43 operations listed.
App and Lookup API
- Read
Domain Lookup
Retrieve organization details associated with a domain name. Provide a clean domain name (e.g., leadboxer.com) without protocol or www prefix. Returned Data When a match is found, the following fields are returned: Organization core details - organizationName - organizationDomain - organizationDomainAliases - organizationType - organizationStatus - organizationSource - organizationReportDate Organization description - organizationDescription - organizationDescriptionShort Organization industry & size - organizationIndustryCode - organizationIndustryGroup - organizationIndustryName - organizationEmployeeCountRangeCode - organizationEmployeeCountRangeName Organization address - organizationAddress.organizationStreetName - organizationAddress.organizationCity - organizationAddress.organizationState - organizationAddress.organizationPostalCode - organizationAddress.organizationCountry - organizationAddress.organizationCountryCode - organizationAddress.organizationPhone Organization social links - organizationSocialLinks.organizationLinkedinUrl Organization specialties - organizationSpecialties
GET /v1/domain-lookup - Read
IP Address Lookup
Retrieve detailed information about an IP address, including organization, geolocation, ISP details, and metadata. Returned Data When a match is found, the following fields are returned: Organization fields - ipDomain - ipOrganization Geo location fields - ipCountryName - ipCountryCode - ipRegionName - ipCity - ipSubContinent - ipLatitude - ipLongitude - ipTimezone IP address details - ipIsp - ipRange - ipUsageType Meta data - searchIp - searchResponseTimeMs
GET /v1/ip-lookup - Read
Email Lookup
Retrieve the professional profile of a contact by email address. Only the email is required; name and company are optional hints that improve matching. Credits: 50 per lookup, charged only when a profile is found. A lookup that finds no profile (404) is free. Available on every plan. The same lookup is also available as GET /v1/email-lookup?email=..., but POST is recommended because it keeps the email address out of URLs and server logs. Returned Data When a match is found, the following fields are returned: Contact details - email - fullName - headline - linkedinUrl - seniority - jobFunction - location Languages - languages[].name - languages[].proficiency Experience - experience[].title - experience[].companyName - experience[].startYear - experience[].endYear - experience[].current
POST /v1/email-lookup - Read
Email Lookup (GET)
Same as POST /v1/email-lookup, with the email and the optional hints as query parameters, for consistency with the IP and domain lookups. Prefer POST where possible: with GET the email address ends up in URLs, browser history and server logs. Credits: 50 per lookup, charged only when a profile is found. A lookup that finds no profile (404) is free. Available on every plan.
GET /v1/email-lookup - Read
Get User Datasets
Returns the list of datasets the authenticated user has access to.
GET /v1/users/datasets - Read
Retrieve Segments for a Given Site
Fetches segments associated with a specified dataset and account, for a user identified by email.
GET /v1/segments - Read
Get Default Segment Users
Get the list of User IDs for whom the specified segment is set as the default under the given Dataset ID.
GET /v1/segment/preference - Read
Retrieve Leads
Returns a list of leads in JSON format based on the provided filters and query parameters.
GET /v1/leads - Read
Retrieve Lead Details
Returns detailed information for a single lead, identified by its lead ID.
GET /v1/leads/{leadId} - Read
Retrieve Lead Sessions
Returns all sessions associated with a specific lead ID. Results can be filtered by segment and time range.
GET /v1/leads/sessions - Read
Retrieve Leads (CSV)
Exports a filtered list of leads as a CSV file for download.
GET /v1/leads/export - Read
Retrieve Lead Events
Returns all events associated with a specific session ID. Results can be optionally filtered by segment.
GET /v1/leads/events - Read
Fetch User Datasets
Retrieves the datasets associated with a user for the given account. This provides details about the user's datasets under their account.
GET /v1/user-datasets - Read
Validate Custom Tracking Domain
Validate the given custom tracking domain.
POST /v1/management/ctd/validate - Read
Get Custom Tracking Domain by Dataset ID
Get all custom tracking domains for a given dataset Id.
GET /v1/management/ctd/{datasetId} - Read
Retrieve leads exclusions
Use this API to retrieve dataset exclusion rules.
GET /v1/dataset-exclusion - Read
Get Credit Grants
Get Credit Grants
GET /v1/management/credits - Write
Update User Name
Updates the display name of an existing user.
PUT /v1/users/{userId}/name - Write
Create or Associate User
Creates a new user or associates an existing user with an account, depending on the provided data.
POST /v1/users - Write
Resend User Invitation
Resends an invitation email to the specified user.
GET /v1/users/{userId}/invite/resend - Write
Assign Leads
Assigns lead to a user.
PUT /v1/management/assign-leads - Write
Update Dataset Name
Updates the human-readable name of the specified dataset.
PUT /v1/datasets/{datasetId}/name - Write
Add Dataset
Creates a new dataset in the account and associates it with the specified users.
POST /v1/datasets - Write
Update Existing Segment
Update an existing segment with the given configuration. Use this endpoint to update filter criteria, email preferences etc.
PUT /v1/segments/{segmentId} - Write
Update Segment User
Updates the user associated with the segment, which allow that user to access the segment.
PUT /v1/segments/user - Write
Create a New Segment
Creates a new segmentRequest for the specified account and dataset using the provided configuration. This includes applying filters and setting up any email notification preferences.
POST /v1/segments - Write
Add User Dataset
Associates a user with a dataset. This operation allows the user to access and work with the specified dataset.
POST /v1/user-datasets - Write
Update Custom Tracking Domain by Dataset ID
Update custom tracking domain entry for the given dataset Id and ctd.
PUT /v1/management/ctd/update - Write
Add Custom Tracking Domain
Adds a custom tracking domain to the dataset and triggers the certificate generation process. <br/><br/><b>Note:</b> This operation may take several minutes to complete.<br/><br/>The response indicates whether the request resulted in an error, completed successfully, or requires additional DNS configuration.
POST /v1/management/ctd/add - Destructive
Delete User
Removes a user from the account and revokes access to all associated resources.
DELETE /v1/users/{userId} - Destructive
Update Lead Tags
Adds or removes lead tags for a specified lead.
PUT /v1/management/lead-tags - Destructive
Update Form Tracking
Updates the form tracking configuration for the specified dataset, including enabling/disabling tracking, IP masking, and form input attributes.
PUT /v1/datasets/{datasetId}/form-tracking - Destructive
Remove Dataset
Deletes the specified dataset from the account.
DELETE /v1/datasets/{datasetId} - Destructive
Delete Segment
To delete specified segment.
DELETE /v1/segments/{segmentId} - Destructive
Add/Update Default Segment for Users
Sets the given Segment ID as the default segment for the provided list of User IDs under the specified Dataset ID. Users included in the list will have their default segment added or updated accordingly. Any users not included in the list will have their existing default-segment association under this dataset removed.
PUT /v1/segment/preference - Destructive
Remove Default Segment
Remove Default Segment for the user with the given Email under the given Dataset ID.
DELETE /v1/segment/preference - Destructive
Remove User Dataset
Disassociates a user from a dataset. This operation will prevent the user from accessing the specified dataset.
DELETE /v1/user-datasets - Destructive
Delete Custom Tracking Domain by Dataset ID
Delete custom tracking domain entry for the given dataset Id and ctd.
DELETE /v1/management/ctd/{datasetId} - Destructive
Hide leads
Use this API to define exclusion rules for specific datasets. These rules allow you to hide leads based on different criteria, such as a specific identifier (use_id) or attributes like organizationName or organizationDomain. Each rule is created using a combination of type and data for a given dataset.
POST /v1/dataset-exclusion - Destructive
Unhide leads
Use this API to delete existing dataset exclusion rules.
DELETE /v1/dataset-exclusion
Tracking API
- Write
Track Event via GET
This is your first endpoint! Edit this page to start documenting your API.
GET / - Write
Track email open event
Records behavioural events, creating or updating event/session/user data and analytics counters. This tracking request is not a semantic read.
GET /log - Write
Track Event via POST
Submit tracking events via the explicitly documented POST variant.
POST /
No operations match.
See How connections work for access and permissions, or browse all integrations.