providers/claude/plugin/skills/ebay/SKILL.md
eBay integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in eBay. Routes through Apideck with serviceId "ebay".
npx skillsauth add apideck-libraries/api-skills ebayInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Access eBay through Apideck's Ecommerce unified API — one of 17 Ecommerce connectors that share the same method surface. Code you write here ports to Shopify, BigCommerce, Shopify (Public App) and 13 other Ecommerce connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant eBay plumbing.
Beta connector. eBay is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
ebayActivate this skill when the user explicitly wants to work with eBay — for example, "list orders in eBay" or "sync products in eBay". This skill teaches the agent:
serviceId to pass on every call (ebay)For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-restFor the raw OpenAPI spec:
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List orders in eBay
const { data } = await apideck.ecommerce.orders.list({
serviceId: "ebay",
});
The Apideck Ecommerce unified API exposes the same methods for every connector in its catalog. Switching from eBay to another Ecommerce connector is a one-string change — no rewrite, no new SDK.
// Today — eBay
await apideck.ecommerce.orders.list({ serviceId: "ebay" });
// Tomorrow — same code, different connector
await apideck.ecommerce.orders.list({ serviceId: "shopify" });
await apideck.ecommerce.orders.list({ serviceId: "bigcommerce" });
This is the compounding advantage of using Apideck over integrating eBay directly: code against the unified Ecommerce API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
available → added → authorized → callable.See apideck-best-practices for Vault setup, connection lifecycle, and handling re-auth flows.
Not every Ecommerce operation is supported by every connector. Always verify before assuming a method works:
curl 'https://unify.apideck.com/connector/connectors/ebay' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}"
See apideck-connector-coverage for patterns around UnsupportedOperationError and connector-specific fallbacks.
When an endpoint isn't covered by the Ecommerce unified API, use Apideck's Proxy to call eBay directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on eBay's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: ebay" \
-H "x-apideck-downstream-url: <target endpoint on eBay>" \
-H "x-apideck-downstream-method: GET"
See eBay's API docs for available endpoints.
Other Ecommerce connectors that share this unified API surface (same method signatures, just change serviceId):
shopify (beta), bigcommerce (beta), shopify-public-app (beta), woocommerce (beta), amazon-seller-central (beta), etsy (beta), magento (beta), bol-com (beta), and 8 more.
apideck-connector-coverage — programmatic coverage checksapideck-best-practices — architecture, Vault, pagination, error handlingapideck-node — TypeScript / Node SDK patternsdevelopment
Jira Teams via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Teams's native API. Use when the user wants to call Jira Teams (no unified API resource mapping). Routes through Apideck with serviceId "jira-teams".
development
Jira Service Desk via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Service Desk's native API. Use when the user wants to call Jira Service Desk (no unified API resource mapping). Routes through Apideck with serviceId "jira-service-desk".
development
Jira Data Center via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Data Center's native API. Use when the user wants to call Jira Data Center (no unified API resource mapping). Routes through Apideck with serviceId "jira-data-center".
development
JetBrains YouTrack via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to JetBrains YouTrack's native API. Use when the user wants to call JetBrains YouTrack (no unified API resource mapping). Routes through Apideck with serviceId "jetbrains-youtrack".