Firmable API FAQs
Get answers to common questions about the Firmable API.
What endpoints does the API support?
The API has four endpoints:
- Company enrichment: look up a known company record using a Firmable ID, ABN, website, FQDN, LinkedIn URL, or LinkedIn slug
- People enrichment: look up a known person record
- People search: search for people at a known company using a Firmable company ID
- Filter options: list the values you can use in people search filters, such as seniority and department (doesn't use credits)
There is no company search endpoint. Open-ended company discovery needs to be done in the platform.
Can I search for companies via the API?
No. There is no company search endpoint. The API only supports company enrichment, meaning you can look up a known company if you already have an identifier such as an ABN, domain, or LinkedIn URL. To discover companies that match an ICP, use the Search page in the platform.
Can I search by company name only?
No. The company enrichment endpoint requires at least one of the following: Firmable ID, ABN, website, FQDN, LinkedIn URL, or LinkedIn slug. A free-text company name is not a valid input. If only company names are available, the recommended workaround is to generate website domains from those names first, then run the API.
What inputs does the people search endpoint require?
A Firmable companyId is mandatory. People search is not a standalone prospecting tool. The typical workflow is:
- Run company enrichment with an ABN, domain, or LinkedIn URL to retrieve the Firmable company ID.
- Use that ID with the people search endpoint to find contacts at that company.
How granular are the people search filters?
The available filters are department, seniority, position and country (selectedCountry, which defaults to AU), plus pagination (from/size). There is no state or suburb filter and no multi-company search. For more granular filtering, use the Search page in the platform.
Can I do bulk or batch enrichment via the API?
No batch endpoint exists. Each request enriches one record at a time. The rate limit is 50 requests per second, meaning enriching 5,000 records takes roughly 100 seconds in a loop. For bulk enrichment without code, uploading a CSV to Data exchange (Small Teams and above, up to 5,000 rows and 2.5 MB) is the better path.
How does credit consumption work?
One credit is charged per record enriched, the first time only. Re-enriching an already-unlocked record is free, whether done via the platform or the API.
Can I get a trial API key?
Yes. Sign up for a free trial and the team can activate an API key within that trial. Reach out to your sales representative to get this set up. API access is available on the Enterprise plan. If you're on an Individual, Small Teams or Teams Pro plan and would like API access, contact your sales representative.
Is the API compatible with tools like Zapier, Make, or n8n?
Yes, via HTTP request nodes. There are no technical blockers. For customers wanting to push data to a tool like Supabase, webhooks are often the simpler path unless programmatic enrichment logic is specifically required.