---
schema_version: "1"
id: e1cc77d58291f54eb242e9ec1de5c3223d4508ab5489a6db20cd44694751ee53
title: SLA Tiers For API Groups
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-manager/latest/api-groups-sla-tiers.md
canonical_url: https://docs.mulesoft.com/api-manager/latest/api-groups-sla-tiers
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 09387adc2c545e596999e6d9769e8289cc68cc3e5108f0e42e9e7ad48aae6304
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: API Manager
version: 2.x
is-latest-version: true
---

# SLA Tiers For API Groups

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

As a Group Administrator, you can specify service-level agreement (SLA) tiers for API Groups
instances to limit the number of requests an application (user) can make to the APIs in an API
Group. SLAs enable you to protect your API Group instances and help manage network traffic to your
APIs.

The SLA tier definition also determines whether access to the API Groups instance requires your
approval. You can configure manual or automatic approvals to requests.

## SLA Types

SLA tiers are of two types:

- [Default SLAs](#default_SLAs)

- [Individual SLAs](#individual_SLAs)

## Default SLAs

The default limit applies to all API instances. This means that the same SLA limit is applicable to
every API instance in that API Group.

If you add a new API instance to an API Group instance, the default limit SLA configured at the
group instance level applies, unless an individual API SLA tier is also configured by the Group
Administrator.

## Individual SLAs

As a Group Administrator, you can define individual limits for API instances within an API Group
instance. If you have configured a default SLA limit at the API Group instance level and an
individual SLA limit at the API instance level, the individual SLA overrides the default limit.

If no individual SLA is configured, then the default SLA limit is enforced for that API instance.

If the Rate Limiting policy is applied on an API instance, as a Group Administrator you must
determine if the new SLA can be fulfilled by the underlying API instance.

## Manual and Automatic Approvals

When you configure automatic approvals for an SLA tier, requests made to the API instances with that
tier applied are automatically approved. Consumers can instantaneously use API Group instances in
this case.

Manual approvals are routed through a manual approval flow, where the API Group owner must manually
approve the consumer request.

## Layered SLAs

API Groups supports multiple SLA limits. You can set multiple throughput limits for a single SLA
tier. A single SLA tier named `Premium` can limit requests to 100 per second as well as limiting
requests to 10,000 per day.

This strategy ensures that applications registered on a `Premium` tier do not exceed the top limit
of 100 requests per second. This way, applications do not inundate the API, and registered
applications get the expected 10,000 requests per day.

## See Also

- [API Groups](https://docs.mulesoft.com/api-manager/latest/api-groups-landing-page)

- [Add SLA Tiers to API Groups](https://docs.mulesoft.com/api-manager/latest/api-groups-add-sla-tiers)

- [Remove SLA Tiers from API Groups](https://docs.mulesoft.com/api-manager/latest/api-groups-remove-sla-tier)

- [Manage Group Instance Contracts](https://docs.mulesoft.com/api-manager/latest/api-groups-manage-api-group-instance-contracts)