# Register a dApp

## dApp registration

Once you are registered in **CKBull Developer Console**, you can start adding your dApps to the console. On the main page, next to **Your dApps,** click the button **Create new dApp.** This action will redirect you to the dApp creation form which should look like the following image.

<figure><img src="https://4100684485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPlB1oN5qXYGlSUWHxkql%2Fuploads%2Fgit-blob-694cbd2b32bf07590c85db5a699f027ad859a171%2FScreenshot%202023-06-28%20at%2011.58.16.png?alt=media" alt=""><figcaption></figcaption></figure>

Once you have added all the necessary information, click the **Create application** button at the bottom of the form. Your dApp is now registered in the platform.

{% hint style="warning" %}
Be aware that the dApp **name**, **description** and **logo** will be displayed in the **CKBull Wallet** every time a sign in request is scanned.
{% endhint %}

<figure><img src="https://4100684485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPlB1oN5qXYGlSUWHxkql%2Fuploads%2Fgit-blob-462c3083cdc3e78886fd6e0f7abe8ed7bcb43e88%2FIMG_9800.PNG?alt=media" alt="" width="375"><figcaption><p>Sign in request data</p></figcaption></figure>

## dApp API keys

You will notice that after creating your dApp a modal is displayed. This modal contains the API keys that will let the dApp connect with the Signer API to send transactions.

{% hint style="danger" %}
Your API Keys **must never be shared**. They may impersonate the dApp and send malicious queries if they are leaked. In that case, see how you can [**regenerate new API keys**](https://docs.ckbull.app/getting-started/regenerate-api-keys).
{% endhint %}

<figure><img src="https://4100684485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPlB1oN5qXYGlSUWHxkql%2Fuploads%2Fgit-blob-103206e84afb56b93a9ad2733276949d4a969641%2FScreenshot%202023-04-19%20at%2012.20.17.png?alt=media" alt=""><figcaption></figcaption></figure>
