Karybase API

Start using the public Karybase API with organization API keys.

The Karybase API exposes selected organization and inventory data for external integrations.

Choose the interface you want to use:

API Origin

Public HTTP requests use the Karybase API origin:

https://api.karybase.com

The docs site runs on https://docs.karybase.com; API requests go to https://api.karybase.com.

Current HTTP Surface

AreaEndpointAuthentication
HealthGET /api/v1/healthNo API key
API key verificationGET /api/v1/auth/verifyAPI key
Organization summaryGET /api/v1/organizationAPI key
Inventory item listGET /api/v1/inventory/itemsAPI key with inventory view access
Inventory item detailGET /api/v1/inventory/itemAPI key with inventory view access

Request Format

Send API keys using either header:

x-api-key: kb_live_...
Authorization: Bearer kb_live_...

JSON responses use Content-Type: application/json. Browser clients may call the public API because the HTTP handlers allow authorization, content-type, and x-api-key headers.

Key Types

Karybase supports organization API keys and user API keys.

API keys are scoped to their organization. Organization-scoped endpoints resolve the organization from the key, so new clients do not need an organizationId query parameter.

Example

curl "https://api.karybase.com/api/v1/inventory/items?limit=25" \
  -H "Authorization: Bearer $KARYBASE_API_KEY"
const items = await karybase.inventory.list({ limit: 25 });

Status Codes

StatusMeaning
200Request succeeded
400Required query parameter is missing or malformed
401API key is missing, invalid, disabled, expired, exhausted, or rate limited
403API key is valid but cannot access the requested organization
404Requested organization or inventory item was not found

On this page