Skip to content

SDKs & APIs Overview

This tab is for engineers wiring ABetterChoice into application code. It answers one question: how do I get experiment assignments and remote-config values into my runtime, and how do I report exposures back?

Generally available today: the Go server SDK and the HTTP API. Every other SDK on Settings → SDK&Key is tagged Coming soon — the per-language pages in this tab document the intended shape so you can plan ahead, but the binaries are not yet published. Use the HTTP API from those runtimes in the meantime.

Settings → SDK&Key page showing the SDK setup grid and the API keys list

What you can do

  • Get to first success in five minutes — go from a project ID and an API key to a returned experiment assignment. SDK Quickstart
  • Pick an integration shape — server SDK, client SDK, or raw HTTP API. Choosing an SDK
  • Drop the Go SDK into your runtime — install, initialize, fetch and log on the server side. Go
  • Call the platform from anywhere — sign and send HTTP requests when no SDK is available. HTTP API
  • Understand the SDK contract — initialization, user objects, exposure logging, default values and local overrides, in one place. SDK concepts
  • Authenticate every call — create, scope, and rotate the keys SDKs and HTTP clients use. API keys

Availability today

The console's Settings → SDK&Key page is the source of truth for what is shippable. Today only the Go server SDK and the HTTP API are generally available; every other SDK card on the page is tagged Coming soon:

SDK / shapeStatusNotes
HTTP APIActiveWorks for any runtime; signed requests, see HTTP API.
Go server SDKActiveSee Go.
C++ server SDKComing soonCard listed under SDK setup; reach out to support if you need early access.
Android client SDKComing soonCard listed under SDK setup; reach out to support if you need early access.
iOS client SDKComing soonSame as Android.
JavaScript client SDKComing soonSame as Android.

The SDK setup grid is informational — clicking a card does not navigate anywhere. While the Coming soon SDKs are not yet shippable, you can still call the platform from those runtimes through the HTTP API today.

How the pieces fit

SDK and API integration architecture: project's API key feeds Server SDK, Client SDK, and HTTP API, all reaching the ABetterChoice platform

The three integration shapes are interchangeable from the platform's point of view: same project, same keys, same experiments and feature flags. Pick the one that matches your runtime.