← ClaudeAtlas

typescript-getting-startedlisted

Entry point for integrating the PayPal Server SDK TypeScript/Node SDK (APIMatic-generated, built on the @apimatic/* runtime packages). Carries the SDK's identity — npm package, `Client` class, `Configuration`, environments, the `ApiError` base — the package layout, and where to read the source. Load this first, before any other typescript-* skill.
MuHamza30/paypal-api-plugin · ★ 0 · Web & Frontend · score 70
Install: claude install-skill MuHamza30/paypal-api-plugin
# Getting started with an APIMatic-generated TypeScript SDK This is the **SDK-specific** reference and grounding layer, and the entry into the companion `typescript-*` skills. The SDK is built on the shared `@apimatic/*` runtime packages — always `@apimatic/core`, `@apimatic/schema`, `@apimatic/axios-client-adapter`, `@apimatic/authentication-adapters` and `tslib`, plus feature-gated ones such as `@apimatic/oauth-adapters` and `@apimatic/pagination`. **`package.json` `dependencies` is the authoritative list — read it rather than assuming.** For the general patterns that apply to *any* such SDK (client setup, auth, calling endpoints, models, error handling, retries, testing), see the companion API-agnostic skills: `typescript-client-initialization`, `typescript-authentication`, `typescript-calling-endpoints`, `typescript-models`, `typescript-error-handling`, `typescript-configuration-resilience`, `typescript-testing`. > **Before writing any integration code, locate the SDK source on disk** (see the *SDK source* section > below) and read it to confirm every signature, interface, enum, schema, and error type as you go. The > source is obtained exactly as that section describes. Do **not** vendor or edit it inside your project; > regenerate the SDK instead if something needs to change. ## SDK identity | | | | --- | --- | | API | `PayPal Server SDK` | | Runtime dependencies | always `@apimatic/core`, `@apimatic/schema`, `@apimatic/axios-client-adapter`, `@apimatic/authenticati