--- schema_version: "1" id: 6ebe86ce567c43efbf6baa1c9b17f20c4ae3c510922211af024c24ded35c3f02 title: Manage Client Applications and Contracts collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-community-manager/client-apps-contracts.md canonical_url: https://docs.mulesoft.com/api-community-manager/client-apps-contracts source_site: docs.mulesoft.com content_type: documentation content_hash: 3d4bf272eb8293662502a33e766508b0cb47e1d368b4261282e5cc452d12bfec description: MuleSoft Documentation Site latest: true --- --- product: API Community Manager --- # Manage Client Applications and Contracts > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can enable your consumer developers to request access to APIs and API Groups in your community and to manage their client applications and contracts. ## API Access Use the [API Access Requester](https://docs.mulesoft.com/api-community-manager/acm-lightning-components#api-access-requester) Lightning component on an API details page to enable consumer developers to request a contract with the corresponding API or API Group. The component allows a developer to select: - An instance of the API or API Group, from the available instances in Anypoint API Manager that have public visibility in Anypoint Exchange - A service-level agreement (SLA) tier, if the selected API or API Group instance has SLA tiers defined in API Manager - A client application, either existing or new To display an API or API group instance in your site, either [set its visibility to public in Exchange](https://docs.mulesoft.com/exchange/to-configure-api-settings), or open the API Community Manager control panel, and in the API curator, set the API or API group’s instances visibility to **All instances**. If you don’t see **API Community Manager** in **App Launcher**, follow [Enable API Community Manager Control Panel](https://docs.mulesoft.com/api-community-manager/manual-setup#enable-api-community-manager-control-panel). When a consumer developer creates a new application, they can provide an additional description. If the API or API Group uses OAuth 2.0 authentication, the consumer developer can provide an OAuth 2.0 redirect URI. When a consumer developer requests access for a new client application to an API instance that has an identity provider (IDP), the consumer developer must specify one or more of the OAuth 2.0 grant types Authorization Code Grant, Implicit Grant, Refresh Token, and Resource Owner Grant. Some IDPs do not support all grant types. Requesting access and specifying an unsupported grant type shows the error `Error creating application.` If the Anypoint organization is configured to use external identity for client applications, then new client applications are created in the corresponding identity provider [according to the environment of the selected API or API Group instance](https://docs.mulesoft.com/api-manager/latest/configure-multiple-credential-providers). When a consumer developer selects an existing client application for a contract, only client applications with the same identity provider as the selected API or API Group instance are available to select. When a consumer developer selects an existing client application, the consumer developer sees all the client applications that their user account has permissions to see in the Anypoint Platform. This includes the client applications created by this user, and also any other client applications that are visible to this user through roles, permissions, or client application ownership assignment in API Manager. Client applications and contracts requested through Anypoint API Community Manager are created in API Manager. Depending on the SLA tier configuration, they are approved automatically or they require approval by the owner of the API or API Group. To review and approve contracts, refer to [the API Manager documentation](https://docs.mulesoft.com/api-manager/latest/manage-client-apps-latest-task). You can define a custom process or workflow to create client applications and contracts with the Salesforce Approval Process, Salesforce Lightning Flow, or custom Lightning components and Apex code. These approaches use the API Community Manager external objects to interact with the Anypoint Platform through the data bridge, so the same principles and operation apply. ## Managing Client Apps and Contracts If a consumer developer has access to a client application or contract in your API Community, then the **Application Listing**, **Application Details** and **Application Analytics Graph** Lightning components display detailed information to them about the client application or contract. The [Application Listing](https://docs.mulesoft.com/api-community-manager/acm-lightning-components#application-listing) component shows a consumer developer a list of all the applications that their user account in the Anypoint Platform can access. The list includes the client applications created by this user through your community, and also any other client application that this user can access, including client applications where this user has been assigned as owner in API Manager, and other client applications visible through user roles and permissions. Each item in the application listing component has a **Delete** option, and a **View** option which shows an application details page for the application. The application details page uses the [Application Details](https://docs.mulesoft.com/api-community-manager/acm-lightning-components#application-details) component to show the application’s credentials, an option to reset the credentials, the application’s contracts, and an option to change the SLA tier of each contract. The application details page can include the [Application Analytics Graph](https://docs.mulesoft.com/api-community-manager/acm-lightning-components#application-analytics-graph) component, which shows an activity chart with an individual client application’s throughput and response time metrics.