> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/notifications/basic-notifications/find-sha-1-key.md).

# Find SHA-1 key

### How to find the SHA-1 key of my app?

The SHA-1 key is a unique certificate fingerprint generated for your app. It is required for enabling features like Google logins and push notifications. AppMySite automatically generates the SHA-1 key when you enable these features.

#### Steps to follow

{% embed url="<https://scribehow.com/viewer/Find_SHA-1_key__7W1g5PTnQzOOUomqeVGO9w>" %}

**Step 1: Go to your app dashboard**

* Log in to your AppMySite account.
* Select the app for which you need the SHA-1 key.

**Step 2: Enable the required feature**

* Go to [**Access > Login**](https://app.appmysite.com/app/login/build-settings) (for social login) or [**Notifications > Basic**](https://app.appmysite.com/app/notifications/build-settings) (for push notifications), depending on what you want to connect.
* Click on Build settings.
* Turn on Social login or Basic notifications.
* Click on the Generate button to create the SHA-1 key.

Step 3: Copy the SHA-1 key

* Once generated, the SHA-1 code will be displayed on the screen.

{% hint style="warning" %}
It may take a few minutes to generate the SHA key.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/app/notifications/basic-notifications/find-sha-1-key.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.