{"api":"Capterra reviews","apiRows":{"Employee profile":4602,"Employee email":3864,"Email validation":5041,"Employee phone":1429,"Company profile":1489,"Company headcount":487,"Phone validation":1427,"Post comments":485,"Post reactions":410,"Employee lookalikes":236,"Company lookalikes":768,"Company technologies":510,"Company job count":67,"Employee posts":510,"Company posts":501,"Company funding":313,"Company jobs":405,"Employee search":1531,"Company search":737,"Job search":551,"Reverse email lookup":921,"Post search":401,"Post details":567,"Job details":484,"Employee comments":257,"Employee reactions":210,"Post reposts":120,"Employee recommendations":96,"Job lookalikes":51,"Employee articles":47,"Company enrichment":2362,"People search":1975,"Company discovery":2025,"Job postings":575,"Job posting details":339,"Person enrichment":326,"Leadership changes":131,"Company hierarchy":154,"Web search":901,"SERP":5452,"News search":919,"Web scraping":2233,"Keyword research":89,"Ranked keywords":60,"Related keywords":136,"Backlinks":102,"Domain authority":86,"X profile":478,"X posts":332,"Instagram profile":430,"Instagram posts":257,"TikTok profile":259,"TikTok videos":238,"YouTube channel":288,"YouTube channel videos":179,"Reddit profile":82,"Reddit posts":79,"Facebook page":132,"Facebook posts":117,"Threads profile":65,"Threads posts":67,"Facebook ads":57,"G2 reviews":11,"Capterra reviews":11,"Trustpilot reviews":22,"Glassdoor reviews":22},"treeCounts":{"Employee profile":{"best":156,"top":3},"Employee email":{"best":161,"top":3},"Email validation":{"best":200,"top":3},"Employee phone":{"best":93,"top":3},"Company profile":{"best":87,"top":3},"Company headcount":{"best":28,"top":3},"Phone validation":{"best":64,"top":3},"Post comments":{"best":34,"top":3},"Post reactions":{"best":27,"top":3},"Employee lookalikes":{"best":16,"top":3},"Company lookalikes":{"best":39,"top":3},"Company technologies":{"best":46,"top":3},"Company job count":{"best":7,"top":3},"Employee posts":{"best":42,"top":3},"Company posts":{"best":44,"top":3},"Company funding":{"best":32,"top":3},"Company jobs":{"best":43,"top":3},"Employee search":{"best":51,"top":3},"Company search":{"best":32,"top":3},"Job search":{"best":42,"top":3},"Reverse email lookup":{"best":56,"top":3},"Post search":{"best":35,"top":3},"Post details":{"best":49,"top":3},"Job details":{"best":41,"top":3},"Employee comments":{"best":22,"top":3},"Employee reactions":{"best":16,"top":3},"Post reposts":{"best":9,"top":3},"Employee recommendations":{"best":8,"top":3},"Job lookalikes":{"best":5,"top":3},"Employee articles":{"best":5,"top":3},"Company enrichment":{"best":141,"top":3},"People search":{"best":110,"top":3},"Company discovery":{"best":131,"top":3},"Job postings":{"best":43,"top":3},"Job posting details":{"best":34,"top":3},"Person enrichment":{"best":33,"top":3},"Leadership changes":{"best":11,"top":3},"Company hierarchy":{"best":17,"top":3},"Web search":{"best":67,"top":3},"SERP":{"best":86,"top":3},"News search":{"best":44,"top":3},"Web scraping":{"best":55,"top":3},"Keyword research":{"best":9,"top":3},"Ranked keywords":{"best":7,"top":3},"Related keywords":{"best":9,"top":3},"Backlinks":{"best":7,"top":3},"Domain authority":{"best":8,"top":3},"X profile":{"best":30,"top":3},"X posts":{"best":29,"top":3},"Instagram profile":{"best":25,"top":3},"Instagram posts":{"best":23,"top":3},"TikTok profile":{"best":24,"top":3},"TikTok videos":{"best":24,"top":3},"YouTube channel":{"best":25,"top":3},"YouTube channel videos":{"best":23,"top":3},"Reddit profile":{"best":9,"top":3},"Reddit posts":{"best":10,"top":3},"Facebook page":{"best":12,"top":3},"Facebook posts":{"best":11,"top":3},"Threads profile":{"best":11,"top":3},"Threads posts":{"best":11,"top":3},"Facebook ads":{"best":7,"top":3},"G2 reviews":{"best":1,"top":1},"Capterra reviews":{"best":1,"top":1},"Trustpilot reviews":{"best":2,"top":2},"Glassdoor reviews":{"best":2,"top":2}},"bestPages":{"Employee profile":["/best-linkedin-profile-api","Best LinkedIn profile API in 2026"],"Employee email":["/best-email-finder-api","Best email finder API in 2026"],"Email validation":["/best-email-verification-api","Best email verification API in 2026"],"Employee phone":["/best-phone-finder-api","Best phone finder API in 2026"],"Company profile":["/best-linkedin-company-data-api","Best LinkedIn company data API in 2026"],"Company headcount":["/best-company-headcount-api","Best company headcount API in 2026"],"Phone validation":["/best-phone-validation-api","Best phone validation API in 2026"],"Post comments":["/best-linkedin-post-comment-api","Best LinkedIn post comment API in 2026"],"Post reactions":["/best-linkedin-post-reaction-api","Best LinkedIn post reaction API in 2026"],"Employee lookalikes":["/best-similar-people-api","Best similar people API in 2026"],"Company lookalikes":["/best-similar-companies-api","Best similar companies API in 2026"],"Company technologies":["/best-tech-stack-api","Best tech stack API in 2026"],"Employee posts":["/best-linkedin-profile-post-api","Best LinkedIn profile post API in 2026"],"Company posts":["/best-linkedin-company-post-api","Best LinkedIn company post API in 2026"],"Company funding":["/best-company-funding-api","Best company funding API in 2026"],"Company jobs":["/best-company-open-jobs-api","Best company open jobs API in 2026"],"Employee search":["/best-linkedin-people-search-api","Best LinkedIn people search API in 2026"],"Company search":["/best-linkedin-company-search-api","Best LinkedIn company search API in 2026"],"Job search":["/best-linkedin-job-search-api","Best LinkedIn job search API in 2026"],"Reverse email lookup":["/best-reverse-email-lookup-api","Best reverse email lookup API in 2026"],"Post search":["/best-linkedin-post-search-api","Best LinkedIn post search API in 2026"],"Post details":["/best-linkedin-post-details-api","Best LinkedIn post details API in 2026"],"Job details":["/best-linkedin-job-details-api","Best LinkedIn job details API in 2026"],"Employee comments":["/best-linkedin-profile-comment-api","Best LinkedIn profile comment API in 2026"],"Employee reactions":["/best-linkedin-profile-reaction-api","Best LinkedIn profile reaction API in 2026"],"Post reposts":["/best-linkedin-post-repost-api","Best LinkedIn post repost API in 2026"],"Company enrichment":["/best-company-enrichment-api","Best company enrichment API in 2026"],"People search":["/best-people-search-api","Best people search API in 2026"],"Company discovery":["/best-company-discovery-api","Best company discovery API in 2026"],"Job postings":["/best-job-postings-api","Best job postings API in 2026"],"Job posting details":["/best-job-posting-details-api","Best job posting details API in 2026"],"Person enrichment":["/best-people-enrichment-api","Best people enrichment API in 2026"],"Company hierarchy":["/best-company-hierarchy-api","Best company hierarchy API in 2026"],"Web search":["/best-web-search-api","Best web search API in 2026"],"SERP":["/best-serp-api","Best SERP API in 2026"],"News search":["/best-news-api","Best news API in 2026"],"Web scraping":["/best-web-scraping-api","Best web scraping API in 2026"],"Related keywords":["/best-related-keywords-api","Best related keywords API in 2026"],"X posts":["/best-x-twitter-post-api","Best X (Twitter) post API in 2026"],"Instagram profile":["/best-instagram-profile-api","Best Instagram profile API in 2026"],"Instagram posts":["/best-instagram-post-api","Best Instagram post API in 2026"],"TikTok profile":["/best-tiktok-profile-api","Best TikTok profile API in 2026"],"TikTok videos":["/best-tiktok-video-api","Best TikTok video API in 2026"],"YouTube channel":["/best-youtube-channel-api","Best YouTube channel API in 2026"],"YouTube channel videos":["/best-youtube-channel-video-api","Best YouTube channel video API in 2026"],"Reddit profile":["/best-reddit-profile-api","Best Reddit profile API in 2026"],"Reddit posts":["/best-reddit-post-api","Best Reddit post API in 2026"]},"accuratePages":{"Employee email":["/most-accurate-email-finder-api","Most accurate email finder API in 2026"],"Email validation":["/most-accurate-email-verification-api","Most accurate email verification API in 2026"],"Employee phone":["/most-accurate-phone-finder-api","Most accurate phone finder API in 2026"],"Company headcount":["/most-accurate-company-headcount-api","Most accurate company headcount API in 2026"],"Phone validation":["/most-accurate-phone-validation-api","Most accurate phone validation API in 2026"],"Reverse email lookup":["/most-accurate-reverse-email-lookup-api","Most accurate reverse email lookup API in 2026"]},"familyPages":[["/best-linkedin-api","Best LinkedIn API in 2026"],["/best-phone-api","Best phone API in 2026"],["/best-email-api","Best email API in 2026"]],"first":[{"provider":"Scavio","api":"Capterra reviews","website":"https://scavio.dev","pricingPage":"https://scavio.dev/pricing","pitch":"Page through a Capterra product's B2B software reviews as JSON: the overall score plus five per-criterion scores including likelihood to recommend, title, pros, cons, advice, how long the reviewer used the product, the incentivized flag and its disclosure, what they considered and what they switched from, and the reviewer's job title, industry and company size.","strengths":[],"aggregators":null,"freshness":"live","fieldFreshness":null,"history":null,"countries":null,"fullFamilyTree":null,"checks":null,"searchesIn":null,"keep":"no limit","use":"You agree not to use the Service to: Violate any applicable law, regulation, or third-party rights. Scrape, redistribute, or resell raw search results as a competing search API service. Circumvent rate limits, authentication mechanisms, or other technical restrictions. Send automated queries designed to overload or degrade the Service. Use the Service for any activity that could cause harm to minors. Transmit malware, viruses, or any destructive code through API requests. Misrepresent your identity or the source of API requests. [...] Search results returned by the API originate from third-party platforms. You are responsible for complying with those platforms' terms of service when using the data.","plan":"Growth, monthly","who":"anyone","billing":"monthly","charged":null,"topUp":null,"pay":500,"currency":"USD","exchangeRate":1,"termMonths":1,"from":null,"graduated":null,"units":200000,"unit":"credit","renews":"month","expires":"Unused credits do not roll over","costUnits":2,"calls":100000,"monthlyCap":null,"perThousand":0.2,"waterfall":null,"listPerThousand":null,"overagePerThousand":null,"unitsCap":"hard","addons":null,"notFoundPerThousand":null,"catchAllPerThousand":null,"bounceRefund":null,"repeatFree":null,"alsoPaysFor":[],"sharesBudgetWith":["388 other calls"],"startPerCall":null,"startPerCallMax":null,"monthlyFee":null,"monthlyFeePer":null,"extras":[],"per":"page","resultsPerPage":25,"resultsCap":null,"perDay":null,"perSecond":null,"concurrent":50,"batch":1,"minBatch":null,"answer":"in the call","latencyMs":null,"call":null,"method":"POST","path":"/api/v1/capterra/reviews","send":"one of product_id or url; slug, page","fields":["product ID","product UUID","product name","product slug","product URL","logo","description","vendor ID","vendor name","target market","product updated at","page","results on page","per page","review count","total pages","has more","overall rating","rating scale","category ratings","video review count","badge count","categories","breadcrumbs","alternatives","review ID","title","published at","rating","sub-ratings","text","pros","cons","advice","time used","incentive","incentivized","incentive note","review source","reasons for choosing","reasons for switching","alternatives considered","switched from","reviewer name","reviewer job title","reviewer industry","reviewer company size","reviewer picture","reviewer verified","verification source","anonymous","reply text","response time","credits used","credits remaining"]}],"total":11,"checked":["2026-10-29","2026-10-29"],"freshness":["Live","Within an hour","Within a day","Within a week","Within a month","Within a year","Stored, age unknown"],"providers":[{"label":"Scavio","value":"Scavio on its own site"}],"at":[5],"fields":{"Capterra reviews":["advice","alternatives","alternatives considered","anonymous","badge count","breadcrumbs","categories","category ratings","cons","credits remaining","credits used","description","has more","incentive","incentive note","incentivized","logo","overall rating","page","per page","product ID","product name","product slug","product updated at","product URL","product UUID","pros","published at","rating","rating scale","reasons for choosing","reasons for switching","reply text","response time","results on page","review count","review ID","review source","reviewer company size","reviewer industry","reviewer job title","reviewer name","reviewer picture","reviewer verified","sub-ratings","switched from","target market","text","time used","title","total pages","vendor ID","vendor name","verification source","video review count"]},"same":["api","per","strengths","aggregators","waterfall","repeatFree","resultsCap","startPerCall","monthlyFee","extras","paysFor","overagePerThousand","addons","catchAllPerThousand","bounceRefund","pitch","freshness","history","countries","fullFamilyTree","checks","searchesIn","keep","use","perDay","perSecond","batch","answer","latencyMs","send","method","path","who","readFrom"],"facets":["defaults","price","fields","billing","freshness"],"ties":{"Capterra reviews":{"tied":[],"movedPages":{},"canonicals":{"Scavio":"free"}}},"shared":[],"notes":{"name":"The sheet's first column gives each row's name. No two rows on the sheet share a name. The name starts with the provider, then the plan's price. Some names: \"API Builderz, $50 monthly\", \"HarvestAPI, $280 pack\", \"Crawlbase, pay as you go\", \"Bright Data, top-up\" (a prepaid balance of any amount), \"AnyAPI, top-up from $10\" (a balance you top up by $10 or more), \"free\" or \"contact us\". Two plans with the same price also get the plan's name. We drop any words in the plan's name that the price already gives. If two rows share a name after that, we add the call's method and path to each name. When two names still match, we add the plan's units. When they still match after that, we add the call's name. The sheet's own CSV and JSON files have no name column. datacircle.json and datacircle.csv have a name column with the same names as the sheets.","api":"This column names each row's API. Each API has a sheet in the GTM APIs list. Most sheets share the API's name. For the rest, we give the sheet's name after the API. \"Employee profile\", on the LinkedIn profiles sheet, returns a person's LinkedIn profile. \"Employee email\", on the Find email sheet, finds a person's work email. \"Email validation\", on the Validate email sheet, checks whether an email address takes mail. \"Employee phone\", on the Find phone sheet, finds a person's phone number. \"Company profile\", on the LinkedIn company profiles sheet, returns a company's LinkedIn page. \"Company headcount\" counts a company's staff. \"Phone validation\", on the Validate phone sheet, checks whether a phone number is valid. \"Post comments\", on the LinkedIn post comments sheet, returns the comments on a LinkedIn post. \"Post reactions\", on the LinkedIn post reactions sheet, returns the reactions to a LinkedIn post, each with the person who reacted. \"Employee lookalikes\", on the Similar people sheet, returns people similar to the person you send. \"Company lookalikes\", on the Similar companies sheet, returns companies similar to the company you send. \"Company technologies\" returns the tools a company uses. \"Company job count\" counts the jobs a company has open on LinkedIn. \"Employee posts\", on the LinkedIn person posts sheet, returns a person's LinkedIn posts. \"Company posts\", on the LinkedIn company posts sheet, returns a company's LinkedIn posts. \"Company funding\" returns a company's funding rounds. \"Company jobs\", on the Company open jobs sheet, returns the jobs a company has open. \"Employee search\", on the LinkedIn people search sheet, finds people by job title, company and place. \"Company search\", on the LinkedIn company search sheet, finds companies by industry, size and place. \"Job search\", on the LinkedIn job search sheet, finds jobs by title, company and place. \"Reverse email lookup\" finds the person behind an email address. \"Post search\", on the LinkedIn post search sheet, finds posts by keyword. \"Post details\", on the LinkedIn post details sheet, returns a post from the post's URL or ID. \"Job details\", on the LinkedIn job details sheet, returns a job from the job's URL or ID. \"Employee comments\", on the LinkedIn person comments sheet, returns the comments a person left on posts. \"Employee reactions\", on the LinkedIn person reactions sheet, returns the posts a person reacted to. \"Post reposts\", on the LinkedIn post reposts sheet, returns the people who reposted a LinkedIn post. \"Employee recommendations\", on the LinkedIn person recommendations sheet, returns the recommendations on a person's LinkedIn profile. \"Job lookalikes\", on the Similar jobs sheet, returns jobs similar to the job you send. \"Employee articles\", on the LinkedIn person articles sheet, returns a person's LinkedIn articles. \"Company enrichment\" returns a company's profile from each seller's own database. \"People search\" finds people in each seller's own database. \"Company discovery\" finds companies in each seller's own database. \"Job postings\" finds job postings in each seller's own database. \"Job posting details\" returns a job posting from the posting's ID. \"Person enrichment\" returns a person's profile. \"Leadership changes\" returns the new hires, promotions and departures in a company's senior roles. \"Company hierarchy\" returns a company's parent companies and subsidiaries. \"Web search\" returns the web pages that match a query. \"SERP\" returns a search engine's results page as data. \"News search\" returns the news articles that match a query. \"Web scraping\" returns a page's content from the page's URL. \"Keyword research\" returns a keyword's search volume, cost per click and competition. \"Ranked keywords\" returns the keywords a domain ranks for in Google, with the domain's position and traffic for each keyword. \"Related keywords\" returns keywords like the keyword you send, with the search volume of each. \"Backlinks\" returns the links that point to a domain. \"Domain authority\" returns a domain's authority score and the number of links to the domain. \"X profile\" returns an X (Twitter) account's profile from the account's handle. \"X posts\" returns an X account's posts. \"Instagram profile\" returns an Instagram account's profile. \"Instagram posts\" returns an Instagram account's posts. \"TikTok profile\" returns a TikTok account's profile. \"TikTok videos\" returns a TikTok account's videos. \"YouTube channel\" returns a YouTube channel's name, subscribers and description. \"YouTube channel videos\" returns a YouTube channel's videos. \"Reddit profile\" returns a Reddit account's profile. \"Reddit posts\" returns a Reddit account's posts. \"Facebook page\" returns a Facebook page's details from the page's URL. \"Facebook posts\" returns a Facebook page's posts. \"Threads profile\" returns a Threads account's profile. \"Threads posts\" returns a Threads account's posts. \"Facebook ads\" returns a company's ads from Meta's Ad Library. \"G2 reviews\" returns a software product's reviews on G2. \"Capterra reviews\" returns a software product's reviews on Capterra. \"Trustpilot reviews\" returns a company's reviews on Trustpilot. \"Glassdoor reviews\" returns a company's reviews on Glassdoor, written by people who work or worked there.","score":"We score each plan out of 100 on five parts: price, data, cost to get started, bundled calls and performance. We score data and performance from our benchmark of the provider's call. Until we benchmark the call, the plan's data, performance and Overall scores are N/A. The data, performance and Overall scores are also N/A on a plan that lacks a check or feature the benchmarked plan has. A plan whose data score is 0 has an Overall score of 0, whatever the plan's other scores. Each API's sheet shows what we measured on each benchmarked plan, in the columns after the price. We rank a plan's price per 1,000 against the other scored plans of the same API. We score cost to get started and bundled calls on the plan alone. We give N/A to yearly plans, contact us plans and plans over $500 to start. We also give N/A to plans bought on a marketplace and plans that need your own LinkedIn or X account. We score a free plan only when the provider has no paid plan for that call. The free plan must never end. Any limit on the plan's calls must reset each day or sooner. Other free plans get N/A. A plan we don't score gets no score for any of the five parts, even when we benchmarked the call. Click Score in the sheet's bar to set the five weights. The JSON, datacircle.json and datacircle.csv give each plan's score at the default weights. A plan with N/A has an empty score in the JSON, datacircle.json and datacircle.csv. The sheet's CSV has no scores.","Price score":"The plan's price score out of 100. We rank the plan's $ per 1,000 against the $ per 1,000 of the other scored plans of the same API. We also count the cost of a call that finds nothing. Some plans give no $ per 1,000. For those plans, when each call returns one result, we use the price our benchmark paid per call. We scale that price by what a credit costs on the plan. We skip our benchmark's price for a plan if another paid plan for the same call lists a $ per 1,000. Plans for one call can each charge a different price per call. On the sheet, click or tap the score to see how we worked out the score.","Data score":"The plan's data score out of 100, from our benchmark of the provider's call. On some APIs, the score measures how complete the call's answer is. On others, the score measures how often the answer is right. We lower the score when we test the call on fewer inputs than the benchmark has. Until we benchmark the call, the score is N/A, and so is the Overall score. The data, performance and Overall scores are also N/A on a plan that lacks a check or feature the benchmarked plan has. On the sheet, click or tap the score to see how we scored the plan. Each API's sheet shows what we measured on each benchmarked plan, in the columns after the price.","Cost to get started score":"The plan's score out of 100 for getting your first result. The score weighs who can get the plan, how you pay, and the least you pay to start. On the sheet, click or tap the score to see why.","Bundle score":"The plan's score out of 100 for the other calls the plan's price gets you. Also pays for lists those calls. On the sheet, click or tap the score to see why.","Performance score":"The plan's performance score out of 100, from our benchmark of the provider's call. We divide the fastest benchmarked provider's median time by this provider's median time. We compare live calls with live calls, and calls that answer from a copy with each other. A median under 0.1 s counts as 0.1 s, since the baseline we take off varies by about that much. The Performance score and the Overall score are N/A until we benchmark the call. The data, performance and Overall scores are also N/A on a plan that lacks a check or feature the benchmarked plan has. If the call gave no answer we could time, the Performance score is N/A. The Overall score then counts Performance as 0. The Performance score is N/A when we timed no other call of the same kind in the same benchmark. The Overall score then leaves Performance out. On the sheet, click or tap the score to see how we scored the plan. Each API's sheet shows what we measured on each benchmarked plan, in the columns after the price.","perThousand":"The price of 1,000 reviews on this plan, in dollars. The price is 0 on a free plan. On a plan that charges by the call, each call asks for one review. We add the Start fee to each review's price. On a plan that charges by the page, we divide 1,000 by the most results one page holds. We round that up to whole pages and add up what the pages cost. We leave the price blank when the provider doesn't say how many results a page holds. On a flat fee, we take the most reviews the plan allows in one month. We multiply that by the months the fee covers. We divide the fee by that total. Then we multiply by 1,000. We leave the price blank when the provider doesn't say how many reviews the plan allows. A plan with no end date and only limits per second, minute, hour or day has no cap on reviews. A flat fee with no cap on reviews shows \"no limit\" on the sheet. We leave the price blank in the CSV and JSON. On a waterfall's paid plan, we show the average cost of a call. We take the price of each provider listed under Waterfall. We weight each price by how often a call reaches that provider. We leave the price blank when a provider a call can reach has no hit rate or page size. On a plan with a Monthly fee, we first subtract one month of the fee from the plan's units. Then we divide the plan's price by the number of reviews the remaining units buy. Then we multiply by 1,000. We leave the price blank when the Monthly fee uses up all the plan's units. Some plans limit calls per second, minute, hour, day or month. We divide the price by the reviews the limit allows, if that is fewer than the reviews you pay for. Then we multiply by 1,000. We leave the price blank on a top-up, because a top-up buys no fixed number of reviews. We also leave the price blank when the provider's website doesn't say what a review costs on this plan. We leave the price blank, too, when the website doesn't say how many reviews the price buys.","per":"The price counts a \"call\" or a \"result\". A call asks for one review. A result is each review a call returns. Some calls return a page of reviews. \"result\" means you pay for each result on the page. \"page of 50\" counts each page. You pay for a whole page even when the page holds fewer than 50. In the JSON, resultsPerPage is the most results a page holds. resultsPerPage is null when the price isn't per page or the provider doesn't say the page size. \"page, size not stated\" means the provider doesn't say how many results a page holds.","billing":"How you pay. \"free\": the plan costs nothing. \"on-demand\": you pay for what you use, with nothing to buy first. \"one-time\": a pack or a top-up you pay for first, then use. \"contact\": no public price, so you ask the provider for one. A subscription: \"monthly\", \"quarterly\" (every three months), \"half-yearly\" (every six months) or \"yearly\". The sheet shows \"one-time\" as \"pay first\" and \"on-demand\" as \"pay as you go\".","perMonth":"On a subscription: the plan's price for one month in dollars. We divide the plan's Pay by the months the plan buys (termMonths), 12 on most yearly plans. We work out this price for the sheet, to the cent. The sheet's CSV and JSON leave this price out. datacircle.json and datacircle.csv have this price. Blank (null) on every other plan.","notFoundPerThousand":"What you pay for 1,000 products the provider can't find. 0 when the provider charges nothing for them, as on free plans. On a waterfall, the cost of a call when no provider finds the answer. That cost is the sum of the prices of the providers that charge for a miss.","strengths":"The plan's strengths, which we work out from the plan's row. Each strength is a band that many plans of the same API are in. Strengths differ by API. We list and explain them under Strengths on datacircle.dev/fields. Only LinkedIn profiles and Find email have strengths so far. Blank ([] in the JSON) when the plan has none, and then the plan's page leaves Strengths out. Under Filters, you see only the rows with every strength you tick.","aggregators":"Aggregators like treg and Deepline sell the row's call. With one aggregator account, you reach many providers. Each cell gives what a call costs through the aggregator with your own provider key. The cell also gives what 1,000 reviews cost when you pay the aggregator and have no account at the provider: \"treg: your key free, paid $1.50\". We add \"per 1,000 results\" when the aggregator charges per result found. We say \"paid, no fixed price\" when the aggregator publishes no price. Some aggregators charge by the page. For those, we take the largest page size. Then we price the full pages you need for 1,000 results. We write \"paid, page size not stated\" when the aggregator doesn't say how many results a page holds. Some aggregators list the call but don't say whether you pay them or use your own key. For those, we write \"listed, how it's sold not stated\". An aggregator may sell one of the provider's calls without saying which. Then the cell ends with \"this call or another\", the provider's name and \"call\": \"this call or another Pubrio call\". A cell says \"none\" when no aggregator we checked for the row's API sells the call. A blank cell (null in the JSON) means we haven't checked any aggregator for that API. We skip calls an aggregator doesn't list. In the JSON, each aggregator has these keys. aggregator is the aggregator's name. url is the aggregator's page for the call. ownKey is what a call costs there with your own key, or null when you can't use yours. paid is true when you can pay the aggregator. paid and ownKey are both null when the aggregator doesn't say how the call is sold. callStated is false when the aggregator doesn't say whether the call is this one or another of the provider's. usd is the aggregator's price in dollars for one per, or null when the aggregator sets no price. perThousand is the aggregator's price in dollars for 1,000. per is \"call\", \"result\" or \"page\". resultsPerPage is the most results a page holds, or null.","waterfall":"Some routers, like treg's, try one provider after another until one finds the answer. On a router's call, the Waterfall column lists each provider the router tries, in order. Each provider shows the router's name for the provider's call in brackets. Then we give the provider's price per 1,000 on this plan and how often the provider finds the answer. We add \"misses billed\" when the provider charges for a miss. Some providers charge by the page. For those, we count the full pages that hold 1,000 results at the largest page size. We write \"page size not stated\" when the provider doesn't say how many results a page holds. The router publishes how often each provider finds an answer over all the router's calls. We assume each provider finds answers at that same rate on the calls the earlier providers miss. We leave the Waterfall column blank on calls with a single provider. In the JSON, each step has these keys. provider is the provider's name. call is the provider's call, which you can also make alone. perThousand, per and resultsPerPage mean the same as on a plan's row. hitRate is from 0 to 1, or null when the router gives none. missesBilled is true when the provider charges for a miss.","repeatFree":"On a call that costs units: how long you can get a paid review again for free. On a flat fee with a call limit, the time before the same review counts toward the limit again. We copy the time from the provider's pages, like \"20 minutes\". \"no limit\" means the provider never charges again for a review you paid for once. \"never\" means the provider charges each time you get the review again. Blank when the provider's pages don't say.","resultsCap":"For a search API: the most results one search gets on this plan, however many pages you ask for. \"no limit\" when the provider says you can get every match. Blank (null in the JSON) when the provider's docs don't say, or when the API isn't a search.","startPerCall":"A fee in dollars you pay once for each call, on top of the price per review. An Apify Actor's start fee is one. You pay the same fee for a call of 1,000 reviews or a call of one review. On a plan that charges by the call, each call asks for one review. On that plan, the $ per 1,000, List $ per 1,000, Overage and Enough for columns all count the Start fee. On a plan that charges by the result or the page, a call can return any number of results. On those plans, the $ per 1,000, List $ per 1,000, Overage and Enough for columns leave the Start fee out. The Start fee is $0.00 on a free plan, and blank when the plan has no start fee. A provider's page can give a range, like \"2-3 credits\". startPerCall then holds the lowest fee and startPerCallMax holds the highest. The sheet and the CSV show \"$0.04 to $0.06\". startPerCallMax is blank on a plan with one start fee or none.","monthlyFee":"A monthly fee the call needs. The provider takes the fee from the plan's units. For example, RouterGrowth charges $9.625 a month for each LinkedIn account you connect. monthlyFee is the fee in dollars. monthlyFeePer is what one fee pays for, like \"LinkedIn account\". The Enough for and $ per 1,000 columns count what is left after one month of the fee. Blank (null in the JSON) when the call has no monthly fee.","extras":"Fields that cost more than the row's price. Each group of extra fields has fields and perThousand. perThousand is the price you pay on top of the row's price. Some providers charge for each search and also for the extra fields on each result. For those providers, perThousand is the price for 1,000 searches. We assume each search returns the most results the plan allows.","Also pays for":"The other calls you get for the plan's price. The other calls each have a separate limit. We use the provider's words. When a plan pays for more than 40 other calls, we write their count instead, like \"300 other calls\". We leave out apps, extensions, MCP servers, proxies and storage, since they are not calls. We also leave out features you can use only in the provider's app, like sending the provider's email campaigns. For example, gtm-api.com's account price also buys 100 searches, 50 messages and 25 connection requests a day. \"nothing\" when you get only the row's call. The row's $ per 1,000 is for that call alone, since providers don't say how to split their price. Blank (null in the JSON) until we read the provider's plan. Also blank on a \"contact\" plan whose pages don't say what the price buys.","overagePerThousand":"On a subscription: dollars for each 1,000 reviews you get past the plan's units, when the provider sells extra reviews. On a plan that charges by the call, Overage includes the Start fee.","unitsCap":"\"hard\" means calls stop once the plan's units run out. \"soft\" means calls go on after the plan's units run out. Those calls cost the Overage price when the provider gives one. Blank (null in the JSON) when the provider's pages don't say.","addons":"On an email API's subscription: the packs of units the provider sells on top of the plan. We read them on the pricing page. Each pack has units and pay, in the plan's currency. renews is \"month\" or \"year\" when you pay for the pack again with the plan. renews is \"never\" when you buy the pack once. perThousand is dollars for 1,000 emails at the pack's price. The sheet's CSV says \"500 credits a month for $10 ($20.00 per 1,000)\". An empty list when the provider sells none. Blank (null) on every other plan.","catchAllPerThousand":"On an email API: dollars for 1,000 calls that return an address at a catch-all domain. Such a domain takes mail for any address. So you can't check whether the person's mailbox exists, and the email may bounce. 0 when such calls cost nothing, or when the provider returns no such address. The same as the row's $ per 1,000 when the provider charges for any address found. Blank when the provider's pages don't say.","bounceRefund":"On an email API: the credit or refund the provider gives when a paid address bounces. Also the conditions, in the provider's words, like \"the credit, reported from the dashboard or the API and reviewed\". \"never\" when the provider's pages say a bounced address stays charged. Blank when the pages don't say.","pitch":"How the provider sells the row's call, quoted from the call's own page. When one page covers all the provider's calls, we quote the provider's own pitch. \"[...]\" marks a cut.","freshness":"How old the answer may be, from the provider's pages. \"live\": the provider gets the data at the moment you call. The provider reads sources like LinkedIn, company websites, job boards, search results, keyword data or a page you send. Or the provider finds or checks an email or phone number at the moment you call. Some providers keep each answer for an hour or less. They give the same answer to anyone who asks the same question in that time. We call such a plan \"live\" too. Renidly keeps each answer for 20 minutes. \"1 month\" or \"30 days\": the provider answers from a copy refreshed that often. \"as of 2025-11-13\": from a copy last refreshed that day. \"stored\": from a copy the provider's pages don't date. Some email or phone checks read only the format, the domain's DNS and the provider's own lists. We mark those checks \"stored\" too. Such a check never asks the mail server or the carrier. Freshness is blank (null in the JSON) when the provider's pages don't say how fresh the answer is. Freshness is also blank when the pages don't agree with each other. A plan whose Freshness says a copy is on the API's sheet, beside the plans that read live. In brackets, we list the fields whose freshness differs on the provider's pages. fieldFreshness gives the freshness of each of those fields. Bright Data's LinkedIn profile is \"live (current title, jobs, schools: as of 2025-11-13)\". LinkedIn put those three behind a login wall, so Bright Data serves them from a cache.","history":"How far back the answers reach, on an API whose answers are dated. A company's funding rounds and open jobs are dated. \"since 2016\": back to 2016. \"open only\": only what is open now. \"the last 7 days\": a window that ends today. \"no limit\": every one ever. \", closed only\" after a value: the closed ones alone. Blank (null in the JSON) when the provider's pages don't say, or when the answers aren't dated.","countries":"On Validate phone, the countries whose numbers the call checks, like \"United States\". We take them from the provider's pages. \"Worldwide\": the call checks numbers from any country, or from over 100 countries. Blank (null in the JSON) until we read the countries on the provider's pages. Also blank when the provider's pages don't list the countries. Always blank on every other API.","fullFamilyTree":"On Company hierarchy, this column says whether one call gives the whole family tree. The whole tree runs from the top parent down each branch. \"yes\" (true in the JSON): one call gives the whole tree, counting every page of results the call returns. \"no\" (false): one call gives part of the tree, like the parents or one level of subsidiaries. You call again for each company to get the rest. The column is blank (null in the JSON) until we read the provider's website. The column is also blank when the provider's website doesn't say. Always blank on every other API.","checks":"This column lists the checks each call makes, as the provider's pages describe them. You find this column on the Validate email and Validate phone sheets. On Find email, the column lists the checks a finder makes on an address before giving you the address. A finder that asks the mail server takes longer than a finder that doesn't. On an email, \"format\": the address is well formed. \"mail servers\": the domain has servers that take mail. \"disposable domains\": the call spots a domain on a list of throwaway domains. \"role addresses\": the call spots a shared address, like sales@. \"mailbox\": the call checks with the mail server that the mailbox exists. On a number, \"numbering plan\": the number fits the rules of the number's country. \"carrier\": the call finds the carrier the number is with today. If the owner moved the number to a new carrier, you see the new carrier. \"line in service\": the call checks with the network that the line is live. \"messaging apps\": the call checks with a messaging app, like WhatsApp, that the number has an account there. A call without \"mailbox\" doesn't check the mailbox. Such a call can pass an address that bounces. The column is blank (null in the JSON) until we read the provider's pages. Also blank when the provider's pages don't say. Always blank on every other API.","searchesIn":"This column says where the call looks for posts. We read where the call looks on the provider's pages. You find this column on the LinkedIn post search sheet. \"LinkedIn's search\": the call runs LinkedIn's own search. \"Google's index\": the call searches Google for LinkedIn posts. Google sets how many posts the call can find. New posts show up only after Google indexes them. \"a search engine's index\": the call searches another search engine for LinkedIn posts. We also mark a call \"a search engine's index\" when the provider's pages don't name the search engine. \"the provider's own database\": the call searches a copy of LinkedIn posts the provider keeps. We leave the column blank (null in the JSON) when the provider's pages don't say. We leave the column blank for every other API.","keep":"How long the provider's terms let you keep the API's answers. \"no limit\" when the terms set none. \"no API terms\" when the provider has no API terms.","use":"What the provider's terms let you use the API's answers for. Also what the terms ask in return, like a link back or a credit. \"any\" when the terms limit nothing and ask nothing. \"no API terms\" when the provider has no API terms.","pay":"The plan's price, in the plan's currency. On a subscription, the price covers the months in termMonths. In the sheet's CSV, we write the months after the price. Some examples: \"$39.00/month\", \"€99.00/month\" on a plan in euros, or \"$468.00/15 months\" on gtm-api.com's yearly plan. A pack's Pay is the pack's price. A top-up's Pay is the smallest amount you can top up. On a top-up with no minimum from the provider, Pay is blank (null in the JSON). A free plan's Pay is $0.00. On a usage tier, Pay is what you pay each month for your calls below that tier. Each of those calls costs the price of the tier the call is in. Some tiers have a minimum. If your calls below the tier cost less than the minimum, you pay the minimum. When a usage tier sits on a subscription, you also pay the plan's price. Crawlbase has a tier for the next 10M requests. On that tier, Pay is $583: what you pay each month for your calls below the tier. On Mailgun's Foundation plan, you pay $95 a month for up to 5,000 validations. The $95 is the $35 plan plus $60 for the validations. On a pay-as-you-go plan, the sheet's Pay column shows Charged.","units":"What the plan gives for the price, counted in unit. On a usage tier, where the tier starts: \"from the 51st call a month\".","calls":"The number of reviews you get for the plan's price, counted in per. On a plan that charges by the page, calls and monthlyCap count pages. calls is the number of reviews the plan's units pay for: \"100 calls, once\" for a free trial, \"1,250 results a month\" for an allowance. On a plan that charges by the call, calls is the plan's units divided by the cost of one call. That cost includes the Start fee. A plan can limit calls per day or per month. Then calls is the most calls the limit allows before the units renew. The limit counts each call as one review. On a plan that charges by the page, the limit counts each call as one page. Say a plan allows 10,000 requests a month and 200 calls a day. You get 6,000 calls a month, because 30 days of 200 calls is 6,000. Some providers count each result toward the limit. A list you send in one call counts one result for each row. When a provider counts results, limitsCountedIn says \"result\", and calls and monthlyCap count results. A limit of 2,000 results a day allows 60,000 results in a month of 30 days. We fill monthlyCap when a call costs 0 units, like a call on a flat fee. monthlyCap is the most reviews you get a month, or \"no limit\". On a plan with a daily or monthly limit, monthlyCap is the most calls in 30 days. 3,000 calls a day make 90,000. The Enough for column shows 3,000 calls a day as \"90,000 calls a month\". Any plan can limit calls per hour, minute or second. calls and monthlyCap also hold the most calls a limit per hour, minute or second allows. A limit of 50 calls an hour allows 36,000 calls in 30 days. We count a call limit in monthlyCap only when each call returns one review or a fixed-size page. On a free trial shorter than 30 days, monthlyCap is the most calls you get over the whole trial. The trial's calls never renew. A 7-day trial with 1,000 calls a day shows as \"7,000 calls, once\". Enough for shows calls, or monthlyCap when a row has no calls. On a plan with a Monthly fee, the provider first takes one month's fee from the plan's units. calls counts the calls left after the fee. We count the calls again each time the provider refills the plan's units. Enough for says \"0 calls left after the monthly fee\" when the fee uses up all the plan's units. Enough for is blank when the provider doesn't say how many reviews you get. Enough for is also blank on pay as you go plans and on top-ups. Enough for is blank too on subscriptions that charge for each review on top of the fee. Enough for is also blank when a waterfall's average call costs nothing. calls and monthlyCap are null when Enough for is blank.","expires":"When the units you don't use lapse, in the provider's words: \"never\", \"365 days\", \"at renewal: unused credits do not carry over\". Blank when the provider's pages don't say.","perDay":"The most calls a day. Some providers count each result of a call instead, like each row of a list. limitsCountedIn says what the provider counts: \"call\", \"result\" or \"page\". The provider counts the same unit for this column and for the plan's monthly limit. limitsCountedIn says \"call\" when the provider's docs don't say.","perSecond":"The most calls a second you can keep up. When the provider counts a limit over a longer window, we divide the limit. We divide a limit per minute by 60, per 5 minutes by 300, per hour by 3,600. When the provider sets several limits, we show the tightest: 25 a second and 40 a minute is 0.67. We round to two decimals. A rate under 0.1 keeps two digits past the zeros: 5 an hour is 0.0014.","concurrent":"The most calls running at once, or \"no limit\". \"n/a\" when the provider sets no cap on calls at once but limits calls by the second. Then Per second sets your limit. Blank (null) when the provider's pages don't say.","batch":"The most products in one call on this plan. 1 when the call takes one at a time. \"no limit\" when the provider says a call takes any number. Blank (null) when a call takes a list and the provider's pages don't say how many. A call that refuses fewer than a set number shows the fewest and the most, like \"2,000 to 2,000,000\". A call that needs at least 2,000 and has no top limit shows \"2,000 or more\". A call that needs at least 2,000 shows \"at least 2,000\" when the provider's pages don't give the top limit.","answer":"The way you get the call's answer. \"in the call\" when the call's response holds the answer. \"by polling or webhook\" when the call returns a job. Once the job is done, you get the answer from another call or at your webhook. \"in the call or by polling\" when the call returns the answer if the answer is ready in time. If the answer isn't ready, the call returns a job you check later. An Apify Actor returns a job when the run goes past 5 minutes. \"in the call or by webhook\" when you choose in your request. \"by polling\" when only another call gets the answer. \"by webhook\" when only a URL you give gets the answer. Blank (null) when the provider's pages don't say.","latencyMs":"The median time a call takes. For a benchmarked call, we show our benchmark's median. The API's benchmark columns show the same median. From each call's time, we subtract the mean time of three free calls to the same provider, made just before. If that mean is longer than the call, we use the provider's median baseline instead. We cap the baseline at the call's time, so no time is below zero. For a call we didn't benchmark, we show the time from the provider's pages. Or we show a time we measured when we added the row. On a plan without a check or feature of the benchmarked plan, we show the provider's time or our own. We leave the median blank (null) when we have no time. We also leave the median blank when the benchmarked call gave no answer we could time. The JSON and datacircle.csv give the time in milliseconds. The sheet and the sheet's CSV give the time in seconds.","send":"What you give the call: a product's Capterra URL. The call needs the inputs before \"Optional:\". The optional ones come after \"Optional:\", or after a semicolon in the CSV and the JSON.","method":"The call's HTTP method.","path":"We give the path from the provider's docs. When that path fails, we give the path that works. Each plan of a call has the same path. A plan the provider serves at a separate address has a separate path.","plan":"The plan's name on the provider's pricing page.","who":"Who the provider offers the plan to: \"anyone\", or the condition the provider's pages set, like \"anyone with a work email\" or \"on approval of an application\".","readFrom":"The pages we read the row's values from. They are the sheet's last column: click a cell to see each page, or press ⌘C to copy them all."},"billed":{"free":"Free: nothing to pay","on-demand":"Nothing to buy first: you pay as you go","one-time":"You buy any amount of credit first, then spend the credit on calls","contact":"No public price: you ask the provider for one","monthly":"A monthly subscription","quarterly":"A quarterly subscription","half-yearly":"A subscription for 6 months","yearly":"A yearly subscription"},"defaults":["No contact us plans","No free plans","No yearly plans","$500 or less to start"],"kept":1,"paid":{"ranked":{"Capterra reviews":[0.2,0.2353,0.2857,0.3429,0.8]},"bench":{}},"alert":true,"more":"/assets/sheet-TI_Tc1dO.json"}