# SDKs and language examples

Availability: Release contract.
Last reviewed: 2026-08-28.

Use a small HTTP client before depending on an SDK. The release examples cover the authentication contract, not business execution.

## Choose a language

Read the [HTTP](/docs/integrations/http), [TypeScript](/docs/integrations/typescript), [Python](/docs/integrations/python) or [Ruby](/docs/integrations/ruby) guide. They use ordinary language HTTP facilities and keep secrets outside source code.

No new Market Monolith package publication, marketplace installation or client acceptance is implied. Existing SDK and OpenAPI source foundations need compatibility and release verification before being described as supported distributions.

## Keep clients predictable

Set a bounded timeout, inspect HTTP status before parsing a success shape, and refuse redirects when sending the application credential. Log safe result metadata, not request headers, raw exceptions or secrets.

Authentication checks are free but may be rate-limited. Do not add aggressive background retries merely to make an onboarding indicator turn green.

## Native clients

Native-shell path configuration is a compatibility topic, not proof of a shipped iOS or Android application. Server keys must not be embedded in mobile binaries.

## Upgrade deliberately

Pin any dependencies your own application uses and review their official documentation. Future business SDK examples must state supported contract versions and preserve partial/uncertain outcomes rather than hiding them behind a success object.