SnozeDevelopers
API referenceProduct controls

Evaluate a feature flag for the caller

Returns whether the named platform feature flag is on for this user and workspace, taking the flag's status, audience targeting, and percentage rollout into account. Requires a Clerk session with a synced profile — API keys are rejected — and the caller must be able to read the workspace, which is loaded first. An unknown key, or any failure while evaluating, resolves to disabled rather than an error.

GET
/v1/workspaces/{workspaceId}/product-controls/features/{key}

Authorization

apiKey
headerAuthorizationBearer <snoze_sk_…>

Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.

Path Parameters

workspaceId*string
key*string

Response Body

Success

application/json
  1. response
data*
Example Request
curl -X GET 'https://api.snoze.dev/v1/workspaces/string/product-controls/features/string'
Example Response
{  "data": {    "key": "string",    "enabled": true  }}

List the deliveries received by an inbound endpoint

Returns the payloads received on one endpoint, newest first, with each delivery's signature status, resulting workspace event id, and any processing error. Requires the `webhooks:read` permission; an unknown endpoint returns not-found. Pass `limit` to change the page size; it defaults to 50 and is capped at 200.

Read the caller's experiment assignment for a target

Returns the running experiment registered against the given target key together with the variant this user or workspace is bucketed into, or a null assignment when no running experiment matches. Requires a Clerk session with a synced profile and read access to the workspace. Bucketing is deterministic per subject, so repeated calls return the same variant.