API

How to use the Vexday API: free key and first CVE request

Create the free key, fetch a CVE as JSON with severity, active exploitation and the risk score, and keep an eye on the account limit. To bring Vexday's data into your system.

  • Who it's forFor developers, SOCs and anyone integrating Vexday into their own system.
  • PlanFree account; more volume on the plans
  • Timeabout 10 min

What you need

  • A Vexday account: just your email, no password and no card.
  • A terminal with curl or any HTTP client.

Account limits: free, 50 per day and 10 per minute · SOC, 5,000 per day and 60 per minute · MSSP, 20,000 per day and 120 per minute.

Step by step

  1. Create the key

    In the dashboard, open Integrations and click New key. Give it a name, such as the system that will use it, and copy the key right away: it starts with vx_live_ and is shown only once.

  2. Make the first request

    Request a CVE's detail with the key in the Authorization header. The lang parameter picks the language of the translated fields: pt, es or en.

    curl -s -H "Authorization: Bearer vx_live_SUA_CHAVE" \
      "https://api.vexday.io/api/v1/cve/CVE-2024-3400?lang=en"
  3. Read the response

    The record comes in data: severity (cvss_score), exploitation probability (epss_score), active exploitation (in_kev), public proof of concept (has_public_poc) and Vexday's risk score (risk). The attribution field carries the source credits: keep it when you show the data.

  4. Search for what matters to you

    Search filters by vendor, product, severity, active exploitation and public proof of concept, sorted by risk. The /kev view returns only what is under active exploitation.

    curl -s -H "Authorization: Bearer vx_live_SUA_CHAVE" \
      "https://api.vexday.io/api/v1/cve?vendor=fortinet&in_kev=true&page_size=20"
  5. Track your usage

    /status shows the plan, today's requests and how many are left. The limit belongs to the account, adding up its keys; past it, the API answers 429 with the Retry-After header.

    curl -s -H "Authorization: Bearer vx_live_SUA_CHAVE" "https://api.vexday.io/api/v1/status"

Something went wrong?

401: missing or invalid keyCheck that the header reads Authorization: Bearer vx_live_… and that the key was not revoked under Integrations.
404 on the CVE requestThe ID is misspelled or the CVE is not in the database yet. The format is CVE, the year and the number, separated by hyphens.
429: limit reachedWait for the Retry-After time. For more volume, the SOC and MSSP plans raise the daily and per-minute limits.

Frequently asked questions

Is the key really free?

Yes. The free account already creates the key, with a lower daily limit. The paid plans raise the volume.

Is there an OpenAPI spec?

Yes, at https://api.vexday.io/openapi.json. The interactive docs, to try each endpoint in the browser, are at https://api.vexday.io/docs.

How do I sync changes without downloading everything again?

With /changes: it lists what changed since a date. Then /cve/batch returns the detail of several CVEs in one call.

Keep going