java-getting-startedlisted

# Getting started with an APIMatic-generated Java SDK This is the **SDK-specific** reference and grounding layer, and the entry into the companion `java-*` skills. The SDK is built on the shared `io.apimatic` runtime artifacts (`io.apimatic:core`, `io.apimatic:core-interfaces`, and `io.apimatic:okhttp-client-adapter`), with **OkHttp3** as the transport and **Jackson** for JSON. 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: `java-client-initialization`, `java-authentication`, `java-calling-endpoints`, `java-models`, `java-error-handling`, `java-configuration-resilience`, `java-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, class, enum, and exception type as you go. The source > is obtained exactly as that section describes. Do **not** vendor or edit it inside your own packages; > regenerate the SDK instead if something needs to change. ## SDK identity | | | | --- | --- | | API | `PayPal Server SDK` | | Runtime dependencies | `io.apimatic:core`, `io.apimatic:core-interfaces`, `io.apimatic:okhttp-client-adapter` (version ranges pinned in `pom.xml`); Jackson and OkHttp3 arrive transitively | | Maven coordinates | `com.paypal.sdk:paypal-server-sdk:2.29.0` — the `<groupId>`/`<artifactId>`/`<version>` in `pom.xml` | | Client | a single `p