// get /v1/author-finder
Author Finder API
Find the verified email address and full profile of any article or blog post author from a URL.
1 search credit
// api console
Example response from the API reference
- richard@piedpiper.com
- full_name
- Richard Hendricks
- position
- CEO
- score
- 100
- verification.status
- valid
- info.title
- Middle-out compression, explained
- info.publisher_name
- Pied Piper
- info.publish_date
- 2025-03-04
// 01 · request
Author Finder is one HTTPS request
Send the parameters with your key and secret. Every SDK, the CLI and the MCP server make this same call.
GET
/author-finderParameterurlrequired- The article URL
curl "https://api.tomba.io/v1/author-finder?url=https%3A%2F%2Fpiedpiper.com%2Fblog%2Fmiddle-out-compression" \
-H "X-Tomba-Key: $TOMBA_API_KEY" \
-H "X-Tomba-Secret: $TOMBA_SECRET_KEY"const res = await fetch("https://api.tomba.io/v1/author-finder?url=https%3A%2F%2Fpiedpiper.com%2Fblog%2Fmiddle-out-compression", {
headers: {
"X-Tomba-Key": process.env.TOMBA_API_KEY,
"X-Tomba-Secret": process.env.TOMBA_SECRET_KEY
}
});
const { data } = await res.json();import os, requests
res = requests.get(
"https://api.tomba.io/v1/author-finder?url=https%3A%2F%2Fpiedpiper.com%2Fblog%2Fmiddle-out-compression",
headers={
"X-Tomba-Key": os.environ["TOMBA_API_KEY"],
"X-Tomba-Secret": os.environ["TOMBA_SECRET_KEY"],
},
)
data = res.json()["data"]// 02 · response
What comes back
JSON, the same in every language. Fields Tomba doesn't know are null, never guessed.
GET
/author-finderFielddata.emailstring | null- The address, or null when none is found
data.scoreinteger- Confidence from 0 to 100
data.verification.statusstring | null- valid, accept_all, invalid or unknown, with verification.date
data.full_name, data.position, data.departmentstring | null- Name, job title and team
data.typestring | null- personal or generic (a role address such as sales@)
data.linkedin, data.twitterstring | null- Public profiles
data.sources[]array | null- Up to 20 public pages where the address was found, with dates
data.info.title, data.info.publisher_name, data.info.publish_datestring- The article, who published it and when
data.info.candidates[]array | null- Every author candidate on the page, with a name confidence and score
GET /author-finder
200 OK· 1 search credit
{
"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
}
],
"info": {
"url": "https://piedpiper.com/blog/middle-out-compression",
"title": "Middle-out compression, explained",
"og_image": "https://piedpiper.com/blog/middle-out-compression/cover.png",
"description": "How middle-out compression reached a Weissman score of 5.2.",
"article_domain": "piedpiper.com",
"publisher_name": "Pied Piper",
"publish_date": "2025-03-04",
"candidates": [
{
"full_name": "Richard Hendricks",
"first_name": "Richard",
"last_name": "Hendricks",
"job_title": "CEO",
"linkedin": "https://www.linkedin.com/in/richard-hendricks",
"name_confidence": 0.98,
"score": 0.95,
"count": 3
}
]
}
}
}// 03 · cost and limits
What a call costs
A call is charged only under the condition below. Rate limits depend on your plan.
// cost
1search credit
Charged when: An address is returned.
Errors, 429 and 451 responses, and the same request again within your usage window cost nothing.
How credits work// rate limits
Requests per second / minute / day| Free | Basic | Growth | Pro | |
|---|---|---|---|---|
| Search, finder, similar, technology | 1 / 2 / 5 | 3 / 50 / 500 | 5 / 80 / 1,000 | 8 / 150 / 4,000 |
| Email verifier | 1 / 2 / 10 | 2 / 40 / 500 | 3 / 60 / 1,000 | 5 / 100 / 4,000 |
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. Rate limits
Pass any article or blog post URL. Tomba extracts the author name from bylines, meta tags, and schema markup, then matches it against our database to find their verified email.
Author email, confidence score, full name, job title, company, department, seniority, LinkedIn, Twitter, phone number, and source URLs.
Blog posts, news articles, Medium posts, and any page with a visible author byline or structured author data.
Yes. Bulk Author Finder API processes hundreds of URLs at once via CSV upload.
No. Credits are only consumed when a valid author email is found. No charge for articles where the author cannot be identified.
Tomba extracts author data from multiple signals including meta tags, schema.org markup, bylines, and page structure. Each result includes a confidence score.
13 official SDKs: C#, Dart, Deno, Elixir, Go, Lua, Node.js, Perl, PHP, Python, R, Ruby and Rust. Or use the REST API directly.
Author data is extracted from the publicly visible portion of the page. If the author byline and meta tags are visible without a subscription, Author Finder will work.