# Register your app in Twilio Verification API

For Twilio Verification SDK for Android to receive SMSs without requesting sms read permissions you will need to register your hash so that Google Play Services will be able to route the SMS to your app.

This is the way Google Play Services redirects the SMS to the app without forcing it to request the `SMS_READ` permission.

![Twilio Verify SMS routing with hash code for app verification.](https://docs-resources.prod.twilio.com/0a5bd5399ca8b48b2939c5213420487d6ef34e386c2bbab23d82ffbf94f37ac1.png)

To obtain your app's hash you can use this script: [sms\_retriever\_hash\_v9.sh](/documents/sms_retriever_hash_v9.sh)

Usage:

```bash
./sms_retriever_hash_v9.sh --package package_name --keystore keystore_file
```

For example

```bash
./sms_retriever_hash_v9.sh --package com.package.name --keystore ./debug.keystore 
```

The script will prompt you to input the keystore password. For debug keystores the default password is `android`

This is the transformation the script does:

![Flowchart showing hash generation using Android keystore and app package name.](https://docs-resources.prod.twilio.com/b214571e340dac3ccb8e8eca42058374e9d36c1b7e0cc55afd4177d904c26fbc.png)

Once obtained, browse to the Twilio Console -> Verify -> (application) -> Settings and add the hash in the Android SDK Hash Signature field then save it:

![Input field for Android SDK hash signature registration.](https://docs-resources.prod.twilio.com/76d0e838da7f752b10388bcebbbc1c6d17753a41a4dcc4ec84796ca4c49718e0.png)

For more information about how to generate your app's hash string, check out Google's SMS retriever documentation

[https://developers.google.com/identity/sms-retriever/verify#computing\_your\_apps\_hash\_string](https://developers.google.com/identity/sms-retriever/verify#computing_your_apps_hash_string)
