# Quick Start Guide
source: https://developer.mastercard.com/account-catalog-services/documentation/quick-start-guide/index.md

## Overview {#overview}

Use this guide to go from account setup to your first successful Sandbox request for Account Catalog Services. You will create a project, generate credentials, make a test call, and prepare the same project for Production access.

### Before you begin {#before-you-begin}

* Create a [Mastercard Developers](https://developer.mastercard.com/) account.
* Have a secure place to store downloaded OAuth and encryption keys.
* Decide how you want to test: Insomnia, the reference application, or your own client.
* Have an OAuth 1.0a signing method ready, such as a Mastercard OAuth library or a configured Insomnia workspace.

### Sandbox checklist {#sandbox-checklist}

| # |      Step      |                                                                                        What to do                                                                                         |
|---|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | Access         | Get access to Account Catalog Services and create your Mastercard Developers project.                                                                                                     |
| 2 | Credentials    | Generate your Sandbox OAuth credentials and record your consumer key.                                                                                                                     |
| 3 | Environment    | Confirm that you are using the Sandbox base URL and that your project is still in Sandbox mode.                                                                                           |
| 4 | Authentication | Configure OAuth 1.0a signing for the first request and confirm which consumer key and private key pair you will use.                                                                      |
| 5 | Encryption     | Complete JWE setup in [API Basics](https://developer.mastercard.com/account-catalog-services/documentation/api-basics/index.md) before testing protected-payload flows.                   |
| 6 | First call     | Send your first Sandbox request using the Sandbox base URL and OAuth 1.0a signing.                                                                                                        |
| 7 | Validation     | Use the sample response and [Testing](https://developer.mastercard.com/account-catalog-services/documentation/testing/index.md) page to validate positive, negative, and follow-on flows. |

## Step 1: Get access to the API {#step-1-get-access-to-the-api}

1. Go to [Mastercard Developers](https://developer.mastercard.com/) and create an account.
2. Activate your account by opening the link sent to your email address, and log in.
3. Open your [My Projects](https://developer.mastercard.com/dashboard) page and start a new project. Sandbox access is open, so you can begin testing as soon as your project credentials are generated.

## Step 2: Create a project and generate Sandbox credentials {#step-2-create-a-project-and-generate-sandbox-credentials}

Create a Mastercard Developers project to generate your Sandbox credentials. Sandbox gives you mocked data so you can validate your integration before requesting Production access.

### Project Details {#project-details}

1. Click **Create new project** on your [My Projects](https://developer.mastercard.com/dashboard) page. ![create-project](https://static.developer.mastercard.com/content/account-catalog-services/uploads/create-project-new.png)
2. Enter a project name.
3. If prompted, indicate whether you are creating the project on behalf of a client.
4. In the 'Select at least one API' field, choose **Account Catalog Services**.

### Service Details {#service-details}

5. Complete the **Service details** form if it appears. Note: Some project flows include additional client or service fields. If you do not see them, continue to the next step.

### Project Credentials {#project-credentials}

6. In **Project Credentials** , select the `OAuth 1.0` radio button for this OAuth 1.0a service.
7. Create a key alias and keystore password for your OAuth keys, record them securely, and click **Proceed** . ![create-project](https://static.developer.mastercard.com/content/platform/img/create-project-oauth-project-key.png)

### Additional Credentials {#additional-credentials}

8. Generate your encryption keys. You can skip this step only if you are limiting your first Sandbox validation to unencrypted requests such as `GET /`.
9. Create a key alias and keystore password for your encryption keys, record them securely, and click **Create Project**.
10. Download the OAuth 1.0a and encryption keys and store them in a safe place. Then click 'Open Project'. ![create-project](https://static.developer.mastercard.com/content/platform/img/create-project-download-key.png)

### Save the values you will need {#save-the-values-you-will-need}

11. On the project dashboard, record the following values:

* Sandbox and Production status
* Authentication consumer key
* Client encryption key fingerprint

![add-api-service](https://static.developer.mastercard.com/content/account-catalog-services/uploads/acs-summary.png)

## Step 3: Confirm Sandbox configuration and make your first request {#step-3-confirm-sandbox-configuration-and-make-your-first-request}

Once you have Sandbox credentials, confirm the environment and configuration, then make a simple GET request to verify that your project is set up correctly.

### Sandbox environment and configuration {#sandbox-environment-and-configuration}

* Use the Sandbox base URL for the first call: `https://sandbox.api.mastercard.com/asc/acs-api`.
* Configure OAuth 1.0a signing for every request to this service.
* Keep your encryption setup ready for protected-payload flows, even if this first request uses an unencrypted GET endpoint. For the complete encryption configuration, see [API Basics](https://developer.mastercard.com/account-catalog-services/documentation/api-basics/index.md#transport-encryption).

Before you run the request, make sure you have:

* Your Sandbox consumer key
* The private key used to sign OAuth requests
* A Mastercard OAuth library or signer that generates `oauth_timestamp`, `oauth_nonce`, and `oauth_signature`

This first-call example uses `GET /account-registrations`, so you can verify access, OAuth signing, and the Sandbox base URL before moving on to encrypted flows.
Note: For a full client setup, including encryption configuration, see the [API Basics](https://developer.mastercard.com/account-catalog-services/documentation/api-basics/index.md) section.

#### Example Request (cURL): {#example-request-curl}

```bash
curl --request GET \
  --url 'https://sandbox.api.mastercard.com/asc/acs-api/account-registrations?correlation_id=<correlation_id>' \
  --header 'Authorization: OAuth oauth_consumer_key="<consumer_key>", oauth_signature_method="RSA-SHA256", oauth_timestamp="<timestamp>", oauth_nonce="<nonce>", oauth_version="1.0", oauth_signature="<signature>"'
```

> This example shows the required OAuth 1.0a header fields explicitly, but uses placeholders for sensitive values.
> Replace `YOUR_CONSUMER_KEY` with the consumer key from your project and generate `oauth_signature` with a Mastercard OAuth library. The library also handles `oauth_timestamp` and `oauth_nonce` for you.
>
> For step-by-step update examples that include `If-Match`, see the [Tutorials and Guides](https://developer.mastercard.com/account-catalog-services/documentation/tutorials-and-guides/index.md).

#### Expected Response: {#expected-response}

**For `200 ok`**
* JSON

```JSON
{
  "accountIdentifier": "5XXXXXXXXXX1111",
  "accountLevelManagement": {
    "productRules": [
      {
        "productRuleId": "f84a1902-428c-44d9-8f9d-0a0652a15670",
        "actionCodes": [],
        "rejectCodes": []
      }
    ]
  }
}
```

**For `404 not found`**
* JSON

```JSON
{
  "Errors": {
    "Error": [
      {
        "Source": "Account-Catalog-Services",
        "ReasonCode": "R0009206",
        "Description": "No data found for the specified 'correlation_id'.",
        "Recoverable": false
      }
    ]
  }
}
```

### What success looks like {#what-success-looks-like}

* Replace the placeholder values (\<correlation_id\>, \<consumer_key\>, , , and ) with your actual values.
* The request returns `200 OK` when the `correlation_id` is valid.
* If the `correlation_id` is invalid, the request returns an error response.
* The response body contains JSON with account-level management details and product rules.
* Please refer to the testing section for additional details about the response object.

> **Test data:** The sandbox includes pre-loaded available data. For a negative-flow test, pass an invalid status value, such as incorrect correlation id. The API returns a `404 Bad Request` with a `BAD_REQUEST` reason code. See [Testing](https://developer.mastercard.com/account-catalog-services/documentation/testing/index.md) for additional scenarios.

## Step 4: Choose how you want to test and integrate {#step-4-choose-how-you-want-to-test-and-integrate}

After the first Sandbox request succeeds, pick the integration path that matches your workflow:

* **Reference Application:** Use the [Reference Application](https://developer.mastercard.com/account-catalog-services/documentation/developer-tools/reference-app/index.md) page.
* **curl or a custom client:** Use the [Testing](https://developer.mastercard.com/account-catalog-services/documentation/testing/index.md) page for test cases and additional examples.

## Step 5: Promote the same project to Production {#step-5-promote-the-same-project-to-production}

Once your project is working in Sandbox, request Production access for that same project.

### Transition your project from Sandbox to Production {#transition-your-project-from-sandbox-to-production}

1. **Open your project in Mastercard Developers** :
   Go to your [My Projects](https://developer.mastercard.com/dashboard) page and open the Account Catalog Services project you used for Sandbox testing.

2. **Request Production access for that project** :
   In the project dashboard, select **Request Production Access** . Your Sandbox and Production statuses are shown separately on the project page, so you can track when Production moves from `Not Requested` to an enabled `Ready` state.

3. **Generate or download your Production keys**:
   After Production access is approved, download the Production OAuth and encryption keys for the same project. Keep the Production key material separate from your Sandbox keys.

4. **Update your application configuration**:
   Switch the base URL from Sandbox to Production:

   * Sandbox: `https://sandbox.api.mastercard.com/asc/acs-api`
   * Production: `https://api.mastercard.com/asc/acs-api`

   Update your application to use the Production consumer key, signing key, and encryption certificates.

Note: OAuth 1.0a authentication and JWE payload encryption work the same way in Sandbox and Production. The main changes are the Production key set, the Production approval state, and the Production base URL.

If you need the full onboarding process, including contract, MTF, SLA, and escalation details, see the [Onboarding Checklist](https://developer.mastercard.com/account-catalog-services/documentation/onboarding-checklist/index.md).

## Next Steps {#next-steps}

Continue with the documentation that matches your next task:

* [API Reference](https://developer.mastercard.com/account-catalog-services/documentation/api-reference/index.md) for endpoint details.
* [API Basics](https://developer.mastercard.com/account-catalog-services/documentation/api-basics/index.md) for authentication, encryption, and client configuration.
* [Testing](https://developer.mastercard.com/account-catalog-services/documentation/testing/index.md) for additional request scenarios.
* [Onboarding Checklist](https://developer.mastercard.com/account-catalog-services/documentation/onboarding-checklist/index.md) for the full operational go-live process.