Add Admin API Endpoint

Create Ghost admin API endpoint files with docName and browse operations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/GeniusHTX/SWE-Skills-Bench --skill add-admin-api-endpoint-geniushtx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Add Admin API Endpoint
Source: https://github.com/GeniusHTX/SWE-Skills-Bench/tree/main/skills/add-admin-api-endpoint
Command: npx skills add https://github.com/GeniusHTX/SWE-Skills-Bench --skill add-admin-api-endpoint-geniushtx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers quickly add new admin API endpoints to Ghost by providing a standardized approach to creating endpoint files, wiring routes, and setting up tests.

Core Features & Use Cases

  • Standardized workflow to add a new admin endpoint by creating the endpoint file with a docName and a browse operation
  • Wire routes in ghost/core/core/server/web/api/endpoints/admin/routes.js
  • Add e2e-api tests to ghost/core/test/e2e-api/admin ensuring endpoint functionality
  • Reuse existing patterns to minimize boilerplate when extending the admin API

Quick Start

Create or modify an admin API endpoint following the steps to implement a new browse endpoint.

Frequently Asked Questions about Add Admin API Endpoint

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

FAQPage Schema
How do I add a new admin API endpoint to Ghost?

You can add a Ghost admin API endpoint by creating a file under the server/api/endpoints directory, defining a docName, wiring the route in routes.js, and verifying functionality with e2e tests.

What is the standard workflow for creating Ghost admin API resources?

The standard workflow for creating Ghost admin API resources involves generating an endpoint file, ensuring a browse endpoint exists, updating the admin routes configuration, and implementing e2e-api tests to verify the integration.

Does adding a Ghost admin endpoint require manual routing configuration?

Yes, adding a Ghost admin endpoint requires manually updating the routes.js file located in ghost/core/core/server/web/api/endpoints/admin to wire the new controller and expose the API path.

How are e2e tests structured for new Ghost admin API endpoints?

E2e tests for Ghost admin API endpoints are added as new files within the ghost/core/test/e2e-api/admin directory to ensure the browse operation and overall endpoint functionality work as expected.

Can I reuse existing patterns when extending the Ghost admin API?

Yes, you can reuse existing patterns when extending the Ghost admin API to minimize boilerplate, applying standardized file creation and routing configurations to quickly implement new browse endpoints.