Talking to the BigQuery API - Google BigQuery Analytics - page 142

contained by these collections are called resources ; the REST operations in
the collection can investigate and manipulate resource objects. This section
describes each of these collections in turn, describes the valid operations,
demonstrates how they are used, and shows additional ways to control their
behavior.
In the REST model, a collection maps to a URL. Figure 5.2 shows a
high-level view of the relationships between BigQuery collections and their
URLs. These collections are discussed from the outside in, starting with
Projects, which is a container for all the other collections.

Figure 5.2 BigQuery collections and their URLs

Projects

The Projects collection is the simplest of the BigQuery REST collections; it
has only a single method: Projects.list() . Projects are containers for
all the other objects in BigQuery, but because projects are configured via
the Google Developers Console (not in BigQuery), the BigQuery API doesn't
have any operations on projects other than to list them. In fact, if there
was a better way to get a list of projects that had BigQuery enabled, the
Projects collection would likely be unnecessary. At a later date BigQuery
may store information on a per-project basis; if so, the Projects collection
would become more interesting. The Projects collection is summarized in
Table 5.2 .

Table 5.2 Projects REST Collection

Method URL HTTP Verb

Projects.list() . . . /projects GET