Features
Create a new feature
Customers
Invoices
Wallets
Entitlements
Environments
Events
Features
Payments
Integrations
Subscriptions
Tenants
Users
Features
Create a new feature
Create a new feature
POST
/
features
curl --request POST \
--url https://api.cloud.flexprice.io/v1/features \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '{
"description": "<string>",
"lookup_key": "<string>",
"metadata": {},
"meter": {
"aggregation": {
"field": "<string>",
"type": "COUNT"
},
"event_name": "api_request",
"filters": [
{
"key": "<string>",
"values": [
"<string>"
]
}
],
"name": "API Usage Meter",
"reset_usage": "BILLING_PERIOD"
},
"meter_id": "<string>",
"name": "<string>",
"type": "metered",
"unit_plural": "<string>",
"unit_singular": "<string>"
}'{
"created_at": "<string>",
"created_by": "<string>",
"description": "<string>",
"environment_id": "<string>",
"id": "<string>",
"lookup_key": "<string>",
"metadata": {},
"meter": {
"aggregation": {
"field": "<string>",
"type": "COUNT"
},
"created_at": "2024-03-20T15:04:05Z",
"event_name": "api_request",
"filters": [
{
"key": "<string>",
"values": [
"<string>"
]
}
],
"id": "550e8400-e29b-41d4-a716-446655440000",
"name": "API Usage Meter",
"reset_usage": "BILLING_PERIOD",
"status": "published",
"tenant_id": "tenant123",
"updated_at": "2024-03-20T15:04:05Z"
},
"meter_id": "<string>",
"name": "<string>",
"status": "published",
"tenant_id": "<string>",
"type": "metered",
"unit_plural": "<string>",
"unit_singular": "<string>",
"updated_at": "<string>",
"updated_by": "<string>"
}Authorizations
Enter your API key in the format x-api-key <api-key>*
Body
application/json
Feature to create
Available options:
metered, boolean, static Example:
"api_request"
Example:
"API Usage Meter"
Available options:
BILLING_PERIOD, NEVER Key is the key for the filter from $event.properties Currently we support only first level keys in the properties and not nested keys
Values are the possible values for the filter to be considered for the meter For ex "model_name" could have values "o1-mini", "gpt-4o" etc
Response
201
application/json
Created
Example:
"2024-03-20T15:04:05Z"
Example:
"api_request"
Key is the key for the filter from $event.properties Currently we support only first level keys in the properties and not nested keys
Values are the possible values for the filter to be considered for the meter For ex "model_name" could have values "o1-mini", "gpt-4o" etc
Example:
"550e8400-e29b-41d4-a716-446655440000"
Example:
"API Usage Meter"
Available options:
BILLING_PERIOD, NEVER Example:
"published"
Example:
"tenant123"
Example:
"2024-03-20T15:04:05Z"
Available options:
published, deleted, archived Available options:
metered, boolean, static curl --request POST \
--url https://api.cloud.flexprice.io/v1/features \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '{
"description": "<string>",
"lookup_key": "<string>",
"metadata": {},
"meter": {
"aggregation": {
"field": "<string>",
"type": "COUNT"
},
"event_name": "api_request",
"filters": [
{
"key": "<string>",
"values": [
"<string>"
]
}
],
"name": "API Usage Meter",
"reset_usage": "BILLING_PERIOD"
},
"meter_id": "<string>",
"name": "<string>",
"type": "metered",
"unit_plural": "<string>",
"unit_singular": "<string>"
}'{
"created_at": "<string>",
"created_by": "<string>",
"description": "<string>",
"environment_id": "<string>",
"id": "<string>",
"lookup_key": "<string>",
"metadata": {},
"meter": {
"aggregation": {
"field": "<string>",
"type": "COUNT"
},
"created_at": "2024-03-20T15:04:05Z",
"event_name": "api_request",
"filters": [
{
"key": "<string>",
"values": [
"<string>"
]
}
],
"id": "550e8400-e29b-41d4-a716-446655440000",
"name": "API Usage Meter",
"reset_usage": "BILLING_PERIOD",
"status": "published",
"tenant_id": "tenant123",
"updated_at": "2024-03-20T15:04:05Z"
},
"meter_id": "<string>",
"name": "<string>",
"status": "published",
"tenant_id": "<string>",
"type": "metered",
"unit_plural": "<string>",
"unit_singular": "<string>",
"updated_at": "<string>",
"updated_by": "<string>"
}