Assignments Discovery Google

This document provides the background information you need to use the Google APIs Discovery Service.

  1. Introduction
  2. Before you start
  3. APIs Discovery Service background
    1. Concepts
    2. Data model
    3. Operations
  4. Calling style
    1. REST

Introduction

This document is intended for developers who want to write client libraries, IDE plugins, and other tools for interacting with Google APIs. The Google APIs Discovery Service supports tools like these by exposing machine readable metadata about various Google APIs through a simple API.

Before you start

If you are unfamiliar with Discovery concepts, you should read through this documentation, experiment with the API, and look at the samples before starting to code.

The APIs Discovery Service provides only public methods that do not require authentication. In addition, unlike the requests you make to many other Google APIs, the requests you make to the Discovery Service API does not necessarily need to include an API key.

APIs Discovery Service background

Concepts

The Google APIs Discovery Service is built upon two basic concepts:

  • APIs Directory: A list of all APIs that are supported by the APIs Discovery Service. Each directory entry shows details about a supported API, including its name, a brief description of what it does, and a link to its documentation. Each supported API can have multiple Directory entries, one for each of its supported versions.
  • Discovery document: A machine-readable description of a particular API. The Discovery document describes the surface for a particular version of an API. The document provides details on how to access the various methods of each API via RESTful HTTP calls. A Discovery document includes descriptions of the data and methods associated with the API, as well as information about available OAuth scopes, and descriptions of schemas, methods, parameters and available parameter values.

Data model

