Help us improve
Share bugs, ideas, or general feedback.
From magento2-commerce
Builds Magento 2 REST and GraphQL APIs with webapi.xml, schema.graphqls, resolvers, authentication, and ACL for custom endpoints, schema extensions, and integrations.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin magento2-commerceHow this skill is triggered — by the user, by Claude, or both
Slash command
/magento2-commerce:magento-apiThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Fetch live docs**:
Guides creation of Magento 2 custom modules: registration, directory structure, models, resource models, collections, declarative schema, data/schema patches. For building modules or reviewing architecture.
Provides expert patterns for Shopify app development including Remix/React Router setup, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions.
Provides deprecated Shopify REST Admin API reference—endpoints, auth, rate limits—and GraphQL migration mappings. Use for legacy maintenance or migration planning.
Share bugs, ideas, or general feedback.
Fetch live docs:
https://developer.adobe.com/commerce/webapi/ for Web API overviewhttps://developer.adobe.com/commerce/webapi/graphql/develop/ for GraphQL development guidehttps://developer.adobe.com/commerce/webapi/get-started/authentication/gs-authentication-token/ for authenticationsite:developer.adobe.com commerce php development components web-api for webapi.xml referenceREST endpoints map HTTP methods + URL paths to service contract methods. Defined in etc/webapi.xml.
Each route defines:
url — endpoint path (e.g., /V1/custom/items/:id)method — HTTP method (GET, POST, PUT, DELETE)service — class + method implementing the endpointresource — ACL resource for authorizationPath parameters (:id) map to method parameters by name.
| Type | Header | Use Case |
|---|---|---|
| Admin Token | Authorization: Bearer <token> | Back-office integrations |
| Customer Token | Authorization: Bearer <token> | Customer-facing apps |
| OAuth 1.0a | OAuth headers | Third-party integrations |
| Session | PHP session cookie | Storefront JS widgets |
| Anonymous | resource="anonymous" | Public endpoints |
Available at /rest/<store>/schema — auto-generated from webapi.xml and service contracts.
GraphQL uses a single endpoint (/graphql) with schema files and resolver classes.
Define types, queries, and mutations in etc/schema.graphqls:
Implement Magento\Framework\GraphQl\Query\ResolverInterface:
resolve(Field $field, $context, ResolveInfo $info, array $value = null, array $args = null)Implement Magento\Framework\GraphQl\Query\Resolver\IdentityInterface for full-page cache invalidation of GraphQL responses.
Authorization: Bearer <customer-token> header$context->getExtensionAttributes()->getIsCustomer() for auth checksDefines the resource tree for authorization:
<resource> elements form a hierarchywebapi.xml via <resource ref="Vendor_Module::resource_name"/>anonymous (no auth), self (customer's own data)Fetch the Web API and GraphQL development docs for exact XML schema, resolver signatures, and authentication patterns before implementing.