Docs/APIs/Open Source Licenses

Open Source Licenses

Get information on open source licenses

OperationalCredits 2 per callp50 281msData LookupStar

Overview

Pass any license name or identifier to retrieve its official metadata. The API checks the record and returns the full name, canonical URL, SPDX ID, legacy identifiers, and whether it is active, retired, or superseded. It also flags applicability across software, content, or data domains, with paid plans adding compatible domain details.

Live Test Open Source Licenses API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/openlicenses
curl "https://api.apiverve.com/v1/openlicenses?name=MIT" \
  -H "x-api-key: your_api_key_here"

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
nameRequiredstringThe name of the open source license to get information about

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "domain_content": false,
    "domain_data": false,
    "domain_software": true,
    "legacy_ids": [
      "mit-license"
    ],
    "license": "MIT",
    "name": "MIT License",
    "license_url": "https://opensource.org/licenses/MIT",
    "license_status": "active",
    "isOsiApproved": true,
    "compatibleDomains": [
      "software"
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
domain_contentbooleanfalseWhether the licence is intended for content
domain_databooleanfalseWhether the licence is intended for data
domain_softwarebooleantrueWhether the licence is intended for software
legacy_idsarray[mit-license]Older identifiers this licence has been known by
licensestring"MIT"SPDX identifier of the licence
namestring"MIT License"Full name of the licence
license_urlstring"https://opensource.org/licenses/MIT"Canonical URL of the licence text
license_statusstring"active"Whether the licence is active, retired or superseded
isOsiApprovedbooleantrueWhether the license is OSI approved
compatibleDomainsPremiumarray[software]List of compatible domains (software, content, data)

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

Dependency Compliance Auditing
CI pipelines check third-party package licenses against OSI approval and active status flags before merging pull requests.
SBOM Metadata Enrichment
Software asset managers match SPDX identifiers and canonical URLs to internal components when assembling software bills of materials.
Package Registry Verification
When developers publish a package, code repositories verify that declared license names map to active SPDX IDs.
Dataset Ingestion Governance
Flag datasets governed by retired licenses or terms not meant for data before ingesting them into analytics environments.

Other ways to use Open Source Licenses

Set up Open Source Licenses on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

More in Data Lookup:

Was this page helpful?