Leads
Store and manage leads
Retrieve Leads
Returns the leads of your workspace, or your own leads when you aren't in a workspace, with each lead's list and custom attribute values.
listreturns only the leads in one list.meta.total_pagesis rounded down, so it doesn't count a last, partial page. Usemeta.totalto know when you've read every lead.- With no matching leads,
data.leadsis an empty array andmetais absent.
Also accepts an OAuth 2.0 access token with the leads scope.
query Parameters
pagePage number, starting at 1.
limitLeads per page. Values above 200 are treated as 200.
listID of a lead list, to return only the leads in it.
sortField to sort by.
directionSort direction.
Retrieve Leads › Responses
A page of leads.
Create a Lead
Saves a lead to your account. Every field is optional, email included. Tomba doesn't check for duplicates: saving the same email address twice creates two leads.
list_idmust be a JSON number. Sent as a string, the lead is still created, but without the list and without every field that followslist_idin the request body. Alist_idthat isn't one of your own lists is dropped.attributessets custom attribute values, keyed by the attribute'sidentifierfromGET /attributes. Send the values as strings. Keys that don't match one of your attributes are ignored.- You can store as many leads as
pricing.available_leadsinGET /me. Past that, the request fails with422rate_limit.
When your plan isn't Free and you've set up a lead webhook, Tomba sends the new lead to it. See Lead events.
Also accepts an OAuth 2.0 access token with the leads scope.
Create a Lead › Request Body
emailEmail address. Stored in lowercase.
list_idID of one of your lead lists. Must be a JSON number.
first_nameFirst name, 1 to 25 characters.
last_nameLast name, 1 to 25 characters.
countryTwo-letter country code in uppercase, for example US.
website_urlCompany domain, for example stripe.com.
positionJob title, up to 255 characters.
twitterTwitter profile URL. A bare handle fails validation.
linkedinLinkedIn profile URL.
phone_numberPhone number.
companyCompany name, up to 55 characters.
notesNotes, up to 55 characters.
scoreLead score, up to 100.
lead_sourceWhere the lead came from, as a code in a string: 1 domain search, 2 email finder, 3 email verifier, 4 browser extension. Leads return it as domain, finder, verify, or browser.
Custom attribute values keyed by attribute identifier. Values must be strings.
Create a Lead › Responses
Lead created.
Retrieve a Single Lead
Returns one lead of your workspace, as the only item of data.leads.
A lead that doesn't exist, or that you can't see, returns 200 with an empty data.leads array, not 404.
Also accepts an OAuth 2.0 access token with the leads scope.
path Parameters
leadIdThe lead's ID. A non-numeric ID fails with 422.
Retrieve a Single Lead › Responses
The lead, or an empty array when there's no such lead.
Update a lead
Updates a lead of your workspace. Send only the fields to change; the others keep their values.
list_idmoves the lead to that list. A list outside your workspace is ignored.attributesadds or replaces custom attribute values, keyed by the attribute'sidentifier. Keys that don't match an attribute of your workspace are ignored.- Some limits differ from
POST /leads:first_nameandlast_nameneed at least 2 characters,positiontakes up to 25, andtwitterandlinkedinup to 99.
Also accepts an OAuth 2.0 access token with the leads scope.
path Parameters
leadIdThe lead's ID. A non-numeric ID fails with 422.
Update a lead › Request Body
emailEmail address. Stored in lowercase.
first_nameFirst name, 2 to 25 characters.
last_nameLast name, 2 to 25 characters.
countryTwo-letter country code in uppercase, for example US.
website_urlCompany domain, for example stripe.com.
positionJob title, up to 25 characters.
twitterTwitter profile URL, up to 99 characters.
linkedinLinkedIn profile URL, up to 99 characters.
phone_numberPhone number.
companyCompany name, up to 55 characters.
notesNotes, up to 55 characters.
scoreLead score, up to 100.
list_idID of a lead list in your workspace. Must be a JSON number.
lead_sourceWhere the lead came from, as a code in a string (see POST /leads).
Custom attribute values keyed by attribute identifier. Values must be strings.
Update a lead › Responses
Lead updated.
Result of an update or delete.
Delete a lead
Deletes a lead of your workspace, with its custom attribute values.
Also accepts an OAuth 2.0 access token with the leads scope.
path Parameters
leadIdThe lead's ID. A non-numeric ID fails with 422.
Delete a lead › Responses
Lead deleted.
Result of an update or delete.