--- schema_version: "1" id: a89666bc6d68c75d1acf3a05bbc5094d5374c8defebeceab79ef480855203389 title: CLI for API Manager collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-cli/latest/api-mgr.md canonical_url: https://docs.mulesoft.com/anypoint-cli/latest/api-mgr source_site: docs.mulesoft.com content_type: documentation content_hash: ddc84f05ba345abacdb2e1622f9323e3babf892c4660330684150db2db4fc8eb description: MuleSoft Documentation Site release: 4.x latest: true --- --- product: Anypoint CLI version: 4.x is-latest-version: true --- # CLI for API Manager > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use the `api-mgr` commands to automate your API Manager processes. For more information about how to use these commands, refer to the [API Manager documentation](https://docs.mulesoft.com/api-manager/latest/).
CommandDescription

Creates an API instance alert

Lists alerts for an API instance

Lists the autodiscovery properties

Changes the asset version for an API instance by choosing a new version from Exchange

Classifies an API instance in a given environment

Deletes an API

Deploys an API to CloudHub, CloudHub2, Hybrid Server, or Runtime Fabric

Deprecates an API instance

Shows details of an API

Downloads the API proxy ZIP file to a local directory

Edits an API instance

Lists all APIs in API Manager 2.x

Manages a new API, API version, or new API instance with an asset from Exchange

Promotes an API instance from source environment

Redeploys an API to CloudHub, CloudHub2, Hybrid Server, or Runtime Fabric

Undeprecates an API instance

Adds an owner to a client application

Imports a client application from an external client identity provider

Lists possible owners for a client application in the current organization

Lists client identity providers with import enabled in the current organization

Deletes a given API contract

Lists all contracts to a given API instance

Applies a policy to a given API instance

Shows the description and available configuration properties of a given policy template

Disables policy from a given API instance

Edits the policy configuration of a given API instance

Enables a policy on a given API instance

Lists policies

Removes a policy from a given API instance

Creates an SLA tier

Copies an SLA tier from source to a target API instance

Deletes an SLA tier from an API instance

Lists the SLA tiers of an API instance

Creates an upstream for an API instance

Bulk edits the TLS context for all upstreams of an API instance

Deletes an upstream from an API instance

Edits an upstream of an API instance

Lists all upstreams for an API instance

## api-mgr:alert:add \> api-mgr:alert:add \[flags\] Creates an API instance alert with the name passed in `name` for the API instance ID passed in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--duration

Condition occurrence period duration.

--duration 60

--durationUnit

Condition occurrence period duration unit.
Supported values: days, hours, and minutes.

--durationUnit minutes

--email

Email to send alert notification to.
Pass this flag multiple times to specify multiple emails.

--enabled

Sets whether the alert is enabled. Include the flag to enable the alert.

--enabled

--operator

Condition operator that explains values in relation to threshold.
Supported values: gt, lt, eq.

--operator gt

--output

Specifies the response format, supported values are table (default) and json

--output json

--periods

Number of consecutive periods condition should occur for.

--periods 34

--policyId

ID of a policy applied to the API instance that triggers a policy-violation alert type.

--policyId http-basic-authentication

--recipient

Username to send alert notification to.
Pass this flag multiple times to specify multiple usernames.

--recipient mulesoftuser

--responseCode

Response codes to trigger response-code alert type.
Pass this flag multiple times to specify multiple codes.

--responseCode 400

--responseTime

Response time to trigger response-time alert type.

--responseTime 60

--severity

Alert severity.
Supported values: Info, Warning, Critical.

--severity Critical

--threshold

Condition occurrences threshold number.

--threshold 3

--type

Alert type/condition.
Supported values: request-count, response-code, policy-violation, response-time

--type response-code

