Skip to main content

Entitlements & Feature Gating

Fype provides an Entitlements Engine that separates purchase details from client-side feature authorization.

Core Entitlements Concept

Your application should never check if a customer has bought a specific “Monthly Plan” or “Yearly Plan.” If you rename plans or change prices, you would have to redeploy your frontend. Instead, your application checks if the customer has an active Entitlement (e.g., premium_analytics). Fype maps purchase events to these entitlements on the server.

Verifying Customer Access

1. Retrieve Active Entitlements via API

To check which entitlements are active for a customer, query the entitlements endpoint:
  • Endpoint: GET /v1/subscriptions/customer/{customer_id}/entitlements
  • Headers: Authorization: Bearer YOUR_API_KEY

Example Response

2. Verify Access using the Python SDK

The Fype SDK provides a convenience helper to check for a specific permission directly:

Setup Guide

1. Create an Entitlement

Define a feature slug in the Fype catalog:
Link the entitlement to a product. Any customer with an active or trialing subscription to this product will automatically have the entitlement unlocked.