# Project Setup
source: https://developer.mastercard.com/consent-management/documentation/tutorials/project-setup/index.md

This guide walks through the steps required to create a new Consents API project and gain access to the Sandbox environment.

## Create a Project {#create-a-project}

To begin, enter the dashboard by clicking "My Projects" in the menu section. Create a new project by clicking "Create New Project" in the upper right corner of the screen.

![Create New Project](https://static.developer.mastercard.com/content/consent-management/documentation/tutorials/images/create-new-project.png "Create New Project")

## Name Your Project {#name-your-project}

Give the project a name

![Project Name](https://static.developer.mastercard.com/content/consent-management/documentation/tutorials/images/project-name-consents.png "Project Name")

1. Enter a descriptive name for your project
2. You also have the choice to build the project on behalf of a client.

## Add the Consents API to Your Project {#add-the-consents-api-to-your-project}

Select the Consents API.

![Add Consents API](https://static.developer.mastercard.com/content/consent-management/documentation/tutorials/images/select-consent-api.png "Add Consents API")

1. From the dropdown list select the Consents API.
2. Click Continue.

## OAUTH Project Key and Encryption {#oauth-project-key-and-encryption}

Enter a key alias and a keystore password.

![Sandbox Cert](https://static.developer.mastercard.com/content/consent-management/documentation/tutorials/images/create-key.png "Sandbox Cert")

1. Make a note of the keystore password and key alias shown on the screen. The keystore password is used in conjunction with the .p12 file and Client ID for OAuth authentication.
2. Click create project.

![Download keyfile](https://static.developer.mastercard.com/content/consent-management/documentation/tutorials/images/download-key.png "Download keyfile")

3. Click Download key file which is required for OAuth authentication in Sandbox.
4. You can now open your project.

Note: Mastercard APIs use OAuth 1.0a with a request body hash as the security standard. The PKCS#12 keystore contains the private key used for signing requests. The key downloaded from our portal will have been generated inside your browser and will not be stored by Mastercard Developers. The public key matching the generated private key will be uploaded to Mastercard Developers for signature verification purposes as part of the process. Make sure to keep this file in a secure place. For more details please check [Mastercard OAuth1.0 page](https://developer.mastercard.com/platform/documentation/security-and-authentication/using-oauth-1a-to-access-mastercard-apis/).

## Summary Page {#summary-page}

![Results](https://static.developer.mastercard.com/content/consent-management/documentation/tutorials/images/results-consents.png "Results")

You should now have Consents APIs in your Project APIs. You can also check the Sandbox credentials on the left column to view and manage your project key. You can also manage your API keys in the credentials page.

*** ** * ** ***