> [!NOTE] This command has multi-option flags. When using multi-option flags in a command, either > put the parameter before the flags or use a \`-- \` (two dashes followed by a space) before the > parameter. ## api-mgr:alert:list \> api-mgr:alert:list \[flags\] Lists alerts for the API instance passed in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--limit

Number of results to retrieve, default is 10 results

--limit 5

--offset

Offsets the amount of APIs passed

--offset 3

--output

Specifies the response format
Supported values are table (default) and json

--output json

--sort

Sorts the results in the field name passed
Supported values are: id, name, createdDate, and updatedDate

--sort name

## api-mgr:api:autodiscovery \> api-mgr:api:autodiscovery \[flags\] This command lists the autodiscovery properties required for a gateway to track the API Instance Id passed in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--gatewayVersion

Specifies the gateway version to download

--gatewayVersion 4.0.1 643404 /tmp/

--output

Specifies the response format
Supported values are table (default) and json

--output table

## api-mgr:api:change-specification \> api-mgr:api:change-specification \[flags\] Changes the asset version for the API instance passed in `` by choosing a new version from Exchange passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:api:classify \> api-mgr:api:classify \[flags\] Classifies the API instance passed in `` in the environment passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:api:delete \> api-mgr:api:delete \[flags\] Deletes the API instance passed in ``. If the API instance is deployed, this command undeploys the API instance before deleting it. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:api:deploy \> api-mgr:api:deploy \[flags\] Deploys the API instance passed in '' to the deployment target specified using the flags described next. Deploy any undeployed API using this command regardless of whether it was created using the API Manager CLI or API Manager UI. > [!NOTE] This command is only supported for endpoints with proxy. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--applicationName

Application name

--applicationName myMuleApp 643404

--environmentName

Target environment name, only for when deploying API instances from unclassified environments

--environmentName TestEnv 643404

--gatewayVersion

The CloudHub Gateway version

--gatewayVersion: 9.9.9.9 643404

--javaVersion

Gateway Java version
This flag only works if the target flag was set as RTF, CH, or CH2

--javaVersion 17 643404

--releaseChannel

Set the name of the release channel to be used for the selected Mule version. + Supported values are NONE, EDGE, and LTS
This flag only works if the target flag was set as RTF, CH, or CH2

--releaseChannel EDGE 643404

--overwrite

Update application if it exists
Include the flag to enable it

--overwrite

--output

Specifies the response format, supported values are table (default) and json

--output json

--target

Hybrid, RTF, CH, or CH2 deployment target ID

--target 1598794 643404

## api-mgr:api:deprecate \> api-mgr:api:deprecate \[flags\] Deprecates the API instance passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:api:describe \> api-mgr:api:describe \[flags\] Shows details of the API instance passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:api:download-proxy \> api-mgr:api:download-proxy \[flags\] This command downloads the API proxy ZIP file of the API instance passed in `` to a local directory specified in ``. You cannot download the API proxy of an Omni Gateway API instance. This command accepts the `--gatewayVersion` flag to specify the gateway version to download. For example: `api-mgr:api:download-proxy --gatewayVersion: 4.0.1 643404 /tmp/` This command also accepts the `--output` flag to specify the response format Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:api:edit \> api-mgr:api:edit \[flag\] Edits the API instance passed in ``. Editing a deployed Omni Gateway API instance redeploys the instance. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

-f, --isFlex

Indicates whether this is an Omni Gateway API instance.
Include the flag to enable it

--isFlex

-m, --muleVersion4OrAbove

Indicates whether this is a Mule 4 API instance.
Include the flag to enable it

--muleVersionOrAbove

-p, --withProxy

Indicates whether the endpoint should use a proxy.
Include the flag to enable it

--withProxy

-r, --referencesUserDomain

Indicates whether a proxy should reference a user domain.
Include the flag to enable it

--referencesUserDomain

--apiInstanceLabel

API instance label

--apiInstanceLabel exampleLabel

--deploymentType

Deployment type
Options: cloudhub, hybrid, rtf (required)

--deploymentType cloudhub

--endpointUri

Consumer endpoint URI (required)

--endpointUri /udp://localhost:65432

--inboundSecretGroupId

Inbound secret group ID

--inboundSecretGroupId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--inboundTlsContextId

Outbound TLS context ID
Supply the --inboundSecretGroupId of the TLS context’s secret group. To remove a TLS context, apply the flag with the following value: --inboundTlsContextId "null".

--inboundTlsContextId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--outboundSecretGroupId

Outbound secret group ID.

--outboundSecretGroupId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--outboundTlsContextId

Outbound TLS context ID.
Supply the --outboundSecretGroupId of the TLS context’s secret group. To remove a TLS context, apply the flag with the following value: --outboundTlsContextId "null".

--outboundTlsContextId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--output

Specifies the response format, supported values are table (default) and json

--output json

--path

Proxy path (required)

--path /http://localhost:3000

--port

Proxy port (required)

--port 8080

--providerId

Client Identity Provider Id that the API is associated with
Default is Anypoint Platform Client Provider

--providerId 1787c36ab544466698e380131040faad

--responseTimeout

Maximum response timeout(required)

--responseTimeout 10

--routing

API instance routes as a JSON array. Each route defines a label, routing rules, and upstream references with weights.

--routing '[{"label":"Rule 1","rules":{"path":"/path"},"upstreams":[{"id":"upstream-id","weight":100}]}]'

--scheme

Proxy scheme (required)
Supported values: http, https.

--scheme http

--serviceName

WSDL service name
Omni Gateway does not support this flag

--serviceName ExampleServerName

--serviceNamespace

WSDL service namespace. Omni Gateway does not support this flag.

--serviceNamespace exampleServiceName

--servicePort

WSDL service port
Omni Gateway does not support this flag

--servicePort 443

--type

Endpoint type
Supported options: http, raml, wsdl, mcp, a2a, llm, grpc

--type http

--updateApisInSamePort

Updates the TLS context of API instances sharing the port of this API.

--updateApisInSamePort

--uri

Implementation URI.

--uri /udp://localhost:65432

## api-mgr:api:list \> api-mgr:api:list \[flags\] Lists all APIs in API Manager 2.x. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--apiVersion

API version that filters results

--apiVersion 1.0.2

--assetId

Asset ID that filters results

--assetId ([group_id]/)<asset_id>/<version>

--instanceLabel

API instance label that filters results

--instanceLabel exampleLabel

--limit

Number of results to retrieve

--limit 50

--offset

Offsets the amount of APIs passed

--offset 3

--output

Specifies the response format, supported values are table (default) and json

--output json

--sort

Sorts the results in the field name passed
Supported values are: id, name, createdDate, and updatedDate

--sort updatedDate

## api-mgr:api:manage \> api-mgr:api:manage \[flags\] Manages a new API, API version, or new API instance with the Exchange asset passed in ``, and the version passed in ``. > [!NOTE] Omni Gateway API instances created with Anypoint CLI do not support multiple upstream > services. To create Omni Gateway API instances with multiple upstream services, see: > > - [Add an API in Connected Mode](https://docs.mulesoft.com/api-manager/latest/create-instance-task-flex) > > - [Add an API in Local Mode](https://docs.mulesoft.com/gateway/latest/local-publish-api-multiple-services). In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

-f, --isFlex

Indicates whether this is an Omni Gateway API instance.
Include the flag to enable it

--isFlex

-m, --muleVersion4OrAbove

Indicates whether this is a Mule 4 API instance.
Include the flag to enable it

--muleVersionOrAbove

-p, --withProxy

Indicates whether the endpoint should use a proxy.
Include the flag to enable it

--withProxy

-r, --referencesUserDomain

Indicates whether a proxy should reference a user domain.
Include the flag to enable it

--referencesUserDomain

`--apiInstanceLabel `

API instance label

--apiInstanceLabel exampleLabel

--deploymentType

Deployment type
Options: cloudhub2, cloudhub, hybrid, rtf (required)

--deploymentType hybrid

--endpointUri

Consumer endpoint URI (required)

--endpointUri /udp://localhost:65432

--inboundSecretGroupId

Inbound secret group ID

--inboundSecretGroupId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--inboundTlsContextId

Outbound TLS Context ID
Supply the --inboundSecretGroupId of the TLS Context’s secret group. To remove a TLS Context, apply the flag with the following value: --inboundTlsContextId "null".

--inboundTlsContextId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--outboundSecretGroupId

Outbound secret group ID.

--outboundSecretGroupId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--outboundTlsContextId

Outbound TLS context ID.
Supply the --outboundSecretGroupId of the TLS context’s secret group. To remove a TLS context, apply the flag with the following value: --outboundTlsContextId "null".

--outboundTlsContextId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--output

Specifies the response format, supported values are table (default) and json

--output json

--path

Proxy path (required)

--path /http://localhost:3000

--port

Proxy port (required)

--port 8080

--providerId

Client Identity Provider Id that the API is associated with
Default is Anypoint Platform Client Provider

--providerId 1787c36ab544466698e380131040faad

--responseTimeout

Maximum response timeout(required)

--responseTimeout 10

--scheme

Proxy scheme (required)
Supported values: http, https.

--scheme http

--serviceName

WSDL service name
Omni Gateway does not support this flag

--serviceName ExampleServerName

--serviceNamespace

WSDL service namespace. Omni Gateway does not support this flag.

--serviceNamespace exampleServiceName

--servicePort

WSDL service port
Omni Gateway does not support this flag

--servicePort 443

--type

Endpoint type
Supported options: http, raml, wsdl, mcp, a2a, llm, grpc

--type http

--uri

Implementation URI

--uri /udp://localhost:65432

## api-mgr:api:promote \> api-mgr:api:promote \[flags\] Promotes the API instance passed in `` from the source environment in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

-a, --copyAlerts

Indicates whether to copy alerts
Include the flag to enable it

--copyAlerts

-p, --copyPolicies

Indicates whether to copy policies
Include the flag to enable it

--copyPolicies

-t, --copyTiers

Indicates whether to copy tiers
Include the flag to enable it

--copyTiers

--output

Specifies the response format, supported values are table (default) and json

--output json

--providerId

Indicates the provider’s ID associated with the API.

--providerId 1787c36ab544466698e380131040faad

## api-mgr:api:redeploy \> api-mgr:api:redeploy \[flags\] Redeploys the API instance passed in `` to the deployment target set up in the flags described below. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--applicationName

Application name

--applicationName Muleapp 643404

--environmentName

Target environment name
Include to redeploy APIs from unclassified environments

--environmentName mulesoftEnvironment 643404

--gatewayVersion

CloudHub Gateway version

--gatewayVersion 9.9.9 643404

--javaVersion

Gateway Java version
This flag only works if the target flag was set as RTF, CH, or CH2

--javaVersion 17 643404

--overwrite

Update application if it exists
Include the flag to enable it

--overwrite

--output

Specifies the response format, supported values are table (default) and json

--output json

--releaseChannel

Set the name of the release channel to be used for the selected Mule version. + Supported values are NONE, EDGE, and LTS
This flag only works if the target flag was set as RTF, CH, or CH2

--releaseChannel EDGE 643404

--target

Hybrid, RTF, CH, or CH2 deployment target ID

--target 1598794 643404

## api-mgr:api:undeprecate \> api-mgr:api:undeprecate \[flags\] Undeprecates the API instance passed in ``. This commands accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:application:add-owner \> api-mgr:application:add-owner \[flags\] Adds the owner passed in `` with the entity type passed in `` to the client application passed in ``. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:application:import \> api-mgr:application:import \[flags\] Imports the client application passed in `` from the external client identity provider passed in ``. The client identity provider must have the import feature enabled. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--description

Description of the client application to import.

--description "Example application description"

--url

URL of the client application to import.

## api-mgr:application:possible-owners-list \> api-mgr:application:possible-owners-list \[flags\] Lists the possible owners for a client application in the current organization. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--search

Search string to filter results.

--search example

--limit

Number of results to retrieve.

--limit 10

--offset

Number of results to skip.

--offset 10

## api-mgr:client-provider:list-importable \> api-mgr:client-provider:list-importable \[flags\] Lists the client identity providers that have the import feature enabled in the current organization. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:contract:delete \> api-mgr:contract:delete \[flags\] This command deletes the contract between the API instance passed in ``, and the client passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:contract:list \> api-mgr:contract:list \[flags\] \[searchText\] Lists all contracts of the API passed in ``. > [!TIP] You can specify keywords in searchText to limit results of APIs containing those specific > keywords. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--limit

Number of results to retrieve

--limit 2

--offset

Offsets the amount of APIs passed

--offset 3

--output

Specifies the response format, supported values are table (default) and json

--output json

--sort

Sorts the contracts by the criteria associated with their client applications
Supported values are: id, name, createdDate, and updatedDate

--sort id

## api-mgr:policy:apply \> api-mgr:policy:apply \[flags\] Applies the policy passed in `` to the API instance passed in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

-c, --config

Pass the configuration data as a JSON string

--config '{\"username\":\"user\",\"password\":\"teste\"}'

--configFile

Pass the configuration data as a file

--configFile ./config.json

--groupId

Mule 4 policy group ID
This value defaults to the MuleSoft group ID.

--groupId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--output

Specifies the response format, supported values are table (default) and json

--output json

-p, --pointcut [dataJSON]

Pass pointcut data as JSON strings

--pointcut '[{"methodRegex":"GET|PUT","uriTemplateRegex":"/users*"}]'

--policyVersion

Mule 4 policy version.

--policyVersion 1.0.2

--upstreamId

Configure upstream

--upstreamId 550e8400-e29b-41d4-a716-446655440000

The following example defines a rate limit of one request every ten seconds: { "rateLimits": \[{ "maximumRequests": 1, "timePeriodInMilliseconds": 10000 }\], "clusterizable": true, "exposeHeaders": false } > [!NOTE] Even if you plan to use the default values, you must configure all required policy > parameters when applying a policy with Anypoint CLI, ## api-mgr:policy:describe \> api-mgr:policy:describe \[flags\] Shows the description and available base configuration properties of the policy name passed in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--groupId

Mule 4 policy group ID

+ Defaults to the MuleSoft group ID.

--groupId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--policyVersion

Mule 4 policy version

--policyVersion 1.0.2

--output

Specifies the response format
Supported values are table (default) and json.

--output json

## api-mgr:policy:disable \> api-mgr:policy:disable \[flags\] Disables the policy passed in `` from the API instance passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:policy:edit \> api-mgr:policy:edit \[flags\] Edits the policy configuration passed in `` for the API instance passed in ``. > [!NOTE] If you are udpating an included Mule Gateway policy, you can include only the changed > values in the configuration. However, if you are updating a custom policy, you must send the full > configuration each time a custom policy is edited. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

-c, --config

Pass the configuration data as a JSON string

--config '{\"username\":\"user\",\"password\":\"teste\"}'

--configFile

Pass the configuration data as a file

--configFile ./config.json

--output

Specifies the response format, supported values are table (default) and json

--output json

-p, --pointcut

Pass pointcut data as JSON strings

-p '[{"methodRegex":"GET|PUT","uriTemplateRegex":"/users*"}]'

## api-mgr:policy:enable \> api-mgr:policy:enable \[flags\] Enables the policy passed in `` for the API instance passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:policy:list \> api-mgr:policy:list \[flags\] \[apiInstanceId\] Lists all policies for all APIs in API Manager 2.x. Specify the `--apiInstanceId` flag to list the policies applied to that API instance. Without the `--apiInstanceId` flag, the command lists all policies for all APIs. This command accepts the `-m, --muleVersion4OrAbove` flag. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:policy:remove \> api-mgr:policy:remove \[flags\] This command removes the policy specified in `` from the API instance passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:tier:add \> api-mgr:tier:add \[flags\] This command creates an SLA tier for the API instance passed in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

-a, --autoApprove

Indicates whether the SAL tier should be auto-approved
Include the flag to enable it

--autoApprove

--name

Tier name

--name muleSLAtier

--description

Tier description

--description tier example description

-l, --limit

Single instance of an SLA tier limit in the form --limit A,B,C where:

  • A is a boolean indicating whether this limit is visible to the user.

  • B is a number of requests per "C" time period.

  • C is the time period unit. Time period options are:

    • ms(millisecond)

    • sec(second)

    • min(minute)

    • hr(hour)

    • d(day)

    • wk(week)

    • mo(month)

    • yr(year)

--limit true,100,min

To create multiple limits, you can provide multiple --limit options.
For example: -l true,100,sec -l false,20,min.

--output

Specifies the response format, supported values are table (default) and json

--output json

## api-mgr:tier:copy \> api-mgr:tier:copy \[flags\] Copies the SLA tier from the API instance passed in `` to the API instance Id passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:tier:delete \> api-mgr:tier:delete \[flags\] This command deletes the SLA tier passed in `` from API instance passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:tier:list \> api-mgr:tier:list \[flags\] \[searchText\] This command lists the SLA tiers of the API instance passed in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--limit

Number of results to retrieve

--limit 2

--offset

Offsets the amount of APIs passed

--offset 3

--output

Specifies the response format, supported values are table (default) and json

--output json

--sort

Sorts the results in the field name passed
Supported values are: id, name, createdDate, and updatedDate

--sort id

## api-mgr:upstream:add \> api-mgr:upstream:add \[flags\] Creates an upstream for the API instance passed in `` with the URI passed in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts these flags:
FlagDescriptionExample

--label

Label for the upstream

--label my-upstream

--tlsContextId

TLS context ID to set on the upstream

--tlsContextId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--tlsContextSecretGroupId

Secret group ID for the TLS context specified in --tlsContextId

--tlsContextSecretGroupId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--output

Format for the response, supported values are table (default) and json

--output json

## api-mgr:upstream:bulk-edit \> api-mgr:upstream:bulk-edit \[flags\] Bulk edits the TLS context for all upstreams of the API instance passed in `` using a single API update. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts these flags:
FlagDescriptionExample

--tlsContextId (required)

TLS context ID to set on all upstreams. Pass null to remove the TLS context from all upstreams.

--tlsContextId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--tlsContextSecretGroupId

Secret group ID for the TLS context specified in --tlsContextId

--tlsContextSecretGroupId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--output

Format for the response, supported values are table (default) and json

--output json

## api-mgr:upstream:delete \> api-mgr:upstream:delete \[flags\] Deletes the upstream passed in `` from the API instance passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options). ## api-mgr:upstream:edit \> api-mgr:upstream:edit \[flags\] Edits the upstream passed in `` for the API instance passed in ``. In addition to the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options), this command accepts the following flags:
FlagDescriptionExample

--uri

Upstream URI

--label

Label for the upstream

--label my-upstream

--tlsContextId

TLS context ID to set on the upstream. Pass null to remove the TLS context.

--tlsContextId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--tlsContextSecretGroupId

Secret group ID for the TLS context specified in --tlsContextId

--tlsContextSecretGroupId 1fec0a49-1551-4199-bfcc-cf0352d0f29d

--output

Format for the response, supported values are table (default) and json

--output json

## api-mgr:upstream:list \> api-mgr:upstream:list \[flags\] Lists all upstreams for the API instance passed in ``. This command accepts the `--output` flag to specify the response format. Supported values are `table` (default) and `json`. This command accepts the [default flags](https://docs.mulesoft.com/anypoint-cli/latest/#default-options).