building-apis

Build Celigo custom HTTP APIs with router-based or script-mode request handling.

3|2|Updated May 20, 2026
One-click install
npx skills add https://github.com/celigo/ai --skill building-apis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-apis
Source: https://github.com/celigo/ai/tree/main/skills/building-apis
Command: npx skills add https://github.com/celigo/ai --skill building-apis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you turn existing Celigo export/import business logic into synchronous, structured HTTP APIs that external systems can reliably call.

Core Features & Use Cases

  • Design REST endpoints (builder mode) that route incoming requests through Celigo routers, lookup exports, and import writes, then return success/fail/custom responses.
  • Control request and response shapes using request transforms, response mapping, and response router selection to match your clients’ required schemas.
  • Use script-mode APIs when logic is too dynamic to express declaratively, returning {statusCode, headers, body} from a single handleRequest function.
  • Common scenarios: proxying authenticated requests via Celigo tokens, implementing lookup/write operations as a REST interface, and supporting multiple response shapes (e.g., success vs validation errors).

Quick Start

Tell the AI: “Using the building-apis skill, outline a builder-mode Celigo API that accepts POST /orders, routes requests to a validation branch and an imports branch, and returns a structured success response plus a structured fail response with correct status codes.”

Frequently Asked Questions about building-apis

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

FAQPage Schema
How do I expose Celigo integration logic as a synchronous REST endpoint?

You can expose Celigo integration logic as a synchronous REST endpoint by building custom HTTP APIs that route incoming requests through routers, lookup exports, and import writes, returning structured success, fail, or custom responses to external callers.

What is the best way to structure request and response shapes for a Celigo REST API?

The best way to structure request and response shapes for a Celigo REST API is using request transforms and response mapping within builder mode, routing requests through page processors and selecting apiRouter responses to match client schemas.

When should I use script mode instead of builder mode for a Celigo HTTP API?

You should use script mode for a Celigo HTTP API when your logic is too dynamic to express declaratively, allowing you to handle requests and return statusCode, headers, and body objects from a single handleRequest function.

What components are required to configure a builder-mode REST API in Celigo?

Configuring a builder-mode REST API in Celigo requires a name, type, request method, relativeURI, at least one router or branch, apiRouter response routing, and defined success and fail responses for deterministic request-to-response behavior.

Can I return multiple custom response shapes from a single Celigo API endpoint?

Yes, you can return multiple custom response shapes from a single Celigo API endpoint by defining structured success and fail responses or using response router selection within builder mode to support varying schemas like validation errors.

Does Celigo API routing support proxying authenticated requests via tokens?

Yes, Celigo API routing supports proxying authenticated requests via tokens, allowing external systems to reliably call synchronous HTTP APIs that process lookup and write operations through structured routers and page processors.