bknd-custom-endpoint

Create custom HTTP endpoints in BKND via Flows or plugin routes.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cameronapak/melos --skill bknd-custom-endpoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bknd-custom-endpoint
Source: https://github.com/cameronapak/melos/tree/main/.agents/skills/bknd-custom-endpoint
Command: npx skills add https://github.com/cameronapak/melos --skill bknd-custom-endpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers implement custom API endpoints in BKND beyond the built-in CRUD routes, enabling tailored HTTP interfaces and integration points.

Core Features & Use Cases

  • Flows + HTTP Triggers: Build multi-step endpoints that process requests and respond with computed results.
  • Plugin Routes (onServerInit): Expose lightweight routes via plugin architecture for direct API access.
  • Request/Response Handling: Access headers, bodies, query parameters, and path segments; respond with JSON, text, or custom responses.
  • Sync vs Async: Support for both immediate responses and background processing for long-running tasks.
  • Use Case: Create a webhook receiver or a custom internal API endpoint to orchestrate business logic.

Quick Start

Install BKND, then choose between flows or plugin routes to implement your endpoints. For flows, define a Flow with an HttpTrigger and optionally set a responding task. For plugins, create a plugin with onServerInit to register Hono routes. Example steps: 1) Create a Flow or plugin, 2) Attach HTTP trigger or routes, 3) Run BKND and send requests to verify responses.

Frequently Asked Questions about bknd-custom-endpoint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create custom API endpoints in BKND beyond the standard CRUD routes?

BKND supports custom API endpoints through two methods: Flows using HttpTriggers for multi-step processing, or plugin routes defined in onServerInit to expose lightweight Hono routes for direct HTTP access.

Can I handle request headers, bodies, and query parameters in BKND flows?

Yes, BKND custom endpoints support full request and response handling, allowing you to access headers, bodies, query parameters, and path segments, and respond with JSON, text, or custom responses.

Do I need TypeScript to build custom HTTP endpoints in BKND?

TypeScript or JavaScript knowledge is required to build custom HTTP endpoints in BKND, as you need to define logic within Flows or create plugins to register Hono routes.

What is the difference between sync and async modes in BKND custom endpoints?

Sync mode provides immediate responses for standard request handling, while async mode enables background processing for long-running tasks triggered by your custom BKND API endpoints.

When should I use plugin routes instead of flows for a BKND API endpoint?

Use plugin routes via onServerInit for lightweight, direct API access, and choose Flows with HttpTriggers when you need multi-step endpoints that orchestrate complex business logic before responding.

Can I build a webhook receiver using BKND custom endpoints?

Yes, you can build a webhook receiver or custom internal API endpoint using BKND Flows and HttpTriggers to orchestrate business logic and process incoming HTTP requests.