A resource is an individual data entity with a unique identifier. The Google APIs Discovery Service operates on two types of resources, based on the above concepts.

  • APIs Directory resource: Represents the set of supported APIs.

    A Directory entry for a specific API version contains four types of information:

    • Identification and description information, including name, version, title, and description.
    • Documentation information, including icons and a documentation link.
    • Status information, including status labels, and an indication as to whether or not this is the preferred version of the API.
    • Discovery document link, the URI of the discovery document for this API (given as a path relative to https://www.googleapis.com/discovery/v1).
  • Discovery Document resource: Represents a machine-readable description of a particular API.

    In addition to the information provided in the APIs Directory, a Discovery document also includes:

    • Schemas, which is a list of API resource schemas that describe the data you have access to in each API; the Google APIs Discovery Service schemas are based on JSON Schema.
    • Methods, including a list of API methods and available parameters for each method.
    • OAuth scopes, which identifies the list of OAuth scopes available for this API.
    • Inline documentation, which provides brief descriptions of schemas, methods, parameters and available parameter values.

The single Directory Collection is the conceptual container of the single APIs Directory resource, and the Discovery Document resources for each supported API.

More details about the the APIs Directory resource and the Discovery Document resource are provided in the Using the API and Reference documents.

Operations

You can invoke two different methods on collections and resources in the Google APIs Discovery Service, as described in the following table.

OperationDescriptionREST HTTP mappings
listLists all supported APIs. on the Directory resource URI.
getRestGets a Discovery Document resource for a particular API. on a Discovery Document resource URI.

Calling style

REST

The supported Google APIs Discovery Service operations map directly to the REST HTTP verb, as described in Operations.

The specific format for Google APIs Discovery Service URIs are:

https://www.googleapis.com/discovery/v1/apis?parameters
https://www.googleapis.com/discovery/v1/apis/api/version/rest?parameters

where is the identifier for a Discovery Document resource, and is the identifier of the particular version of the API, , and  are any parameters to apply to the query. See Query parameter summary in the reference documentation for details

Details on the full set of URIs used for each supported operation in the API is summarized in the Google APIs Discovery Service Reference document.

Here are a couple of examples of how this works in the Google APIs Discovery Service.

List all the Google APIs Discovery Service supported APIs:

GET https://www.googleapis.com/discovery/v1/apis

Try it now in APIs Explorer!

Get the Discovery document for the URL Shortener API, version 1:

GET https://www.googleapis.com/discovery/v1/apis/urlshortener/v1/rest

Try it now in APIs Explorer!


In some cases, Google automatically assigns a license for a service to every user in your entire organization. In other cases, you can manually assign licenses to your entire organization, an organizational unit, a group of users, or an individual user. You can also turn on the option to automatically assign licenses to users. 

You assign and manage licenses in 3 places in the Google Admin console:

  • The Billing page—Use to assign licenses to all users in your organization or an uploaded list of users or to set up automatic licensing
  • The Users page—Useful for assigning licenses to multiple users, but not all users in your organization
  • An individual user’s page—Good for managing a single user

Note: If you’re a Postini (Google Message Discovery) customer who transitioned to Google Vault, you can assign Vault Former Employee licenses instead.

Assign and remove licenses

These steps are for assigning and removing user licenses. If you want to reduce your license count, see Reduce licenses instead.

Automatically assign a license to every user in your organization
  • You can assign a license to every user in your organization automatically from the Billing page or the license-management page.
  • If you have multiple Google services or multiple subscriptions of the same service, you can only turn on automatic licensing for one service or subscription.
  • If you choose to automatically assign licenses for a service to all users, you can’t remove an individual user’s license.
  • If you have organizational units under your top-level organization, you can set automatic licensing options for specific organizational units.

Note:If you use Google Cloud Directory Sync, you must pick one way to automatically assign licenses—either the option in the Google Admin console described here or with Google Cloud Directory Sync.

Automatically assign a license to everyone from the Billing page

  1. From the Admin console dashboard, go to Billing.

    The Billing page lists each service you've purchased, along with basic information about your subscription.

  2. For the service you want, to the left of the service name, click the Down arrow  to expand the box.
  3. Click the Auto-licensing field and select ON for everyone.
  4. Click Save.

Automatically assign a license to everyone from the license-management page

  1. From the Admin console dashboard, go to Billing.

    The Billing page lists each service you've purchased, along with basic information about your subscription.

  2. Next to the service you want to assign licenses for, click ActionsManage Licenses.
  3. On the Manage licenses tab, next to Automatic License assignment, check the auto-assign box.
  4. If you have multiple services, from the list below the box, choose a license option.
  5. At the bottom, click Save.

    If you turn on automatic license assignment, only the Manage licenses tab appears on the license-management page.

Manually assign and remove licenses on the Billing page
  1. From the Admin console dashboard, go to Billing.

    The Billing page lists each service you've purchased, along with basic information about your subscription.

  2. Next to the service you want to assign licenses for, click ActionsManage Licenses.
  3. If you want to assign a license to individual users in your account:
    1. On the Unassigned users tab, check the box next to each user you want to assign a license to.
    2. Click Assign, select the service you want to assign the license to, and click Assign License.

      The assigned users are moved to the Assigned users tab.

  4. If you want to assign licenses to an uploaded list of users:
    1. On the Manage licenses tab, next to Assign bulk licenses to users, click Choose File.

      Note: This option isn’t available if you have automatic licensing turned on.

    2. Select the user file and click Upload.

      The file should be in .csv format and contain the full email address of each user you want to assign a license to. Include one address per line.

    3. If you have multiple subscriptions of a service, select the subscription for which you want to apply the licenses.
    4. Click Upload.
  5. If you want to assign a license to each user in an organization:
    1. At the top of the Unassigned users tab, click Org.
    2. On the left, select the organization you want to assign licenses to. You can also search for an organization in the search field.

      The Org screen shows how many users in the organization do and don't have licenses.

    3. Click Assign, select the service you want to assign the license to, and click Assign License.

      If you have multiple subscriptions of a service and some of the users already have a license for a different subscription, you’ll be asked if you want to replace those users’ licenses with the new license or only assign a license to users who don’t already have one.

      Assigning licenses to an organization only gives users in that organization a license. Users in suborganizations aren’t assigned a license.

  6. If you want to remove licenses:
    1. On the Assigned users tab, select or search for users (List view) or an organization (Org view).
    2. Click Unassign.

      This removes the license and moves the user from the Assigned to the Unassigned tab.

Manually assign and remove licenses on the Users page
  1. From the Admin console dashboard, go to Users.
  2. Next to each user’s name where you want to assign or remove a license, check the box.
  3. In the top corner, click More   Assign Licenses or Remove Licenses.
  4. Click the service  Assign or Remove.
Manually assign and remove licenses on an individual user's page
  1. From the Admin console dashboard, go to Users.
  2. Click the name of the user you want to manage.
  3. Scroll down and click the user’s License section.
  4. Next to a service, in the Status column, click the switch to assign or remove a license.
  5. Click Save.

Reassign licenses

You can’t directly reassign a license for a Google service from one user to another. Instead, follow any of the procedures above to unassign the license from the original user and then assign it to the new user.

After you unassign a license, it might take up to 24 hours before you can reassign the license to a different user.

Related topics

0 Replies to “Assignments Discovery Google”

Lascia un Commento

L'indirizzo email non verrà pubblicato. I campi obbligatori sono contrassegnati *