API Proxy ACL
Consumer access permission alone is not sufficient for API proxy access.
For the settings in the consumer and access permission to be valid, one of the authentication policies must be added on the API Proxy and the Security Manager option must be selected as the authentication method in this policy.
On this page, all API Proxies belonging to the project in which the authorized application user is included are listed as shown in the image below, and can be filtered optionally.
API Proxy Access Permission Management
To perform operations on an API Proxy, go to the detail screen of the relevant API Proxy by pressing the button marked in red above.
This screen contains the list of Consumers that have been previously granted access permission for the API Proxy.
To add a new Consumer, press the button marked in red in the image above.
When the Add button is pressed, consumers defined within the project or defined from the management menu are listed as shown in the image below.
On this screen, access permission for one or more consumers to the API Proxy can be granted at the same time.
Consumer Configuration
After granting access permission to the consumer for the API Proxy, return to the page with the list of consumers that have been granted access permission to the API Proxy:
To make API Proxy-specific settings for the consumer, press the Edit button marked in red on this page.
Configuration Parameters
As of 2026.09, the gateway no longer reads the Environment Quota / Environment Throttling fields below (or their Message Count/Interval/Window Type/Counting Mode/Limit Change Action details), nor the environment's own Enable AI Token Budget field and its budget values — on upgrade, every existing value here was converted automatically into a typed Limit Plan and assignment; see Legacy Limits Migrated at Upgrade and, for the AI budget specifically, AI Budgets. These fields remain visible below as a read-only audit trail; edit the migrated ceiling going forward on the consumer's Limits tab or the Token Quotas screen. The access fields — Expires On, Environment List (enabled/disabled), Disallowed Methods, AI Model Access, and AI Budget Source — are unaffected and keep controlling access exactly as before; AI Budget Source in particular still decides whether the organization-level AI budget chain applies to this row.
The fields used for access configuration are shown in the table below:
| Field | Description |
|---|---|
| Expires On (Expires On) | If this date value is entered, the Consumer will no longer be able to access the API Proxy from the time this date arrives (valid from midnight 00:00). If left empty, it continues to access the API Proxy as long as it does not become inactive. The arrival of this date only restricts access to this API Proxy, it does not make any change in access to other API Proxies. |
| Environment List (Environment List) | Enables entering Quota and Throttling values specific to the environment where the API Proxy is deployed. |
| Environment Quota (Quota) | The quota value specific to the specified environment of the API Proxy. |
| Environment Throttling (Throttling) | The throttling value specific to the specified environment of the API Proxy. |
| Message Count (Message Count) | The maximum number of messages that can be sent to the Backend API within the time given with the Throttling Interval. |
| Interval Time Amount (Interval Time Amount) | A numeric value indicating the duration of the limitation window in the selected time unit. |
| Interval Time Unit (Interval Time Unit) | The time interval unit used for API request limitation (for example, second, minute). |
| Interval Window Type (Interval Window Type) | The time interval method used for API request limitation (fixed or sliding). |
| Quota Counting Mode (Quota Counting Mode) | Determines whether requests rejected by the Quota limit still consume it. All requests (default): every request, accepted or rejected, increases the usage counter. Accepted only: only requests that pass the quota increase the usage counter. |
| Quota Limit Change Action (Quota Limit Change Action) | Determines what happens to the existing usage counter when the Quota value is changed. Clamp to previous limit (default): the counter is capped to the previous limit value, never the new one. Reset: the counter is reset to zero, but only when the limit is raised. Leave unchanged: the counter is left untouched. |
| Throttling Counting Mode (Throttling Counting Mode) | Determines whether requests rejected by the Throttling limit still consume it. All requests (default): every request, accepted or rejected, increases the usage counter. Accepted only: only requests that pass the limit increase the usage counter. |
| Throttling Limit Change Action (Throttling Limit Change Action) | Determines what happens to the existing usage counter when the Throttling value is changed. Clamp to previous limit (default): the counter is capped to the previous limit value, never the new one. Reset: the counter is reset to zero, but only when the limit is raised. Leave unchanged: the counter is left untouched. |
| Cache Connection Timeout (Second) (Cache Connection Timeout (Second)) | The timeout duration for cache connection is specified. |
| Action for Cache Connection Error (Action for Cache Connection Error) | The action to be applied if the policy experiences a connection problem with the cache server is specified. |
| Disallowed Methods (Disallowed Methods) | If it is desired that the consumer not access any method of the API Proxy regardless of the roles it has, the methods of the API Proxy that are desired to be closed to access are selected here. By default, the consumer can access all methods of the API Proxy. |
| AI Model Access (AI Model Access) | AI proxies only, per environment. When enabled, the consumer may call only the models listed under Allowed models on this proxy; requests for any other model are rejected by the gateway, including models reached through failover. When enabled with an empty list, no restriction is applied. |
| Allowed models (Allowed models) | The model ids the consumer may call when the restriction is enabled (for example gpt-4o). The same restriction can be set while granting access through APIops with the enabledAiModelRestriction and allowedAiModelIds fields; see Grant Access. |
| Save and Deploy Button (Save and Deploy) | After completing the settings/changes, press the Save and Deploy button to activate the settings. |
Uniqueness of Access Permissions
A consumer's access permission for a given API Proxy is held in a single record. Even if you stay on the screen and press Save and Deploy several times, no new record is created for the same permission; the record created by the first save is updated by the later ones.
Access permissions that arrive through an API Product subscription in the portal are the exception. Because those permissions are held against the subscribed product, the same consumer and the same API Proxy may be listed as separate records for different product subscriptions. Each record carries the quota and throttling values of its own product.
In versions before 2026.09.1 the same permission could be recreated on every save. When you upgrade to this version, existing duplicates are consolidated automatically: the oldest record is kept and the restrictions from the other copies are applied onto it (the earliest expiry date, the union of disallowed methods, and any environment disabled in any copy). Consolidation never widens access.
If you need to clean up without waiting for the upgrade, you can request the cleanup script from the Apinizer team.