> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/administrator-settings/configuring-apis/manage-apps.md). # Manage Apps In the emSigner application for integrating any source application and to make the API calls, the Source Sytem should get the request authenticated using the App Name and Secret Key. Below are the steps to create App Name and Secret Key **Step 1:** Login into the Administrator account and click on the "Settings" tab.

**Step 2:** Navigate to "Manage Apps" under "API Settings."

Step 3: The list of all the existing Apps will be shown in this grid. Click "Create New" to create a new app.

**Step 4:** Provide App Name and clik on "Generate SecretKey".

**Step 5:** Once the Secret Key is generated, click on Save to save the details.

**Step 6:** The created app can be seen on the Manage Apps grid. The created apps can be deleted or edited by clicking on the bin and pen icons under the Actions.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.emsigner.com/administrator-settings/configuring-apis/manage-apps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.