OpenMeter Entitlements

Get customer entitlement access

Changed on

Pre-release Endpoint This endpoint is currently in beta and is subject to change.

Get the customer's access to a single feature.

get/v3/openmeter/customers/{customerId}/entitlement-access/features/{featureKey}

Request

  • Base URL: https://global.api.konghq.com
  • URL: https://global.api.konghq.com/v3/openmeter/customers/{customerId}/entitlement-access/features/{featureKey}
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer
    • HTTP bearer
    • HTTP bearer

Path parameters

customerIdstring required

ULID (Universally Unique Lexicographically Sortable Identifier).

Example:01G65Z755AFWAKHE12NY0CQ9FH
featureKeystring required

A key is a unique string that is used to identify a resource.

Example:resource_key

Response

EntitlementAccessCheckResult response.

has_accessboolean required

Whether the customer has access to the feature. Always true for boolean and static entitlements. Depends on balance for metered entitlements.

configstring

Only available for static entitlements. Config is the JSON parsable configuration of the entitlement. Useful to describe per customer configuration.

type'metered' | 'static' | 'boolean'

The type of the entitlement.

If not provided, the feature has no entitlement defined (has access is always false in this case)

Example response

{
  "has_access": true,
  "config": "{ \"availableModels\": [\"gpt-5\", \"gpt-4o\"] }"
}

Changes

    • breaking

      added to the / response property oneOf list for the response status

    • warning

      added the new key_invalid enum value to the ////// response property for the response status

    • warning

      added the new unique enum value to the ////// response property for the response status

    • info

      endpoint added