Technical setup

Before you begin

Before starting, you need the following:

• Super admin access to your reseller domain. For more information, see how to access the Cloud Channel API.

• Access to the Google Cloud console and the Partner Sales Console.

Step 1: Prepare the Partner Sales Console

Before you can use the API, you must accept the terms and conditions of the Channel Services platform.

Log in to the Partner Sales Console at least once as an administrator of the reseller domain. The first time you sign in, you must accept the reseller terms of service, if applicable. If you accepted specific terms of service offline, this step isn't applicable to you.

You can accept additional terms of service on the Terms page of the Partner Sales Console.

Note: You need your Account ID, found in the Partner Sales Console Settings page, for API integration.

Step 2: Configure your Google Cloud project

To use any Google API, you must have a Google Cloud project.

Create a Google Cloud project

To create a project, navigate to the Projects area of your Google Cloud console and click Create Project.

For more detailed instructions on creating a project, and for a list of best practices, see our Creating and managing projects guide.

Most resellers create Google Cloud projects under their main Google Cloud organization instead of under the reseller domain. Accessing data from the reseller domain is granted by setting up domain-wide delegation to let a service account access data from the reseller domain.

Give the project a descriptive name. The project ID is an arbitrary identifier that does not affect your ability to call the Cloud Channel API.

Enable the API

Navigate to the API Library section in the Google Cloud console and enable the Cloud Channel API.

Create a service account

To create your service account, go to the Service accounts page.

Go to Service accounts

1. Click Create Service Account.
2. Enter the Service account name (and optional Service account description) then click Create.
3. Click Continue to skip the Grant service account access to project option.
4. Skip the Grant users access to this service account section and click Done to finish account creation.

After you create your account, create a service account key:

1. In the Google Cloud console, click the email address for the service account that you created.
2. Click Keys.
3. Click Add key, then click Create new key.

4. Click Create. A JSON key file is downloaded to your computer.

   Make sure to store the key file securely, because it can be used to authenticate as your service account. You can move and rename this file however you would like.

5. Click Close.

You can delete and create private key files from the Service accounts page.

Step 3: Authorize the service account for the reseller domain

You need your service account's Client ID for this section. From the Actions menu, select Manage details and copy your Unique ID.

Go to the Domain-wide delegation page using your reseller domain's super-admin account.

• Click Add new and enter your service account's ID in the Client ID field.
• Enter https://www.googleapis.com/auth/apps.order in the OAuth Scopes field.
• Click Authorize to allow your service account to use the Cloud Channel API in the context of your Channel Services account.

Note: If you use additional APIs in your final integration, you might have more than one scope for your service account's client.

Then click Authorize so your service account can use the Cloud Channel API in the context of your Channel Services account.

Note: You might have to enable more APIs and add more scopes in other codelabs. Your final integration might have more than one scope for your service account's client.

Next steps

Now that you have an initial technical integration, you can discover the API by reading the Cloud Channel API documentation.

Note: If you also have a Test Partner Sales Console, follow steps one through four with your test reseller domain. Make sure to create a separate project since Google APIs have per-project quotas. Sharing a project across environments might cause your test accounts to impact the quotas on your production account.