Ir al contenido

// plataforma para desarrolladores

API Potente para Inteligencia de Email

Integra la búsqueda, verificación y enriquecimiento de emails en tus aplicaciones. API RESTful con SDK para todos los lenguajes principales.

api.tomba.io/v1X-Tomba-Key · X-Tomba-SecretOpenAPI 3
GETapi.tomba.io/v1/domain-search
Ejemplo
organization.organization
Pied Piper
organization.industries
computer software
organization.company_size
11-50
organization.pattern
{first}
organization.accept_all
false
emails
2 items
emails[0].email
dinesh@piedpiper.com
emails[0].position
Software Engineer
emails[0].verification.status
valid

// 01 · endpoints

Cada endpoint, su coste y su página de referencia

REST sobre HTTPS, JSON de entrada y de salida, dos cabeceras para la autenticación. URL base https://api.tomba.io/v1.

GET/email-finderA person's work email from their name and company domainCoste:1 search creditSe cobra cuando:An address is returned with a status other than unknown; 6 search credits instead of 1 with phone data (enrich_mobile).
GET/domain-searchThe email addresses at a company, with names, roles and the company profileCoste:1 search credit per 10 resultsSe cobra cuando:At least one address is returned. 1 credit per 10 results requested with limit.
GET/email-verifierWhether an address is deliverable: syntax, MX, SMTP, catch-all and greylisting checksCoste:1 verification creditSe cobra cuando:The status is not disposable or unknown. Phone numbers returned with enrich_mobile cost 5 search credits each, from the search allowance.
GET/enrichThe person behind an email address: name, role, company and profilesCoste:1 search creditSe cobra cuando:An address is returned with a status other than unknown; 6 search credits instead of 1 with phone data (enrich_mobile).
GET/linkedinThe work email of the person behind a LinkedIn profile URLCoste:1 search creditSe cobra cuando:An address is returned; 6 search credits instead of 1 with phone data (enrich_mobile).
GET/author-finderThe email of the person who wrote an articleCoste:1 search creditSe cobra cuando:An address is returned.
GET/phone-finderA person's phone number from their email, domain or LinkedIn URLCoste:5 search creditsSe cobra cuando:A valid number is returned; 1 search credit instead of 5 when you search by domain.
GET/phone-validatorWhether a phone number is valid, its line type, carrier and regionCoste:1 search creditSe cobra cuando:Every successful response, including one with no data.
POST/reveal/searchCompanies that match a plain-language query or filtersCoste:1 search creditSe cobra cuando:At least one company is returned.
GET/combined/findThe person and their company from one email addressCoste:2 search creditsSe cobra cuando:A person is returned.
GET/companies/findA company profile from its domain: industry codes, size, location, socialsCoste:1 search creditSe cobra cuando:A company is returned.
GET/technologyThe technologies a website runs, by categoryCoste:FreeSe cobra cuando:Not charged; needs a positive search balance.
GET/email-countHow many addresses Tomba holds for a domain, by department and seniorityCoste:1 email count creditSe cobra cuando:Every call.
GET/similarCompanies similar to a domain, with their industryCoste:1 search credit per 10 resultsSe cobra cuando:Results are returned. 1 credit per 10 results requested with limit.
GET/email-formatThe address patterns a company uses, with their shareCoste:1 email count creditSe cobra cuando:Every successful call, including an empty result.
GET/locationWhere a company's people are, by countryCoste:1 email count creditSe cobra cuando:Every successful call, including an empty result.
GET/people/findA person profile from a work email: name, employment, location, social handlesCoste:1 search creditSe cobra cuando:A person is returned.
URL base https://api.tomba.io/v1 · Envía X-Tomba-Key y X-Tomba-Secret con cada solicitud.Todos los endpoints en la referencia de la API

// 02 · masivo

Trabajos masivos para listas de hasta 25.000 filas

Envía por POST una lista, filas o un CSV a /bulk/, recibe un webhook firmado cuando termine y paga una sola vez en la primera descarga.

Tipo masivoEntradaFilas máx.
POST/bulk/searchDomains or company names25,000
POST/bulk/similarDomains or company names5,000
POST/bulk/companyDomains or company names25,000
POST/bulk/finderNames, with a domain or company name10,000
POST/bulk/enrichEmail addresses20,000
POST/bulk/linkedinLinkedIn profile URLs20,000
POST/bulk/authorArticle URLs5,000
POST/bulk/verifierEmail addresses20,000
POST/bulk/phone-finderEmail addresses, LinkedIn URLs or domains10,000
POST/bulk/phone-validatorPhone numbers, with an optional country10,000

Desplázate en horizontal para ver todas las columnas

// 03 · límites de solicitudes

Capacidad por plan

Los límites son por cuenta, para todas sus claves. Los trabajos masivos tienen sus propios límites.

// límites de solicitudes

Solicitudes por segundo / minuto / día
FreeBasicGrowthPro
Search, finder, similar, technology1 / 2 / 53 / 50 / 5005 / 80 / 1,0008 / 150 / 4,000
Email verifier1 / 2 / 102 / 40 / 5003 / 60 / 1,0005 / 100 / 4,000

Desplázate en horizontal para ver todas las columnas

Pro Plus, Scale and credit packs of 50,000 or more: no limit on these endpoints. Enterprise: no per-second or per-minute limit, 100,000 requests a day. Daily limits reset at 00:00 UTC. Límites de solicitudes

// preguntas frecuentes

Preguntas frecuentes de API

¿Tiene más preguntas? Visite el centro de ayuda

// inicio rápido

Haz tu primera llamada en un minuto

Cuenta gratis, clave API real, los mismos endpoints que usan los clientes Enterprise.

  1. 01Crea una cuenta gratis25 créditos de búsqueda cada 30 días. Sin tarjeta.
  2. 02Copia tu clave y tu secretoDesde Claves API en el panel.
  3. 03Llama a la APIPega la solicitud; la respuesta es JSON.
curl -G https://api.tomba.io/v1/email-finder \
  --data-urlencode "domain=piedpiper.com" \
  --data-urlencode "first_name=Richard" \
  --data-urlencode "last_name=Hendricks" \
  -H "X-Tomba-Key: $TOMBA_API_KEY" \
  -H "X-Tomba-Secret: $TOMBA_SECRET_KEY"
Respuesta
200 OK
{
  "data": {
    "email": "richard@piedpiper.com",
    "first_name": "Richard",
    "last_name": "Hendricks",
    "full_name": "Richard Hendricks",
    "website_url": "piedpiper.com",
    "company": "Pied Piper",
    "pattern": "{first}",
    "department": "executive",
    "type": "personal",
    "position": "CEO",
    "country": "US",
    "gender": "male",
    "twitter": null,
    "linkedin": "https://www.linkedin.com/in/richard-hendricks",
    "score": 100,
    "accept_all": false,
    "phone_number": true,
    "verification": {
      "date": "2025-01-15T10:32:00+01:00",
      "status": "valid"
    },
    "sources": [
      {
        "uri": "https://piedpiper.com/blog/engineering",
        "website_url": "piedpiper.com",
        "extracted_on": "2024-06-01T09:14:07+01:00",
        "last_seen_on": "2025-01-10T17:02:44+01:00",
        "still_on_page": true
      }
    ],
    "phone_data": []
  }
}