Client libraries

Official libraries wrap authentication, retries, and pagination so you write less boilerplate:

LanguageInstallNotes
JavaScript / TypeScriptnpm install @example/sdkNode.js 18+. Browser use is not supported, keys stay server-side.
Pythonpip install example-sdkPython 3.9+.
import { ExampleClient } from '@example/sdk'

const client = new ExampleClient({ apiKey: process.env.API_KEY })

const order = await client.orders.create({
  total: 42.50,
  currency: 'USD',
})

The libraries read API_KEY from the environment, retry transient failures automatically, and send idempotency keys on create calls. See Idempotent requests for how that works.

OpenAPI specifications

Every published API ships with an OpenAPI 3.0 specification. You can download the spec from each API's page in the API catalog.

Use the spec to:

  • Generate a client in any language with an OpenAPI generator.
  • Mock the API in your integration tests.
  • Validate your requests and responses against the published schema.

Testing tools

  • Sandbox mode - register your application with an API in sandbox to get test credentials. Requests behave like production but never create real resources.
  • Test cards and addresses - the sandbox docs for each API list deterministic test values that trigger specific responses.
Keep keys out of the browser

Client libraries are for server-side use. If you build a browser app, proxy your API calls through your own backend so credentials never reach the client.

Next steps