Check Endpoint
Verify whether two technologies are compatible before committing to your tech stack.Endpoint
Request
Headers
| Header | Type | Required | Description |
|---|---|---|---|
Content-Type | string | Yes | Must be application/json |
Body
| Field | Type | Required | Description |
|---|---|---|---|
techA | string | Yes | First technology name |
techB | string | Yes | Second technology name |
Example Request
Response
Success Response (200)
Response Fields
| Field | Type | Description | |
|---|---|---|---|
version | string | API version (always “1.0”) | |
status | string | compatible, partial, incompatible, deprecated, unknown | |
severity | string | info, warning, error, critical (optional) | |
message | string | Human-readable compatibility description | |
workaround | string | null | Suggested fix for issues |
docsUrl | string | URL to full compatibility documentation | |
lastUpdated | string | ISO 8601 timestamp of last data update |
Status Values
| Status | Meaning |
|---|---|
compatible | Works seamlessly |
partial | Works with limitations or configuration |
incompatible | Fundamental conflicts exist |
deprecated | One or both technologies are end-of-life |
unknown | No compatibility data available |
Code Examples
cURL
JavaScript (fetch)
JavaScript (axios)
Python (requests)
Go
Example Responses
Compatible
Partial with Workaround
Incompatible
Unknown
Error Responses
400 Bad Request
429 Rate Limit Exceeded
Rate Limiting
- Limit: 60 requests per minute
- Headers:
X-RateLimit-Remaining,X-RateLimit-Reset
What’s Next
- Scan Endpoint - Analyze complete projects
- Badge Endpoint - Generate badges
- Errors - Error handling guide
Try it now: Interactive API Demo →