Public API reference
/Browser Feature Transformations
v4 Public API reference
Authentication
Braintree Payments
Decision Engine
Dynamic Offer Decision Engine
Dynamic Offer Promo Code Decision
OAuth Flow
Payments
Product Sharing
SDK Feature Decision Engine
Sessions
Stripe Payments
Third-Party Authentication
User
V4 Gifts
Web Analytics
Zephr Features
Component Library
Change the Stripe subscription price
Oauth2 Access Token
Subscription
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.
Providing a JWT
Supply it as a jwt query parameter, an X-Blaize-Jwt header, an X-Zephr-Jwt header, an Authorization: Bearer header, or a blaize_jwt cookie. If more than one is present, the first found in that order is used.
Security
CookieBlaizeSession or JwtQuery or JwtHeaderXBlaizeJwt or JwtHeaderXZephrJwt or JwtBearer or JwtCookie
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"
- https://demo-sitehttps://demo-site/zephr/feature-decisions
{ "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", "customData": { "key": "value" } }
Response
{ "featureResults": { "featureX": "blaize.transform.resource('...')" }, "resources": { "uiComponents": { … } }, "accessDetails": { "authenticated": false, "accessDecisions": { … }, "entitlements": { … }, "credits": { … }, "meters": { … }, "trialTrackingDetails": [ … ], "trials": { … }, "timeTrials": { … }, "testGroups": { … }, "activeProducts": [ … ] } }