Airapi User Guide
  • πŸ“™What is Airapi?
  • πŸ“˜Getting Started
    • Manage Environment
      • What is an Environment?
      • Add a New Environment
      • Update Environment
        • Reset Environment Cache
      • Delete Environment
      • Dashboard
      • Messages
      • Configurations
      • Endpoints
      • Applications
      • Documents
      • Agreements
      • Account Settings
    • Create Your Account
      • Verify Email
      • Forget Password
  • πŸ“—Management Portal
    • API Definition
      • Consent Management
      • Scope Management
  • πŸ“•Quota Management
    • Quota Management
    • API Base Quota
    • Application Base Quota
    • Domain Base Quota
  • πŸ“”UK Open Banking
    • Account Details
    • Regular Payments
  • πŸ“’TCMB Standard
    • Hata KodlarΔ±
  • πŸ““Advanced Features
    • App To App Authentication
    • mutual TLS
  • πŸ“–How to
    • How To Get a Client Credential Token?
    • How To Get an AppToApp Token?
    • How To Add Multiple Function Policy?
    • How To Add Data Mask Policy?
    • How To Create a New Tenant User?
    • How To Configure Developer Portal?
    • How To Modify Global Rate Limit?
    • How To Retire an API?
    • How To Reject a Payment Initiation?
    • How To Add a Global Variable?
    • How To Restrict Working Hours?
    • How To Track Gateway Error?
    • How To Export/Import Endpoints?
    • How To Reject Account Consent?
    • How To Exclude an Endpoint?
    • How To Define an Endpoint?
    • How To Define a Mock Policy?
    • How To Define a Rate Limit Policy?
    • How To Define a Mail Policy?
    • How To Transform a Header?
    • How To XML to JSON?
    • How To JSON to XML?
  • πŸ“™Release Notes
    • Versions
    • v2.1.80
    • v2.1.76
    • v2.1.72
    • v2.1.68
    • v2.1.64
    • v2.1.60
    • v2.1.56
    • v2.1.52
    • v2.1.44
    • v2.1.36
    • v2.1.20
    • v2.1.16
    • v2.0.96
    • v2.0.80
    • v2.0.72
    • v2.0.70
    • v2.0.66
    • v2.0.60
    • v2.0.55
    • v2.0.51
    • v2.0.50
    • v1.9.47
    • v1.9.46
    • v1.9.45
    • v1.9.44
    • v1.9.43
    • v1.9.42
    • v1.9.41
    • v1.9.40
    • v1.9.39
    • v1.9.38
    • v1.9.37
    • v1.9.3
    • v1.9.2
    • v1.9.1
    • v1.8.8
    • v1.8.7
    • v1.8.6
    • v1.8.5
    • v1.8.4
    • v1.8.3
    • v1.8.2
    • v1.8.1
    • v1.8.0
    • v1.7.9
    • v1.7.8
    • v1.7.7
    • v1.7.6
    • v1.7.5
    • v1.7.4
    • v1.7.3
    • v1.7.2
    • v1.7.1
    • v1.7.0
    • v1.6.9
    • v1.6.8
    • v1.6.7
    • v1.6.5
    • v1.6.2
    • v1.6.0
    • v1.5.8
    • v1.5.6
    • v1.5.4
    • v1.5
    • v1.4.6
    • v1.4.3
    • v1.4.0
    • v1.3.0
    • v1.2.1
    • v1.1.1
    • v0.8.6
  • βš™οΈPlanned Activities
Powered by GitBook
On this page
  1. Quota Management

Application Base Quota

PreviousAPI Base QuotaNextDomain Base Quota

Last updated 2 years ago

Client applications are needed to access API resources within the scope of OAuth2.0. ApiGo is a powerful API management application and powerfully responds to end-to-end API management needs of any organizations. Developers who want to access API resources can become members by using the developer portal provided by ApiGo to companies and can access API resources by creating one or more applications. With ApiGo, you can assign quotas for API access to applications created in the system. This is a feature that will be especially useful in your B2B structures. For one enterprise integration, you can set permission for 10,000 API calls per month, while for another enterprise integration, you can set permission for 1,000 requests per month.

Advantages

  • It provides a great advantage especially in meeting B2B needs.

  • It prevents complexity and provides a simple architecture.

Disadvantages

  • It does not allow to make quota application specific to API alone.

How to configure Application Based Quota?

You can access the application-based quota management by clicking the Applications menu on the left menu of the ApiGo management portal, to the list of applications defined in the system. From this list, find the application you want to apply the quota for and click the edit link.

After that, the application detail page will open. At the bottom of this screen, click on the Show Advanced Settings link.

There are special settings you can assign for this application on the Advanced Settings screen. From these settings, the Usage Quota feature can be clicked and a configuration can be defined as follows. This configuration is only valid for this application (Client) and other clients are not affected by this quota.

The parameters specified in the Usage Quota definition and their explanations are as follows.

  • Enable Usage Quata: It is used to activate or deactivate the quota application for this application.

  • Max request per period: defines how many requests can be made for this API in a given period below.

  • Quota reset every: It is used to determine what the quota period is. 4 different periods can be defined as Day, Week, Month and Year.

  • Error Message: What should be the response message that the API will produce in case of exceeding the quota.

Requests made to all APIs defined in the system are evaluated as a whole. That is, all calls to one or more of the APIs defined in the system are included in the quota calculation. When the total access amount is accessed, a response is generated by ApiGo, as in the example, and the application request is returned.

πŸ“•
Edit Application detail
Postman Request sample
Advanced Settings
List applications on ApiGo