Features

Features describe what your API offers to customers. They represent the capabilities in your API product - access to specific endpoints, usage allowances, premium functionality, or any other aspect you want to track or gate.

Metered vs Static Features

Features come in two types:

• Metered features are linked to a meter and track consumption. Use these for usage-based capabilities like API calls, tokens, or data transfer.
• Static features have no meter attached. Use these for boolean capabilities like "access to premium endpoints" or "priority support".

Feature Properties

Creating a Feature

Create a metered feature linked to the api_requests meter. The feature's key must match the meter's slug:

Code
curl \
  https://dev.zuplo.com/v3/metering/$BUCKET_ID/features \
  --request POST \
  --header "Authorization: Bearer $ZAPI_KEY" \
  --header "Content-Type: application/json" \
  --data @- << EOF
{
  "key": "api_requests",
  "name": "API Requests",
  "meterSlug": "api_requests"
}
EOF

The response includes the created feature:

Code
{
  "id": "01ARZ3NDEKTSV4RRFFQ69G5FAV",
  "key": "api_requests",
  "name": "API Requests",
  "meterSlug": "api_requests",
  "createdAt": "2026-01-01T01:01:01.001Z",
  "updatedAt": "2026-01-01T01:01:01.001Z"
}

Creating a Static Feature

For features without usage tracking, omit the meterSlug. A plan's rate card attaches a boolean entitlement that determines whether the customer has access to the capability:

Code
curl \
  https://dev.zuplo.com/v3/metering/$BUCKET_ID/features \
  --request POST \
  --header "Authorization: Bearer $ZAPI_KEY" \
  --header "Content-Type: application/json" \
  --data @- << EOF
{
  "key": "priority_support",
  "name": "Priority Support"
}
EOF

API Reference

For complete API operations (list, get, archive), see the Features API Reference.