Email list of companies using Salt Security API
Reach application security and CISO-level leaders using Salt Security for API discovery, posture governance and threat protection.
Free Salt Security API count + 10 sample records
4,003+ companies · 18,092+ contacts available
- ✓Exact count for your titles, regions and company size
- ✓10 verified sample records to check quality
- ✓Price quote within 1 business day
Trusted by B2B and enterprise revenue teams
How many companies use Salt Security API?
Data InfoMetrix tracks 4,003+ companies running Salt Security API as of October 2026, with 18,092+ verified contacts at those accounts. The largest groups are Financial Services, Insurance and Retail. Buying decisions usually sit with the CISO, VP of Engineering and Head of Application Security. Counts are estimates built from technology footprint scans, job-post signals and partner directories, checked by our research team. How we count
Organizations detected running Salt Security API.
Direct emails and phone dials for decision-makers.
Full buying committee mapped.
SMTP-verified, with 1:1 replacement of any email that hard bounces within 30 days.
| Technology category | Cybersecurity |
|---|---|
| Tracked organizations | 4,003+ verified accounts worldwide |
| Decision-maker contacts | 18,092+ records with emails, mobile and direct dials |
| Key roles | Head of Application Security, CISO, Director of API Platform, platform administrators, IT directors, procurement |
| Geography | 180+ countries · country-by-country counts on request |
| Verification | DNS and script telemetry, 5-stage SMTP handshake, manual research |
| Refresh cadence | Continuous, 30–45 day maximum record age at delivery |
| Compliance | GDPR, CAN-SPAM, CCPA and CASL |
| Delivery | 24–48 hours as CSV, XLSX or CRM API |
Researched by the Data InfoMetrix research team. Counts updated October 2026.
How we count and verify dataSee 10 records first
Matched to your ICP filters, free.
Size your Salt Security API audience
Pick a region, company size and buying role to estimate how many accounts and contacts you can reach.
Estimates from our current Salt Security API dataset. Exact counts come with your quote.
Reach the whole buying committee
A Salt Security API account is not one contact. We map the people who evaluate, buy, run and use it across API Security & Posture Governance.
These are examples. We build records for any department, seniority or custom title.
See exactly what you get
Every record carries 60+ fields, from verified email, direct dial and LinkedIn to full postal address, Salt Security API edition, coexisting stack and intent.
We deliver 60+ data fields per record, including intent data. The sample shows a selection only. Tell us which fields you need, including any that aren't listed here, and we'll add them to your list.
How we prove an account runs Salt Security API
No scraped résumés or stale directories. Three layers confirm a live installation before a contact reaches your list. Read our verification protocol
Live DNS & script signals
We inspect response headers, DNS MX and CNAME records and live JavaScript bundles to confirm a running Salt Security API instance.
DNS · CNAME · MX recordsHTTP headers · JS bundles✓ Verified against live infrastructure90-day hiring signals
We track job requisitions that ask for Salt Security API skills, which shows ongoing budget and headcount.
Pre-delivery SMTP handshake
Each email is tested against the destination mail server, and titles are checked against current company rosters.
Maximum bounce rate, or we replace the contacts. Your sender reputation stays clean.
Every email that hard-bounces within 30 days of delivery is replaced free, record for record.
Live SMTP and MX checks right before we send your file.
Clean CSV or XLSX, ready for one-click import.
What are you trying to do?
Each campaign needs a different data strategy. Pick your goal to see how we build the audience.
Find companies on rival platforms and reach the people evaluating a move to, or away from, Salt Security API.
Conquesting playbookPitch integrations, add-ons and complementary tools to companies already running Salt Security API.
Ecosystem playbookBuild account lists around Salt Security API deployment scale and engage the full committee across departments.
ABM playbookKnow the stack around every account
Salt Security API rarely runs alone. Every record is tagged with the tools detected alongside it, so you can segment by complementary stacks.
Open the coexistence matrixWhat Salt Security API customers look like
Anonymised profiles of companies in our Salt Security API dataset of 4,003+ accounts. Named accounts are shared in your free sample, never on a public page.
| Company size | Industry | Country | Employees | Revenue |
|---|---|---|---|---|
| Mid-market | Retail | United Kingdom | 200–999 | $50M–$250M |
| Enterprise | Telecommunications | United States | 5,000+ | $1B+ |
| Upper mid-market | Financial Services | Canada | 1,000–4,999 | $250M–$1B |
| SMB | Insurance | Germany | 50–199 | $10M–$50M |
| Enterprise | Retail | United States | 10,000+ | $5B+ |
| Mid-market | Telecommunications | Australia | 500–999 | $100M–$250M |
| Mid-market | Financial Services | United States | 200–999 | $50M–$250M |
| Enterprise | Insurance | United States | 5,000+ | $1B+ |
Plus 170 more countries. Ask for a country-by-country count of Salt Security API accounts and we'll include it with your free sample.
Build the list your way
Every list is assembled from source to your product tier, job function, geography and revenue band. Nothing is a fixed export.
Filter by what they actually run.
Match revenue, size and industry.
Target any territory.
What Salt Security API teams are struggling with
Know the friction before you reach out, and position your product where it matters.
API attacks bypass WAFs
Posture drift
AI agents calling APIs
“Instead of waiting at a booth hoping for foot traffic, our reps arrived at the summit with a fully booked calendar of qualified buying committees. It transformed our event ROI.”
Salt Security API list questions, answered
How many companies use Salt Security API?
Data InfoMetrix tracks 4,003 companies using Salt Security API, with 18,092 verified contacts at those accounts as of October 2026. The largest groups are Financial Services, Insurance and Retail. Counts are estimates from our database and market research, so ask us for a live count for your exact criteria.
Who buys and manages Salt Security API inside a company?
Salt Security API is usually owned by API Security & Posture Governance. Decision-makers include CISO, VP of Engineering and Head of Application Security; AppSec Engineering Manager and DevSecOps Lead shape the choice, and Software Engineers and AppSec Engineers use it day to day. Our Salt Security API list can include any of these roles.
Which Salt Security API products or editions can I target?
You can target accounts by the Salt Security API products they run, including Salt API Discovery, Salt Posture Governance, Salt Threat Protection, Salt Illuminate and Salt AI Agent Security. Tell us which edition or module matters and we filter the list to those accounts.
What other software do Salt Security API customers use?
Salt Security API customers commonly also run AWS, Apigee, Kong, Splunk and GitHub. Salt Security API is often connected to AWS API Gateway, so users of those tools overlap heavily. We can filter any list by this kind of stack overlap.
What are the main alternatives to Salt Security API?
The main alternatives to Salt Security API are Noname (Akamai), Traceable and Cequence.
When are Salt Security API customers most likely to buy?
Buying triggers we track for Salt Security API accounts include API program expansion, breach involving APIs, AI agent rollout and New AppSec leader. A common pain point is API attacks bypass WAFs: logic abuse looks like normal traffic.
Can Data InfoMetrix deliver a free sample Salt Security contact list before ordering?
Yes. Data InfoMetrix delivers a complimentary 10-record sample tailored to your target Salt Security criteria—including target job titles, company size, and region—delivered within one business day with no obligation.
How does Data InfoMetrix guarantee email deliverability for Salt Security contacts?
Data InfoMetrix provides a 99% email deliverability guarantee on all Salt Security datasets. Every contact record undergoes real-time email verification within a 30 to 45-day refresh cycle, backed by a 1:1 hard bounce replacement policy for 30 days after delivery.
Sourcing and compliance. Business contacts come from public company sources, professional directories and opt-in publishing partners, then go through SMTP verification and human review. Lists are for B2B outreach: include an unsubscribe link and honour opt-outs (CAN-SPAM), and have a lawful basis such as legitimate interest when you email people in the EU or UK (GDPR). Read how we source and verify data
Get your Salt Security API users list
Tell us your titles, regions and company size. We'll send counts, a quote and a free 10-record sample.
Related lists
Alternatives to Salt Security API, tools its customers also run, and more Cybersecurity lists.

