Sales Legends Sales Jobs
Search open sales jobs with posted pay, and look up posted pay and H-1B sponsorship data by kind of sales role. Free, no key. Remote server.
Hosted MCP Server
npx add-mcp 'https://saleslegends.co/api/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
Sales hiring, as data
What sits behind Sales Legends: today's open sales roles counted by kind of work and by company, and the pay their postings state. Files go to your work email, cut from the same reads of each company's careers system that refresh the board every hour.
The files
Three files from the latest read
The files are built from the same read of employers' hiring systems as the pages, so a figure in a file matches the figure on screen. Ask for them above and one email brings all three links.
Open sales roles
/roles.json
The size of the sales market this hour: openings counted for each kind of sales role and each employer, with the openings new in the last 7 days set beside each recent week's. Counts only; it never lists single postings.
name, description
What the file contains, in a sentence.
source
The page here that shows the same numbers.
license
CC BY 4.0.
measurement_technique
How each number is counted.
updated
When the employers' hiring systems were last read (ISO 8601, UTC).
temporal_coverage
The day the numbers describe (YYYY-MM-DD). Cite it with any number you use.
totals.open_roles
Sales openings across every employer we read.
totals.platforms_live
Employers hiring now: those we read that have at least one sales opening up (the employer directory's hiring-now count).
totals.new_last_7d
Openings up today that our reads first found in the last 7 days (the 7 UTC days up to today).
recent_market_momentum.weekly[]
A row for each recent ISO week (week_start and the new_roles found in it), followed by the average over those weeks.
open_by_work_type[]
slug, label and open_count for each kind of sales role, with the pay fields below where at least three employers post pay for it (null where fewer do).
open_by_platform[]
slug, name and open_count per employer.
Posted base and OTE by kind of role
/pay.json
The yearly pay that sales postings state, for each kind of role where three or more employers publish a figure, so one employer's range never passes for the market.
name, description
What the file contains, in a sentence.
source
The page here that shows the same numbers.
license
CC BY 4.0.
measurement_technique
How each number is counted.
updated
When the employers' hiring systems were last read (ISO 8601, UTC).
temporal_coverage
The day the numbers describe (YYYY-MM-DD). Cite it with any number you use.
pay_by_work_type[].slug, label
The kind of sales role (SDRs, account executives or sales managers, for example).
currency, unit
USD a year: the base salary, or the OTE when that is the figure a posting states.
median
The median of the posted yearly figures.
typical_low, typical_high
The typical band, which runs from the 25th percentile of posted range midpoints up to the 90th percentile of the ranges' upper ends, every figure taken as a year's pay (an hourly rate times 2,080 hours).
rate_samples
The number of distinct pay figures measured, reposted openings left out.
platforms
The number of employers those figures come from.
open_total, unpriced
open_total is the kind's openings up now; unpriced is how many of them post no pay.
The pay table in CSV
/pay.csv
The rows of /pay.json as a dated CSV file that opens in Excel or Google Sheets.
For developers
Fetch them from code
A program can fetch all three files over HTTPS with no key, from any origin. If you open one of those addresses in a browser tab you land on this page instead, where you can ask for the files by email.
curl https://saleslegends.co/roles.json
const res = await fetch("https://saleslegends.co/pay.json");
const { pay_by_work_type } = await res.json();
Individual open roles are not in those three files. They are in the open jobs API, GET https://saleslegends.co/api/v1/jobs: JSON, no key, up to 50 roles a page, filtered by q, kind, platform, country, min_pay_usd and since, and paged with limit and offset. Each role links to the employer's own posting. It is described in openapi.json. There is no CSV of open roles.
For investors
Hiring radar
The records under every number on this page: each sales role at every company we read since the first read, with its pay, kind of sales work, countries and the days it opened and closed, each company day by day, and a log of every change, sent as files each day. See what is inside and the record counts.
For AI assistants
Let Claude or ChatGPT search sales roles
The same data is served by a remote MCP server. An assistant can look up open sales roles and the pay they post, and each role it brings back links to its page here, where the application begins.
Server address (Streamable HTTP transport)
https://saleslegends.co/api/mcp
search_sales_jobs
Open sales roles filtered by keywords, kind of work, company, country or a pay floor, each returned with its stated pay and an apply link.
get_sales_pay
Salary midpoints and the usual low-to-high band per kind of sales work, mirroring /pay.json.
get_sales_market
Open-role counts by kind of sales work and by company, for one country if you name it (what /roles.json returns).
get_hiring_radar
Sales hiring data for investors
Inside Claude it goes in as a custom connector (Settings, Connectors). For Cursor, VS Code, Claude Code or any client set up through a JSON file, paste:
{
"mcpServers": {
"sales-legends": { "url": "https://saleslegends.co/api/mcp" }
}
}
Terms
Free to reuse, with credit
- License: CC BY 4.0, so republish or chart it as you like. Attribute it to Sales Legends with a link to the sales pay report and quote the temporal_coverage day next to any number you use.
- A copy to cite: the posted-pay table and the H-1B, H-1B1, E-3 and green card sponsorship table of 2026-11-20 are also published as a dated copy under the same license, with the permanent DOI 10.5281/zenodo.24392229 on Zenodo and on Hugging Face. Cite the copy when you need a version that never changes, and this page for today's figures; the files here are re-read every hour.
- Access: a person gets them by email, at a company address; a script fetches them straight over HTTPS, keyless and cross-origin. Machine-readable spec: /openapi.json.
- Freshness: each company's careers system is re-read every hour, and polling faster brings back identical numbers, so holding a copy for up to an hour loses nothing.
- Method: which postings count, which are left out and why a pay figure needs three companies behind it are set out in our methodology.
Need it by country, employer or kind of role, over a longer period, or opening by opening?