SDKs & developer tools

SDKs for the stacks your team already uses.

Partner-oriented clients help engineering teams evaluate ONE faster. Availability below reflects the current evaluation posture — ask us for access during onboarding.

Clients

Multi-language coverage for B2B backends.

OneClient

Available during technical evaluation

JavaScript / Node

Partner client for health checks, tenant context, plan generation and related flows in Node services.

one_client

Available during technical evaluation

Python

Python client mirroring the core partner surface for backend and data teams.

ONE PHP SDK

Early access

PHP

PHP partner client aligned with the same core partner capabilities.

ONE .NET SDK

Early access

.NET

.NET client for teams standardising on Microsoft stacks for server-side integration.

Playground

Interactive evaluation

An interactive developer playground is available during technical evaluation to help teams validate authentication and core endpoints — alongside OpenAPI contracts and SDK clients.

Available during technical evaluation

# Node example (conceptual)
import { OneClient } from "@osca/one-client";

const one = new OneClient({
  baseUrl: "https://api.one.osca.solutions",
  token: process.env.ONE_TOKEN,
});

const plan = await one.createPlan({
  oneUserId: "…",
  horizonDays: 7,
});

Build personalised nutrition into your product.

Talk to the ONE by OSCA team about how personalised nutrition can fit your product roadmap — and how optional wearable data context can extend it when needed.

Product teams book a demo · Engineering teams explore the API and SDKs