01
Profiles & rules
Upsert nutrition profiles, resolve rules with precedence and attribution, and configure tenant defaults.
API
Everything your product needs to build personalised nutrition.
ONE exposes the core capabilities of the nutrition engine through APIs designed for reliable B2B integrations — so engineering teams can evaluate and integrate with confidence.
Surface
What partners integrate against.
02
Plan generation
Synchronous meal planning with idempotency support for reliable partner retries and rate-limit guardrails.
03
Catalog authoring
Custom foods, tenant recipes, publish/archive lifecycle and replacement overrides for global items.
04
Search & recommendations
Customer-safe recipe and ingredient search with diet, allergen and preference-aware filtering.
05
Ops & metering
Usage events, observability summaries, request IDs and commercial metering hooks for production teams.
06
Auth model
Tenant API keys and admin access with cross-tenant isolation enforced on every scoped route.
Partner integrations
Built for reliable server integrations.
Partner plan generation expects a stable idempotency key so transport retries replay the first outcome instead of regenerating silently. Correlate support with X-Request-Id.
POST /v1/plans
X-ONE-Client-Type: partner_s2s
Idempotency-Key: plan-user-42-2026-07-25
Authorization: Bearer <token>
{
"oneUserId": "…",
"horizonDays": 7,
"mealTypes": ["breakfast", "lunch", "dinner"]
}Developer experience
Playground and SDKs for faster evaluation.
Interactive playground access and multi-language clients help teams validate auth, planning and catalog flows before production cutover.
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