Skip to content
/
Browser Feature Transform...

Public API Reference (2025-07-30)

The Zephr Public API provides common client-side actions tied to a session cookie. Unlike the Admin API, neither users nor other resources can be dereferenced; the only data that can be accessed is owned by the user who is currently signed-in. This design is used to protect other users from malicious attacks.

You can find the base URL for the Public API by navigating to your site domains. To do this, select Sites from the Delivery menu, select your site, and then click the Site Domains button. The base URL is the Live domain.

Zephr forms use the Public API by default, with relative URLs based on the base URL.

Download OpenAPI description
index.json
index.yaml
Languages
Servers
Mock server
https://developer.zuora.com/_mock/zephr-api-reference/zephr-public-api
https://{your-domain}

Authentication

Operations

Braintree Payments

Operations

Browser Feature Transformations

Operations

Execute Browser feature decisions

Request

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.

Security
CookieBlaizeSession or JwtQuery or JwtHeaderXBlaizeJwt or JwtHeaderXZephrJwt or JwtBearer or JwtCookie
Headers
Cookiestring

The session cookie.

Example: blaize_session=...
Bodyapplication/json
featureIdsArray of anyrequired

Array of HTML Feature IDs

Example: ["featureX"]
sessionstring

Zephr Session ID

Example: "xxx-xxx-xxx"
refererstring

Browser referer

Example: "https://www.zephr.com/"
pathstring

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

Example: "/x.html"
content_metadataobject
Example: {"content_id":"xxx-xxx-xxx"}
giftTokenstring

Token to provide access to content for one session.

Example: "xxx-xxx-xxx"
jwtstring

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

Example: "xxx-xxx-xxx"
customDataobject

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

Example: {"key":"value"}
curl -i -X POST \
  https://developer.zuora.com/_mock/zephr-api-reference/zephr-public-api/zephr/feature-decisions \
  -H 'Content-Type: application/json' \
  -H 'Cookie: blaize_session=...' \
  -b blaize_session=YOUR_API_KEY_HERE \
  -d '{
    "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"
    }
  }'

Responses

OK

Bodyapplication/json
featureResultsobject

Map of HTML Feature IDs and feature result transformations.

resourcesobject

Map of transformation resources

accessDetailsobject

Feature access details

Response
application/json
{
  "featureResults": {
    "featureX": "blaize.transform.resource('...')"
  },
  "resources": {
    "uiComponents": { … }
  },
  "accessDetails": {
    "authenticated": false,
    "accessDecisions": { … },
    "entitlements": { … },
    "credits": { … },
    "meters": { … },
    "trialTrackingDetails": [ … ],
    "trials": { … },
    "timeTrials": { … },
    "testGroups": { … },
    "activeProducts": [ … ]
  }
}

Execute Browser feature transformations

Request

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.

Security
CookieBlaizeSession or JwtQuery or JwtHeaderXBlaizeJwt or JwtHeaderXZephrJwt or JwtBearer or JwtCookie
Headers
Cookiestring

The session cookie.

Example: blaize_session=...
Bodyapplication/json
featureIdsArray of anyrequired

An array of HTML Feature IDs.

Example: ["featureX"]
sessionstring

The Zephr Session ID.

Example: "xxx-xxx-xxx"
refererstring

Browser referer

Example: "https://www.zephr.com/"
pathstring

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

Example: "/x.html"
content_metadataobject
Example: {"content_id":"xxx-xxx-xxx"}
giftTokenstring

Token to provide access to content for one session.

Example: "xxx-xxx-xxx"
jwtstring

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

Example: "xxx-xxx-xxx"
customDataobject

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

Example: {"key":"value"}
curl -i -X POST \
  https://developer.zuora.com/_mock/zephr-api-reference/zephr-public-api/zephr/feature-transformations \
  -H 'Content-Type: application/json' \
  -H 'Cookie: blaize_session=...' \
  -b blaize_session=YOUR_API_KEY_HERE \
  -d '{
    "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"
    }
  }'

Responses

OK

Bodyapplication/json
featureResultsobject

Map of HTML Feature IDs and feature result transformations

resourcesobject
Response
application/json
{
  "featureResults": {
    "featureX": { … }
  },
  "accessDetails": {
    "authenticated": false,
    "accessDecisions": { … },
    "entitlements": { … },
    "credits": { … },
    "meters": { … },
    "trialTrackingDetails": [ … ],
    "trials": { … },
    "timeTrials": { … },
    "testGroups": { … },
    "activeProducts": [ … ]
  }
}

Decision Engine

Operations

Dynamic Offer Decision Engine

Operations

Dynamic Offer Promo Code Decision

Operations

OAuth Flow

Operations

Payments

Operations

Product Sharing

Operations

SDK Feature Decision Engine

Operations

Sessions

Operations

Stripe Payments

Operations

Third-Party Authentication

This section contains the API operations for the OAuth 2.0 Authorization Code Flow.

Operations

User

Operations

V4 Gifts

Create a Gift resource for V4. Gifts can be used to provide access to a particular URL for one session only by appending a gift token ID to the URL as the gift path parameter.

Operations

Web Analytics

Operations

Zephr Features

Operations

Component Library

Operations

Change the Stripe subscription price

Request

Generates a new preview of the price that Stripe will charge the customer if they create a new subscription for the specified plan. Note: This method does not create any entities in Stripe and does not result in any payments being made.

Security
CookieBlaizeSession or JwtQuery or JwtHeaderXBlaizeJwt or JwtHeaderXZephrJwt or JwtBearer or JwtCookie
Path
externalIdstringrequired
Bodyapplication/json
plan_idstring
curl -i -X POST \
  'https://developer.zuora.com/_mock/zephr-api-reference/zephr-public-api/zephr/payment/stripe/subscriptions/{externalId}/change-previews' \
  -H 'Content-Type: application/json' \
  -b blaize_session=YOUR_API_KEY_HERE \
  -d '{
    "plan_id": "string"
  }'

Responses

OK

Bodyapplication/json
totalnumber

The total amount the user will be initially charged for the subscription in the relevant currency's lowest denomination (e.g. pence), i.e. for a monthly subscription, the first month's cost.

Example: 5000
sub_totalnumber

The total amount minus tax for the initial charge in the relevant currency's lowest denomination (e.g. pence).

Example: 4500
Response
application/json
{
  "total": 5000,
  "sub_total": 4500
}

Oauth2 Access Token

Operations

Subscription

Operations