bagisto-api-admin
Installation
SKILL.md
Build an admin app on the Bagisto Admin API
Implement any admin/back-office interface on the Bagisto Admin API (/api/admin/* REST + POST /api/admin/graphql). The API mirrors the Bagisto admin panel menu-for-menu, so any admin screen can be rebuilt from it. This skill is a router: it gives the flow and points you at the per-menu reference page; the reference pages carry the endpoints, UI/UX, and checklists.
⚠️ Load these FIRST (before any code)
reference/connecting-to-the-api.md— admin auth (the Integration Bearer token), the{data,meta}listing envelope, the list→detail→action pattern, permissions, errors, and the verify-before-coding protocol.reference/graphql.md— if the client picked GraphQL: the admin endpoint, the result-field/idrule, camelCase inputs + filter args, cursor pagination.
The api-docs are the source of truth for exact shapes — https://api-docs.bagisto.com (Admin API section) + its /llms.txt index. The reference pages name the endpoints and flow; open the linked docs page for the precise body/response before writing the call. Never invent a payload from memory.
Step 1 — ask the client (CRITICAL, before building)
- Platform — web, mobile (native/cross-platform), desktop?
- Framework/stack — React/Next, Vue/Nuxt, Flutter, React Native, plain JS?
- Which admin menus — Sales, Catalog, Customers, Marketing, CMS, Settings, Configuration, Dashboard/Reporting — or one first?
- Transport — REST or GraphQL? (REST for list/detail/action screens; GraphQL when a screen needs many related fields in one round-trip. Both fully supported.)
- First screen/flow — order list + actions, product management, Create-Order, a dashboard, …?