Skip to content

API Overview & Authentication

The Skillett API is a REST API served over HTTPS. All requests require authentication via an API key. Responses are JSON.

https://api.skillett.dev

All API requests require a Bearer token in the Authorization header:

Terminal window
Authorization: Bearer sk_a1b2c3d4e5f6...

API keys are created on the Skillett dashboard or via the CLI after login.

Keys follow the format sk_ followed by a hex string. The first 8 characters after sk_ form the key prefix (visible in the dashboard). The full key is shown once at creation and cannot be retrieved again.

Keys can be scoped to specific integrations:

ScopeAccess
* (default)All integrations
githubOnly GitHub endpoints
github,gmailGitHub and Gmail only
  • Content-Type: application/json for POST/PATCH requests
  • Parameters: Passed in the JSON body under a params key for skill execution
  • Query strings: Used for pagination and filtering on list endpoints

Success:

{
"status": 200,
"data": { ... }
}

Error:

{
"error": "error_code",
"message": "Human and agent-readable description of the error.",
"action_url": "https://app.skillett.dev/..."
}
PlanRate limitDaily limit
Free30 req/min10,000/day
ProHigherHigher
UnlimitedHighestHighest

When rate limited, the API returns HTTP 429:

{
"error": "daily_limit_reached",
"message": "Daily API call limit reached (10000). Resets at midnight UTC.",
"action_url": "https://app.skillett.dev/billing"
}
MethodPathDescription
GET/v1/skillsList integrations
GET/v1/skills/:integrationList endpoints for integration
GET/v1/skills/:integration/:endpointEndpoint documentation
POST/v1/:integration/:endpointExecute an endpoint
POST/v1/connectStart integration connection
GET/v1/connect/:connectionIdPoll connection status
GET/v1/:slug/downloadDownload skill files
POST/auth/device/codeRequest device authorization code
POST/auth/device/authorizeAuthorize device code
POST/auth/device/tokenPoll for device token
GET/api-keysList API keys
POST/api-keysCreate API key
DELETE/api-keys/:idRevoke API key