cert/map API
The certification data as plain JSON: prices, levels, prerequisites, study plans and comparisons for 478 cybersecurity certifications. Free to use, no key, callable from a browser.
Open the entry point OpenAPI description
Endpoints
| URL | Returns |
|---|---|
/api/v1/index.json | Counts and the URL of every endpoint |
/api/v1/certs.json | Every certification, summarised: vendor, domain, level, price |
/api/v1/certs/{id}.json | One certification in full, with its study plan and comparisons |
/api/v1/vendors.json | Vendors and the ids of their certifications |
/api/v1/domains.json | Domains and the ids of their certifications |
/api/v1/comparisons.json | Pairs that have a comparison page, with the page in each language |
/api/v1/paths.json | Preset role paths with cost and study-time totals |
Example
Show the current exam price of a certification on your own page:
const res = await fetch("https://certmap.dev/api/v1/certs/oscp.json");
const { certification } = await res.json();
console.log(certification.acronym, certification.price_usd); // OSCP+ 1749
How it works
- It is static. The files are regenerated whenever the dataset changes, so there is nothing to query: fetch a file and filter it on your side.
- Cross-origin requests are allowed, so it works from client-side code on any site.
- Responses are cached for about ten minutes. Cache on your side too; see fair use below.
- URLs under
/api/v1/keep their shape. A breaking change would be published asv2. price_usdis the exam list price in US dollars:nullwhen the vendor does not publish one,0when it is free.price_verified_atis the date it was last seen on the vendor's page.
Fair use
The API is free and needs no key, which only works if it is used with some care. By using it you agree to the following.
- Cache what you fetch for at least 10 minutes. Do not call the API on every page view of your site.
- Stay under 60 requests a minute from one client or address.
- If you need the whole dataset, download certs.json or data/certs.json once. Do not walk the per-certification files.
- Automated clients identify themselves with a User-Agent that names the project and gives a contact URL or address.
- Credit cert/map with a visible link to https://certmap.dev/ wherever the data is shown (CC BY 4.0).
- Show price_verified_at next to a price, or tell readers to confirm with the vendor. Do not present the prices as live or authoritative.
- Do not suggest that cert/map or any listed vendor endorses your product.
- The API comes as it is, with no uptime or accuracy guarantee. Clients that ignore these terms can be limited or blocked.
Need more than this allows, or want to tell us what you are building? Write to contact@certmap.dev.
Licence and attribution
The data is published under CC BY 4.0. You can use it in any project, commercial or not, as long as you credit cert/map with a link to certmap.dev. Prices change without notice, so tell your readers to confirm with the vendor.
The whole dataset is also available as single files: certs.json, certs.csv, resources.csv and comparisons.csv.