Deprecated and Removed
Version 2026.10.0
REMOVED FEATURESWARNING! The Token Quotas screen and the budgets it saved are removed: the organization AI budget, the AI proxy application budget, the anonymous budget of the AI proxy routing, the project budget, and the default and default anonymous budgets in AI Gateway Settings. The upgrade removes the stored values. It does not convert them into Limit Plans. Recreate each limit as an AI Token Limit plan or as AI Proxy Protection in the Token Rate Limit policy. Export packages and APIops requests that still carry these fields are accepted. Apinizer ignores the fields and keeps the rest. See
WARNING! The APIops /ai-budgets endpoints (scope rules, hierarchy, effective limit and budget update) are removed. Use the Limit Plans endpoints instead. See
WARNING! The default budget fields of AI Gateway Settings, the application budget and routing anonymous budget fields of an API proxy, and the budget field of a project are removed from the Management API. See
WARNING! The AI Budget Source setting and the AI token budget of each environment on an API proxy access row are removed. See
WARNING! The Project and Platform Limits screen and the project and platform limit assignments are removed, for API Request Count and for AI Token Limit. A Limit Plan can be assigned to a consumer, an API client, an application, an organization, an API proxy (AI Gateway) or an audience rule. The gateways no longer enforce project or platform assignments. On upgrade, every project and platform assignment that was not ended is ended, and every enabled AI Token Usage Percentage alarm with the Project scope is disabled. The alarm is kept. Change its scope to AI Gateway and enable it again. The Manager REST API and the Management API refuse a new project or platform assignment, and a package import skips such an assignment file. See
WARNING! The model catalog and the separate Models page are removed. A model is now managed only inside its LLM provider. The provider definitions (the Definitions tab, custom provider definitions and Clone from Catalog) and the built-in seeded models and prices are removed too. See
WARNING! The allow-list of models of an LLM provider (Allowed at gateway) and the model lifecycle (the deprecated flag and Sunset At) are removed. Use the Enabled switch of a model instead. After the upgrade every existing model is switched on.
WARNING! The Model Definition export and import type and the APIops /llm-models endpoints are removed. The models travel inside their LLM provider. The allowedModelIds and providerDefinitionId fields of the LLM provider payloads are removed. See
WARNING! The typed access model is removed. Access is defined only on the ACL (the Access Control screen). The access entitlements and the API client authorization restrictions (Follow the owner, Deny all, Allow a subset) no longer exist, and nothing is carried over from them. See Authorization of an API Client.
WARNING! The Authorization tab of the API client, and the client mode, access and reach badges and columns of the Access Control screen, are removed.
WARNING! The access-entitlement REST endpoints and the API client restriction endpoints (authorization-restrictions) are removed. The APIops /entitlements sub-resources of consumers, applications and API clients, and the API client restriction section of APIops, are removed too. See
WARNING! The Access Entitlement (ACCESS_ENTITLEMENT) export and import type is removed. An old package that still contains such files imports normally; each file is skipped with the advisory accessEntitlement.removed.
WARNING! The Rate Limit Control List screen is deprecated. It is a read-only screen with a Deprecated badge under Identity Management and Administration → Identity Management. You can only view a list and delete it; deleting a list does not change the limit plan that was made from it. Manage every limit with Limit Plans. A create or update through the management API is rejected with the error credentialRateLimit.retired. See
WARNING! The APIops /credentials/ and /credential-organizations/ endpoints are deprecated. They still work. Every response carries a Deprecation header and a Link header with rel="successor-version" that points to /consumers or /consumer-organizations. Move your automation to the new endpoints. See
WARNING! The APIops ignores an unknown field in a request body. From version 2027.01.0, a request body with an unknown field will be rejected with 400, the error will name the field, and nothing will be saved. The fields that a read returns will still be accepted. Check the field names of your automation against the API Reference before you upgrade.
Version 2026.09.3
REMOVED FEATURESWARNING! The Rate Limit Control List screen has been removed from the project and Administration menus. The records had already been converted into Limit Plans and assignments at upgrade; every limit is now managed from Limit Plans, which is also available under Administration → Identity Management for system administrators. Legacy records stay readable through the management API. See
WARNING! The Inherit limit assignment mode has been retired. The gateway never resolved it — an Inherit assignment behaved exactly like Off — so it is no longer offered on the Limits tab, and existing Inherit assignments are converted to Off at upgrade. Gateway behaviour is unchanged. Use an organization's Default Limit Plans to give new consumers a starting limit. See
Version 2026.09.2
REMOVED FEATURESWARNING! The Rate Limit Control List has been retired; the gateway no longer evaluates these records. Your existing records were converted automatically into Limit Plans and assignments on upgrade, and the screen is kept read-only for viewing and deleting only. See
WARNING! The environment-scoped quota and throttling fields on an API Proxy and API Proxy Group's access permissions are no longer enforced by the gateway; your existing values were converted automatically into Limit Plans and assignments on upgrade. See
Version 2026.04.0
REMOVED FEATURESWARNING! Automatic deletion of audit logs and ACL audit logs through Cleanup Tasks has been removed. These logs are critical for compliance and should not be deleted automatically. Manual cleanup scripts are available in the database growth management documentation. See
WARNING! The option to disable writing audit and login logs to the database in General Settings has been removed. These logs are now always recorded in the database.
Version 2025.11.0
REMOVED FEATURESWARNING! In Management APIs, the relativePath field has been replaced with the clientRoute field in Create/Update API Proxy APIs. Users utilizing proxy management APIs in CI/CD processes should pay attention to this field. See
Version 2025.04.0
REMOVED FEATURESWARNING! The feature to update applications through the application has been removed.
WARNING! The integration with Opsgenie product has been removed due to its termination by Jira.
Version 2025.01.4
FEATURES TO BE REMOVED- The feature to update applications through the application will be removed in the next release version.
- Opsgenie integration will be removed in the next release version.
- The Client Banner feature will be removed from the Routing section in the next release version. This feature will now be managed directly through the policy.
Version 2024.09.0
FEATURES TO BE REMOVEDWARNING! Due to the requirement for data owners to control the deletion of log records, the automatic deletion of log records with retention period in Monitor Screens, Application Logs, API Integration, and Reports pages has been removed. Purge scripts have been prepared for manual deletion of these records from the database. See
IMPORTANT! Snapshot policy screens used for automatic backup of Elasticsearch indices through Apinizer screens have been removed due to snapshot policy usage requirements. Necessary scripts have been prepared for manual execution of these operations. See
WARNING! All features related to the old revision logic have been removed due to usage difficulties. Now, completely switched to the "Deployment History" application started in Version 2023.06.1. Revision parameters in Apinizer Management APIs have also been removed. See
Version 2024.05.3
REMOVED FEATURESWARNING Multiple API Proxy selection has been enabled in API Proxy Group. With this setting, the feature of applying policies in API Proxy Group to API Proxies has been removed as it existed before. See
From now on, policies in API Proxy Group will only be applied to requests coming to API Proxy Group, if a request comes directly to API Proxy and this API Proxy is included in API Proxy Group, policies in API Proxy Group will not be executed in this case.
Version 2024.05.0
REMOVED FEATURESWARNING! Simple method has been removed from LDAP settings in general settings. See
Version 2024.01.1
REMOVED FEATURESWARNING The feature of subjecting the value found with variable to URL decode operation at the time it is found has been removed. If this need exists, URL decode should be done with business rule.
Version 2023.03.1
REMOVED FEATURES- The option to Load from Spec for creating API Proxy in Swagger and Open API types has been removed.
- JWT 3rd Party policy has been removed because JOSE Validation policy included JWT 3rd Party policy.
- Due to the arrangement made with APNZ-3472, the feature to configure log settings on API Proxy Group basis has been removed.
- Due to the arrangement made with APNZ-3472, the Project Log Settings screen has been removed.
- Due to the arrangement made with APNZ-3472, the feature to set the severity level of log settings on a general settings basis has been removed.
Version 2022.12.1
REMOVED FEATURES- Type value (Prod, Test, Sandbox) has been removed from Environment.