bknd-custom-endpoint
Use when creating custom API endpoints in Bknd. Covers HTTP triggers with Flows, plugin routes via onServerInit, request/response handling, sync vs async modes, accessing request data, and returning custom responses.
npx skills add majiayu000/claude-skill-registry --skill bknd-custom-endpoint --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Custom Endpoint Create custom API endpoints beyond Bknd's auto-generated CRUD routes. ## Prerequisites - Running Bknd instance - Basic understanding of HTTP methods and REST APIs - Familiarity with TypeScript/JavaScript ## When to Use UI Mode Custom endpoints require code configuration. No UI approach available. ## When to Use Code Mode - Creating webhooks for external services - Building custom business logic endpoints - Adding endpoints that combine multiple operations - Integrating with third-party APIs - Creating public endpoints without entity CRUD ## Two Approaches Bknd offers two ways to create custom endpoints: | Approach | Best For | Complexity | |----------|----------|------------| | **Flows + HTTP Triggers** | Business logic, webhooks, multi-step processes | Medium | | **Plugin Routes** | Simple endpoints, middleware, direct Hono access | Low | ## Approach 1: Flows with HTTP Triggers ### Step 1: Create a Basic Flow Endpoint ```typescript import { App, Flow, HttpTrigger, LogTask } from "bknd"; // Define a flow with tasks const helloFlow = new Flow("hello-endpoint", [ new LogTask("log", { message: "Hello endpoint called!" }), ]); // Attach HTTP trigger helloFlow.setTrigg
- Prerequisites
- When to Use UI Mode
- When to Use Code Mode
- Two Approaches
- Approach 1: Flows with HTTP Triggers
- Step 1: Create a Basic Flow Endpoint
- Step 2: Create Endpoint with Response
- Step 3: Handle POST with Request Body
- Step 4: Sync vs Async Mode
- Step 5: Multi-Task Flow with Connections
- HTTP Trigger Options Reference
- Approach 2: Plugin Routes (Direct Hono)
- Step 1: Create Plugin with Routes
- Step 2: Access App Context in Plugin Routes
curl http://localhost:7654/api/custom/hello curl -X POST http://localhost:7654/api/custom/process \ List all registered routes including custom ones bknd debug routes
What does the bknd-custom-endpoint skill do?
Use when creating custom API endpoints in Bknd. Covers HTTP triggers with Flows, plugin routes via onServerInit, request/response handling, sync vs async modes, accessing request data, and returning custom responses.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill bknd-custom-endpoint --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.