@openmeter/sdk 1.0.0-beta-8a1bc3f3231a → 1.0.0-beta-cd7699299ca5

package/dist/src/client/schemas.d.ts

@@ -204,6 +204,8 @@ export interface paths {
          * Update Stripe API key
          * @deprecated
          * @description Update the Stripe API key.
+         *
+         *     ⚠️ __Deprecated__: Use [`PUT /api/v1/apps/{id}`](#tag/apps/put/api/v1/apps/{id}) instead.
          */
         put: operations['updateStripeAPIKey'];
         post?: never;
@@ -890,9 +892,12 @@ export interface paths {
         };
         /**
          * List all entitlements
+         * @deprecated
          * @description List all entitlements for all the subjects and features. This endpoint is intended for administrative purposes only.
          *     To fetch the entitlements of a specific subject please use the /api/v1/subjects/{subjectKeyOrID}/entitlements endpoint.
          *     If page is provided that takes precedence and the paginated response is returned.
+         *
+         *     ⚠️ __Deprecated__: Use [`GET /api/v2/entitlements`](#tag/entitlements/get/api/v2/entitlements) instead.
          */
         get: operations['listEntitlements'];
         put?: never;
@@ -911,8 +916,11 @@ export interface paths {
             cookie?: never;
         };
         /**
-         * Get entitlement by id
-         * @description Get entitlement by id.
+         * Get entitlement by ID
+         * @deprecated
+         * @description Get entitlement by ID.
+         *
+         *     ⚠️ __Deprecated__: Use [`GET /api/v2/entitlements/{entitlementId}`](#tag/entitlements/get/api/v2/entitlements/{entitlementId}) instead.
          */
         get: operations['getEntitlementById'];
         put?: never;
@@ -1012,9 +1020,12 @@ export interface paths {
         };
         /**
          * List grants
+         * @deprecated
          * @description List all grants for all the subjects and entitlements. This endpoint is intended for administrative purposes only.
          *     To fetch the grants of a specific entitlement please use the /api/v1/subjects/{subjectKeyOrID}/entitlements/{entitlementOrFeatureID}/grants endpoint.
          *     If page is provided that takes precedence and the paginated response is returned.
+         *
+         *     ⚠️ __Deprecated__: Use [`GET /api/v2/grants`](#tag/entitlements/get/api/v2/grants) instead.
          */
         get: operations['listGrants'];
         put?: never;
@@ -1037,8 +1048,11 @@ export interface paths {
         post?: never;
         /**
          * Void grant
+         * @deprecated
          * @description Voiding a grant means it is no longer valid, it doesn't take part in further balance calculations. Voiding a grant does not retroactively take effect, meaning any usage that has already been attributed to the grant will remain, but future usage cannot be burnt down from the grant.
          *     For example, if you have a single grant for your metered entitlement with an initial amount of 100, and so far 60 usage has been metered, the grant (and the entitlement itself) would have a balance of 40. If you then void that grant, balance becomes 0, but the 60 previous usage will not be affected.
+         *
+         *     ⚠️ __Deprecated__: Use [`DELETE /api/v2/grants/{grantId}`](#tag/entitlements/delete/api/v2/grants/{grantId}) instead.
          */
         delete: operations['voidGrant'];
         options?: never;
@@ -1769,16 +1783,22 @@ export interface paths {
         };
         /**
          * List subjects
+         * @deprecated
          * @description List subjects.
+         *
+         *     ⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
          */
         get: operations['listSubjects'];
         put?: never;
         /**
          * Upsert subject
+         * @deprecated
          * @description Upserts a subject. Creates or updates subject.
          *
          *     If the subject doesn't exist, it will be created.
          *     If the subject exists, it will be partially updated with the provided fields.
+         *
+         *     ⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
          */
         post: operations['upsertSubject'];
         delete?: never;
@@ -1796,14 +1816,20 @@ export interface paths {
         };
         /**
          * Get subject
+         * @deprecated
          * @description Get subject by ID or key.
+         *
+         *     ⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
          */
         get: operations['getSubject'];
         put?: never;
         post?: never;
         /**
          * Delete subject
+         * @deprecated
          * @description Delete subject by ID or key.
+         *
+         *     ⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
          */
         delete: operations['deleteSubject'];
         options?: never;
@@ -1820,12 +1846,16 @@ export interface paths {
         };
         /**
          * List subject entitlements
+         * @deprecated
          * @description List all entitlements for a subject. For checking entitlement access, use the /value endpoint instead.
+         *
+         *     ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements) instead.
          */
         get: operations['listSubjectEntitlements'];
         put?: never;
         /**
          * Create a subject entitlement
+         * @deprecated
          * @description OpenMeter has three types of entitlements: metered, boolean, and static. The type property determines the type of entitlement. The underlying feature has to be compatible with the entitlement type specified in the request (e.g., a metered entitlement needs a feature associated with a meter).
          *
          *     - Boolean entitlements define static feature access, e.g. "Can use SSO authentication".
@@ -1835,6 +1865,8 @@ export interface paths {
          *     A given subject can only have one active (non-deleted) entitlement per featureKey. If you try to create a new entitlement for a featureKey that already has an active entitlement, the request will fail with a 409 error.
          *
          *     Once an entitlement is created you cannot modify it, only delete it.
+         *
+         *     ⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements) instead.
          */
         post: operations['createEntitlement'];
         delete?: never;
@@ -1852,12 +1884,16 @@ export interface paths {
         };
         /**
          * List subject entitlement grants
+         * @deprecated
          * @description List all grants issued for an entitlement. The entitlement can be defined either by its id or featureKey.
+         *
+         *     ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants) instead.
          */
         get: operations['listEntitlementGrants'];
         put?: never;
         /**
          * Create subject entitlement grant
+         * @deprecated
          * @description Grants define a behavior of granting usage for a metered entitlement. They can have complicated recurrence and rollover rules, thanks to which you can define a wide range of access patterns with a single grant, in most cases you don't have to periodically create new grants. You can only issue grants for active metered entitlements.
          *
          *     A grant defines a given amount of usage that can be consumed for the entitlement. The grant is in effect between its effective date and its expiration date. Specifying both is mandatory for new grants.
@@ -1869,6 +1905,8 @@ export interface paths {
          *     Rollover settings define what happens to the remaining balance of a grant at a reset. Balance_After_Reset = MIN(MaxRolloverAmount, MAX(Balance_Before_Reset, MinRolloverAmount))
          *
          *     Grants cannot be changed once created, only deleted. This is to ensure that balance is deterministic regardless of when it is queried.
+         *
+         *     ⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants) instead.
          */
         post: operations['createGrant'];
         delete?: never;
@@ -1887,9 +1925,12 @@ export interface paths {
         get?: never;
         /**
          * Override subject entitlement
+         * @deprecated
          * @description Overriding an entitlement creates a new entitlement from the provided inputs and soft deletes the previous entitlement for the provided subject-feature pair. If the previous entitlement is already deleted or otherwise doesnt exist, the override will fail.
          *
          *     This endpoint is useful for upgrades, downgrades, or other changes to entitlements that require a new entitlement to be created with zero downtime.
+         *
+         *     ⚠️ __Deprecated__: Use [`PUT /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/override`](#tag/entitlements/put/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/override) instead.
          */
         put: operations['overrideEntitlement'];
         post?: never;
@@ -1908,9 +1949,12 @@ export interface paths {
         };
         /**
          * Get subject entitlement value
+         * @deprecated
          * @description This endpoint should be used for access checks and enforcement. All entitlement types share the hasAccess property in their value response, but multiple other properties are returned based on the entitlement type.
          *
          *     For convenience reasons, /value works with both entitlementId and featureKey.
+         *
+         *     ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/value`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/value) instead.
          */
         get: operations['getEntitlementValue'];
         put?: never;
@@ -1930,15 +1974,21 @@ export interface paths {
         };
         /**
          * Get subject entitlement
+         * @deprecated
          * @description Get entitlement by id. For checking entitlement access, use the /value endpoint instead.
+         *
+         *     ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}) instead.
          */
         get: operations['getEntitlement'];
         put?: never;
         post?: never;
         /**
          * Delete subject entitlement
+         * @deprecated
          * @description Deleting an entitlement revokes access to the associated feature. As a single subject can only have one entitlement per featureKey, when "migrating" features you have to delete the old entitlements as well.
          *     As access and status checks can be historical queries, deleting an entitlement populates the deletedAt timestamp. When queried for a time before that, the entitlement is still considered active, you cannot have retroactive changes to access, which is important for, among other things, auditing.
+         *
+         *     ⚠️ __Deprecated__: Use [`DELETE /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}`](#tag/entitlements/delete/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}) instead.
          */
         delete: operations['deleteEntitlement'];
         options?: never;
@@ -1955,11 +2005,14 @@ export interface paths {
         };
         /**
          * Get subject entitlement history
+         * @deprecated
          * @description Returns historical balance and usage data for the entitlement. The queried history can span accross multiple reset events.
          *
          *     BurndownHistory returns a continous history of segments, where the segments are seperated by events that changed either the grant burndown priority or the usage period.
          *
          *     WindowedHistory returns windowed usage data for the period enriched with balance information and the list of grants that were being burnt down in that window.
+         *
+         *     ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/history`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/history) instead.
          */
         get: operations['getEntitlementHistory'];
         put?: never;
@@ -1981,9 +2034,12 @@ export interface paths {
         put?: never;
         /**
          * Reset subject entitlement
+         * @deprecated
          * @description Reset marks the start of a new usage period for the entitlement and initiates grant rollover. At the start of a period usage is zerod out and grants are rolled over based on their rollover settings. It would typically be synced with the subjects billing period to enforce usage based on their subscription.
          *
          *     Usage is automatically reset for metered entitlements based on their usage period, but this endpoint allows to manually reset it at any time. When doing so the period anchor of the entitlement can be changed if needed.
+         *
+         *     ⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/reset`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/reset) instead.
          */
         post: operations['resetEntitlementUsage'];
         delete?: never;
@@ -2398,8 +2454,8 @@ export interface paths {
             cookie?: never;
         };
         /**
-         * Get entitlement by id
-         * @description Get entitlement by id.
+         * Get entitlement by ID
+         * @description Get entitlement by ID.
          */
         get: operations['getEntitlementByIdV2'];
         put?: never;
@@ -4411,10 +4467,16 @@ export interface components {
              */
             op: 'unschedule_edit';
         };
-        /** @description Entitlement templates are used to define the entitlements of a plan.
-         *     Features are omitted from the entitlement template, as they are defined in the rate card. */
+        /**
+         * @deprecated
+         * @description Entitlement templates are used to define the entitlements of a plan.
+         *     Features are omitted from the entitlement template, as they are defined in the rate card.
+         */
         Entitlement: components['schemas']['EntitlementMetered'] | components['schemas']['EntitlementStatic'] | components['schemas']['EntitlementBoolean'];
-        /** @description Entitlement template of a boolean entitlement. */
+        /**
+         * @deprecated
+         * @description Entitlement template of a boolean entitlement.
+         */
         EntitlementBoolean: {
             /**
              * @description discriminator enum property added by openapi-typescript
@@ -4489,7 +4551,10 @@ export interface components {
             /** @description The defined usage period of the entitlement */
             usagePeriod?: components['schemas']['RecurringPeriod'];
         };
-        /** @description Create inputs for boolean entitlement */
+        /**
+         * @deprecated
+         * @description Create inputs for boolean entitlement
+         */
         EntitlementBooleanCreateInputs: {
             /**
              * @description The feature the subject is entitled to use.
@@ -4594,7 +4659,10 @@ export interface components {
         };
         /** @description Create inputs for entitlement */
         EntitlementCreateInputs: components['schemas']['EntitlementMeteredCreateInputs'] | components['schemas']['EntitlementStaticCreateInputs'] | components['schemas']['EntitlementBooleanCreateInputs'];
-        /** @description The grant. */
+        /**
+         * @deprecated
+         * @description The grant.
+         */
         EntitlementGrant: {
             /**
              * Creation Time
@@ -4703,7 +4771,10 @@ export interface components {
              */
             annotations?: components['schemas']['Annotations'];
         };
-        /** @description The grant creation input. */
+        /**
+         * @deprecated
+         * @description The grant creation input.
+         */
         EntitlementGrantCreateInput: {
             /**
              * Format: double
@@ -4923,8 +4994,11 @@ export interface components {
             /** @description The recurrence period of the grant. */
             recurrence?: components['schemas']['RecurringPeriod'];
         };
-        /** @description Metered entitlements are useful for many different use cases, from setting up usage based access to implementing complex credit systems.
-         *     Access is determined based on feature usage using a balance calculation (the "usage allowance" provided by the issued grants is "burnt down" by the usage). */
+        /**
+         * @deprecated
+         * @description Metered entitlements are useful for many different use cases, from setting up usage based access to implementing complex credit systems.
+         *     Access is determined based on feature usage using a balance calculation (the "usage allowance" provided by the issued grants is "burnt down" by the usage).
+         */
         EntitlementMetered: {
             /**
              * @description discriminator enum property added by openapi-typescript
@@ -5045,7 +5119,10 @@ export interface components {
             /** @description THe usage period of the entitlement. */
             readonly usagePeriod: components['schemas']['RecurringPeriod'];
         };
-        /** @description Create inpurs for metered entitlement */
+        /**
+         * @deprecated
+         * @description Create inpurs for metered entitlement
+         */
         EntitlementMeteredCreateInputs: {
             /**
              * @description The feature the subject is entitled to use.
@@ -5323,7 +5400,10 @@ export interface components {
             /** @description The items in the current page. */
             items: components['schemas']['Entitlement'][];
         };
-        /** @description A static entitlement. */
+        /**
+         * @deprecated
+         * @description A static entitlement.
+         */
         EntitlementStatic: {
             /**
              * @description discriminator enum property added by openapi-typescript
@@ -5404,7 +5484,10 @@ export interface components {
             /** @description The defined usage period of the entitlement */
             usagePeriod?: components['schemas']['RecurringPeriod'];
         };
-        /** @description Create inputs for static entitlement */
+        /**
+         * @deprecated
+         * @description Create inputs for static entitlement
+         */
         EntitlementStaticCreateInputs: {
             /**
              * @description The feature the subject is entitled to use.
@@ -5520,6 +5603,7 @@ export interface components {
             customerId: string;
         };
         /**
+         * @deprecated
          * @description Type of the entitlement.
          * @enum {string}
          */
@@ -5768,6 +5852,8 @@ export interface components {
              *     Useful if the meter scope is broader than what feature tracks.
              *     Example scenario would be a meter tracking all token use with groupBy fields for the model,
              *     then the feature could filter for model=gpt-4.
+             *
+             *     ⚠️ __Deprecated__: Use advancedMeterGroupByFilters instead
              * @example {
              *       "model": "gpt-4",
              *       "type": "input"
@@ -5831,6 +5917,8 @@ export interface components {
              *     Useful if the meter scope is broader than what feature tracks.
              *     Example scenario would be a meter tracking all token use with groupBy fields for the model,
              *     then the feature could filter for model=gpt-4.
+             *
+             *     ⚠️ __Deprecated__: Use advancedMeterGroupByFilters instead
              * @example {
              *       "model": "gpt-4",
              *       "type": "input"
@@ -10071,11 +10159,14 @@ export interface components {
             message?: string;
         };
         /**
+         * @deprecated
          * @description A subject is a unique identifier for a usage attribution by its key.
          *     Subjects only exist in the concept of metering.
          *     Subjects are optional to create and work as an enrichment for the subject key like displayName, metadata, etc.
          *     Subjects are useful when you are reporting usage events with your own database ID but want to enrich the subject with a human-readable name or metadata.
          *     For most use cases, a subject is equivalent to a customer.
+         *
+         *     ⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
          * @example {
          *       "createdAt": "2025-01-01T01:01:01.001Z",
          *       "updatedAt": "2025-02-01T01:01:01.001Z",
@@ -10158,7 +10249,10 @@ export interface components {
             stripeCustomerId?: string | null;
         };
         /**
+         * @deprecated
          * @description A subject is a unique identifier for a user or entity.
+         *
+         *     ⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
          * @example {
          *       "key": "customer-id",
          *       "displayName": "Customer Name",
@@ -11451,6 +11545,8 @@ export interface components {
          * @description Simple filter for group bys with exact match.
          *
          *     For example: ?filterGroupBy[vendor]=openai&filterGroupBy[model]=gpt-4-turbo
+         *
+         *     ⚠️ __Deprecated__: Use `advancedMeterGroupByFilters` instead
          */
         'MeterQuery.filterGroupBy': {
             [key: string]: string;
@@ -19447,6 +19543,8 @@ export interface operations {
                  * @description Simple filter for group bys with exact match.
                  *
                  *     For example: ?filterGroupBy[vendor]=openai&filterGroupBy[model]=gpt-4-turbo
+                 *
+                 *     ⚠️ __Deprecated__: Use `advancedMeterGroupByFilters` instead
                  */
                 filterGroupBy?: components['parameters']['MeterQuery.filterGroupBy'];
                 /** @description Optional advanced meter group by filters.
@@ -22430,6 +22528,8 @@ export interface operations {
                  * @description Simple filter for group bys with exact match.
                  *
                  *     For example: ?filterGroupBy[vendor]=openai&filterGroupBy[model]=gpt-4-turbo
+                 *
+                 *     ⚠️ __Deprecated__: Use `advancedMeterGroupByFilters` instead
                  */
                 filterGroupBy?: components['parameters']['MeterQuery.filterGroupBy'];
                 /** @description Optional advanced meter group by filters.

package/dist/src/zod/index.d.ts

@@ -2313,6 +2313,8 @@ export declare const uninstallAppParams: zod.ZodObject<{
 }>;
 /**
  * Update the Stripe API key.
+
+⚠️ __Deprecated__: Use [`PUT /api/v1/apps/{id}`](#tag/apps/put/api/v1/apps/{id}) instead.
  * @deprecated
  * @summary Update Stripe API key
  */
@@ -8620,6 +8622,9 @@ export declare const listCustomerSubscriptionsQueryParams: zod.ZodObject<{
  * List all entitlements for all the subjects and features. This endpoint is intended for administrative purposes only.
 To fetch the entitlements of a specific subject please use the /api/v1/subjects/{subjectKeyOrID}/entitlements endpoint.
 If page is provided that takes precedence and the paginated response is returned.
+
+⚠️ __Deprecated__: Use [`GET /api/v2/entitlements`](#tag/entitlements/get/api/v2/entitlements) instead.
+ * @deprecated
  * @summary List all entitlements
  */
 export declare const listEntitlementsQueryExcludeInactiveDefault: false;
@@ -8665,8 +8670,11 @@ export declare const listEntitlementsQueryParams: zod.ZodObject<{
     orderBy?: "createdAt" | "updatedAt" | undefined;
 }>;
 /**
- * Get entitlement by id.
- * @summary Get entitlement by id
+ * Get entitlement by ID.
+
+⚠️ __Deprecated__: Use [`GET /api/v2/entitlements/{entitlementId}`](#tag/entitlements/get/api/v2/entitlements/{entitlementId}) instead.
+ * @deprecated
+ * @summary Get entitlement by ID
  */
 export declare const getEntitlementByIdPathEntitlementIdRegExp: RegExp;
 export declare const getEntitlementByIdParams: zod.ZodObject<{
@@ -8961,6 +8969,9 @@ export declare const deleteFeatureParams: zod.ZodObject<{
  * List all grants for all the subjects and entitlements. This endpoint is intended for administrative purposes only.
 To fetch the grants of a specific entitlement please use the /api/v1/subjects/{subjectKeyOrID}/entitlements/{entitlementOrFeatureID}/grants endpoint.
 If page is provided that takes precedence and the paginated response is returned.
+
+⚠️ __Deprecated__: Use [`GET /api/v2/grants`](#tag/entitlements/get/api/v2/grants) instead.
+ * @deprecated
  * @summary List grants
  */
 export declare const listGrantsQueryIncludeDeletedDefault: false;
@@ -9005,6 +9016,9 @@ export declare const listGrantsQueryParams: zod.ZodObject<{
 /**
  * Voiding a grant means it is no longer valid, it doesn't take part in further balance calculations. Voiding a grant does not retroactively take effect, meaning any usage that has already been attributed to the grant will remain, but future usage cannot be burnt down from the grant.
 For example, if you have a single grant for your metered entitlement with an initial amount of 100, and so far 60 usage has been metered, the grant (and the entitlement itself) would have a balance of 40. If you then void that grant, balance becomes 0, but the 60 previous usage will not be affected.
+
+⚠️ __Deprecated__: Use [`DELETE /api/v2/grants/{grantId}`](#tag/entitlements/delete/api/v2/grants/{grantId}) instead.
+ * @deprecated
  * @summary Void grant
  */
 export declare const voidGrantParams: zod.ZodObject<{
@@ -13404,6 +13418,9 @@ export declare const createStripeCheckoutSessionBody: zod.ZodObject<{
 
 If the subject doesn't exist, it will be created.
 If the subject exists, it will be partially updated with the provided fields.
+
+⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
+ * @deprecated
  * @summary Upsert subject
  */
 export declare const upsertSubjectBodyItem: zod.ZodObject<{
@@ -13452,6 +13469,9 @@ export declare const upsertSubjectBody: zod.ZodArray<zod.ZodObject<{
 }>, "many">;
 /**
  * Get subject by ID or key.
+
+⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
+ * @deprecated
  * @summary Get subject
  */
 export declare const getSubjectParams: zod.ZodObject<{
@@ -13463,6 +13483,9 @@ export declare const getSubjectParams: zod.ZodObject<{
 }>;
 /**
  * Delete subject by ID or key.
+
+⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
+ * @deprecated
  * @summary Delete subject
  */
 export declare const deleteSubjectParams: zod.ZodObject<{
@@ -13482,6 +13505,9 @@ export declare const deleteSubjectParams: zod.ZodObject<{
 A given subject can only have one active (non-deleted) entitlement per featureKey. If you try to create a new entitlement for a featureKey that already has an active entitlement, the request will fail with a 409 error.
 
 Once an entitlement is created you cannot modify it, only delete it.
+
+⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements) instead.
+ * @deprecated
  * @summary Create a subject entitlement
  */
 export declare const createEntitlementParams: zod.ZodObject<{
@@ -13632,6 +13658,9 @@ export declare const createEntitlementBody: zod.ZodUnion<[zod.ZodObject<{
 }>]>;
 /**
  * List all entitlements for a subject. For checking entitlement access, use the /value endpoint instead.
+
+⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements) instead.
+ * @deprecated
  * @summary List subject entitlements
  */
 export declare const listSubjectEntitlementsParams: zod.ZodObject<{
@@ -13651,6 +13680,9 @@ export declare const listSubjectEntitlementsQueryParams: zod.ZodObject<{
 }>;
 /**
  * List all grants issued for an entitlement. The entitlement can be defined either by its id or featureKey.
+
+⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants) instead.
+ * @deprecated
  * @summary List subject entitlement grants
  */
 export declare const listEntitlementGrantsParams: zod.ZodObject<{
@@ -13686,6 +13718,9 @@ Grants can have a recurrence setting intended to automate the manual reissuing o
 Rollover settings define what happens to the remaining balance of a grant at a reset. Balance_After_Reset = MIN(MaxRolloverAmount, MAX(Balance_Before_Reset, MinRolloverAmount))
 
 Grants cannot be changed once created, only deleted. This is to ensure that balance is deterministic regardless of when it is queried.
+
+⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants) instead.
+ * @deprecated
  * @summary Create subject entitlement grant
  */
 export declare const createGrantParams: zod.ZodObject<{
@@ -13766,6 +13801,9 @@ export declare const createGrantBody: zod.ZodObject<{
  * Overriding an entitlement creates a new entitlement from the provided inputs and soft deletes the previous entitlement for the provided subject-feature pair. If the previous entitlement is already deleted or otherwise doesnt exist, the override will fail.
 
 This endpoint is useful for upgrades, downgrades, or other changes to entitlements that require a new entitlement to be created with zero downtime.
+
+⚠️ __Deprecated__: Use [`PUT /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/override`](#tag/entitlements/put/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/override) instead.
+ * @deprecated
  * @summary Override subject entitlement
  */
 export declare const overrideEntitlementParams: zod.ZodObject<{
@@ -13921,6 +13959,9 @@ export declare const overrideEntitlementBody: zod.ZodUnion<[zod.ZodObject<{
  * This endpoint should be used for access checks and enforcement. All entitlement types share the hasAccess property in their value response, but multiple other properties are returned based on the entitlement type.
 
 For convenience reasons, /value works with both entitlementId and featureKey.
+
+⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/value`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/value) instead.
+ * @deprecated
  * @summary Get subject entitlement value
  */
 export declare const getEntitlementValueParams: zod.ZodObject<{
@@ -13942,6 +13983,9 @@ export declare const getEntitlementValueQueryParams: zod.ZodObject<{
 }>;
 /**
  * Get entitlement by id. For checking entitlement access, use the /value endpoint instead.
+
+⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}) instead.
+ * @deprecated
  * @summary Get subject entitlement
  */
 export declare const getEntitlementParams: zod.ZodObject<{
@@ -13957,6 +14001,9 @@ export declare const getEntitlementParams: zod.ZodObject<{
 /**
  * Deleting an entitlement revokes access to the associated feature. As a single subject can only have one entitlement per featureKey, when "migrating" features you have to delete the old entitlements as well.
 As access and status checks can be historical queries, deleting an entitlement populates the deletedAt timestamp. When queried for a time before that, the entitlement is still considered active, you cannot have retroactive changes to access, which is important for, among other things, auditing.
+
+⚠️ __Deprecated__: Use [`DELETE /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}`](#tag/entitlements/delete/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}) instead.
+ * @deprecated
  * @summary Delete subject entitlement
  */
 export declare const deleteEntitlementParams: zod.ZodObject<{
@@ -13975,6 +14022,9 @@ export declare const deleteEntitlementParams: zod.ZodObject<{
 BurndownHistory returns a continous history of segments, where the segments are seperated by events that changed either the grant burndown priority or the usage period.
 
 WindowedHistory returns windowed usage data for the period enriched with balance information and the list of grants that were being burnt down in that window.
+
+⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/history`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/history) instead.
+ * @deprecated
  * @summary Get subject entitlement history
  */
 export declare const getEntitlementHistoryParams: zod.ZodObject<{
@@ -14008,6 +14058,9 @@ export declare const getEntitlementHistoryQueryParams: zod.ZodObject<{
  * Reset marks the start of a new usage period for the entitlement and initiates grant rollover. At the start of a period usage is zerod out and grants are rolled over based on their rollover settings. It would typically be synced with the subjects billing period to enforce usage based on their subscription.
 
 Usage is automatically reset for metered entitlements based on their usage period, but this endpoint allows to manually reset it at any time. When doing so the period anchor of the entitlement can be changed if needed.
+
+⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/reset`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/reset) instead.
+ * @deprecated
  * @summary Reset subject entitlement
  */
 export declare const resetEntitlementUsageParams: zod.ZodObject<{
@@ -19914,8 +19967,8 @@ export declare const listEntitlementsV2QueryParams: zod.ZodObject<{
     customerKeys?: string[] | undefined;
 }>;
 /**
- * Get entitlement by id.
- * @summary Get entitlement by id
+ * Get entitlement by ID.
+ * @summary Get entitlement by ID
  */
 export declare const getEntitlementByIdV2PathEntitlementIdRegExp: RegExp;
 export declare const getEntitlementByIdV2Params: zod.ZodObject<{