SDKs

GemInHay ships first-party SDKs for the three stacks dating apps actually build on:

• Java — dev.geminhay:geminhay-sdk:1.0.0
• Python — pip install geminhay
• TypeScript — @geminhay/sdk (Node 18+)

All three speak the same wire protocol; the API surface is intentionally identical across languages so docs apply equally to all of them.

What the SDKs do for you

• Auth handling — read GEMINHAY_API_KEY from env or accept it via the builder.
• Retries with jittered backoff for transient 5xx and 429 responses.
• Typed responses — every endpoint returns a typed object, no JSON destructuring in your code.
• Idempotency keys — auto-generated per request so retries are safe.
• Telemetry headers — SDK version + language reported on every call so we can spot upgrade-blocking issues from the partner portal's analytics.
• Structured errors — QuotaExceededException / RateLimitedException / UnsafeContentException instead of generic HTTP errors.

Choosing a tier

If you're starting fresh, pick whichever SDK matches your existing stack — the SDK choice does not affect API behavior, latency, billing, or features.

If you're polyglot, prefer:

• Java for high-throughput backend services where typed contracts and null-safety matter most.
• Python for ML workflows or data-pipeline integrations.
• TypeScript for any code that runs in Node.js — including Lambda / Cloud Functions / Workers.

What's NOT in the SDKs (yet)

• Browser-only / Edge runtime support — the SDKs assume a Node-compatible environment.
• Streaming opener responses — the underlying API supports it; the SDK exposes only the all-at-once response in 1.0. Coming in 1.1.