Open Source Licenses API
Overview
To use Open Source Licenses, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/openlicensesExample
How to call the Open Source Licenses API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/openlicenses?name=MIT" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/openlicenses?name=MIT', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/openlicenses?name=MIT', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/openlicenses?name=MIT", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"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"
]
}
}Authentication
The Open Source Licenses API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Open Source Licenses API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Open Source Licenses API:
Get Open Source Licenses Information
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
name | string | required | The name of the open source license to get information about | - |
Response
The Open Source Licenses API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<domain_content>false</domain_content>
<domain_data>false</domain_data>
<domain_software>true</domain_software>
<legacy_ids>
<legacy_id>mit-license</legacy_id>
</legacy_ids>
<license>MIT</license>
<name>MIT License</name>
<license_url>https://opensource.org/licenses/MIT</license_url>
<license_status>active</license_status>
<isOsiApproved>true</isOsiApproved>
<compatibleDomains>
<compatibleDomain>software</compatibleDomain>
</compatibleDomains>
</data>
</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
| key | value |
|---|---|
| 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 Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
domain_content | boolean | - | |
domain_data | boolean | - | |
domain_software | boolean | - | |
legacy_ids | array | - | |
license | string | - | |
name | string | - | |
license_url | string | - | |
license_status | string | - | |
isOsiApproved | boolean | Whether the license is OSI approved | |
compatibleDomainsPremium | array | List of compatible domains (software, content, data) |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Open Source Licenses through GraphQL to combine it with other API calls in a single request. Query only the open source licenses data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
openlicenses(
input: {
name: "MIT"
}
) {
domain_content
domain_data
domain_software
legacy_ids
license
name
license_url
license_status
isOsiApproved
compatibleDomains
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Open Source Licenses API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Open Source Licenses requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Open Source Licenses API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Open Source Licenses
Official Open Source Licenses packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Open Source Licenses works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Open Source Licenses?
How many credits does Open Source Licenses cost?
Each successful Open Source Licenses API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful open source licenses lookups.
Can I use Open Source Licenses in production?
The free plan is for testing and development only. For production use of Open Source Licenses, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Open Source Licenses from a browser?
What happens if I exceed my Open Source Licenses credit limit?
When you reach your monthly credit limit, Open Source Licenses API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








