Sign in

v1

latestOpenAPI 3.0.02026-08-0610682246.0 KB
Browser Feature Transformations

Execute Browser feature decisions

Zephr HTML Features can be run in the browser by calling this API directly or using the Zephr Browser SDK. For compatibility with CDN, any web headers (Referrer, User-Agent) will be accepted and passed onto the rule engine. Note: This endpoint may return different response structures depending on your tenant configuration. The example shown here reflects one supported response format. If your tenant returns a different structure and you need this format, contact Zuora Support for guidance.

post/zephr/feature-decisions

Headers

Cookiestring

The session cookie.

Request body

sessionstring

Zephr Session ID

refererstring

Browser referer

pathstring

Request path, defaults to "/". If available, include the content ID as a query parameter. For example, /story.html?content_id=abc-123.

giftTokenstring

Token to provide access to content for one session.

jwtstring

A Json Web Token, may include identity or product holding claims.

customDataobject

Custom data to be used in Feature HTML browser rule. Accepts a JSON object.

Example request

{
  "featureIds": [
    "featureX"
  ],
  "session": "xxx-xxx-xxx",
  "referer": "https://www.zephr.com/",
  "path": "/x.html",
  "content_metadata": {
    "content_id": "xxx-xxx-xxx"
  },
  "giftToken": "xxx-xxx-xxx",
  "jwt": "xxx-xxx-xxx",
  "customData": {
    "key": "value"
  }
}

Response

OK

Example response

{
  "featureResults": {
    "featureX": "blaize.transform.resource('...')"
  }
}