Abstract
In some implementations, the techniques described herein relate to a method including: receiving, at an API gateway, an API request from an API client; extracting, by the API gateway, a client identity associated with the API request; checking, by the API gateway, API Level Objectives (ALOs) associated with the client identity, the ALOs defining acceptable usage limits for the client identity; determining, by the API gateway, that the API request falls outside the acceptable usage limits defined by the ALOs; and applying, by the API gateway, an API Level Agreement (ALA) action, the ALA action specifying an action to be taken when an ALO is breached.
Full Text
What is claimed is:
In some implementations, the techniques described herein relate to a method including: receiving, at an API gateway, an API request from an API client; extracting, by the API gateway, a client identity associated with the API request; checking, by the API gateway, API Level Objectives (ALOs) associated with the client identity, the ALOs defining acceptable usage limits for the client identity; determining, by the API gateway, that the API request falls outside the acceptable usage limits defined by the ALOs; and applying, by the API gateway, an API Level Agreement (ALA) action, the ALA action specifying an action to be taken when an ALO is breached.
Timeline
Filed
05/12/2026Published
09/10/2026Granted
Not AvailableIPC Codes(3)
H04L 41/5009:Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
H04L 9/40:Network security protocols
H04L 67/02:based on web technology, e.g. hypertext transfer protocol [HTTP]