OpenFeature (OFREP)

Evaluate Oriel feature flags from any OpenFeature SDK without an Oriel-specific provider. Oriel implements the OpenFeature Remote Evaluation Protocol (OFREP), so the generic OFREP provider for your language talks to Oriel directly and your code targets the OpenFeature standard instead of a custom shape.

What to configure

Mint a project- and environment-pinned feature-flag SDK key under workspace settings. OFREP uses the same bearer token as Oriel’s /api/v1/sdk/flags surface.

Authorization: Bearer orl_...

The OpenFeature evaluation context must carry a targetingKey; Oriel maps it to the flag context key. Additional context attributes are available to targeting rules.

{ "context": { "targetingKey": "user-123", "tier": "pro" } }

Wiring a provider

Point the generic OFREP provider at your Oriel base URL.

import "github.com/open-feature/go-sdk-contrib/providers/ofrep"

provider := ofrep.NewProvider(
    "https://oriel.example.com",
    ofrep.WithBearerToken("orl_..."),
)
openfeature.SetProvider(provider)

import { OFREPWebProvider } from "@openfeature/ofrep-web-provider";

OpenFeature.setProvider(
  new OFREPWebProvider({
    baseUrl: "https://oriel.example.com",
    headers: [["Authorization", "Bearer orl_..."]],
  }),
);

Tracking

OFREP defines no tracking endpoint, and OpenFeature tracking is a client-side concern. Oriel does not expose a remote tracking call. Evaluations and per-unit exposures are recorded on the evaluation path and surface as flag telemetry in the same project when the API and ingest path run together.

For endpoint shapes, reason mapping, and error mapping, see the OpenFeature OFREP reference.