package google.api

Get desktop application:
View/edit binary Protocol Buffers messages

Generated advice about this change, used for providing more information about how a change will affect the existing service.

Used in: ConfigChange

• string description = 2

  Useful description for why this advice was applied and what actions should be taken to mitigate any implied risks.

Configuration for an anthentication provider, including support for [JSON Web Token (JWT)](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32).

Used in: Authentication

• string id = 1

  The unique identifier of the auth provider. It will be referred to by `AuthRequirement.provider_id`. Example: "bookstore_auth".

• string issuer = 2

  Identifies the principal that issued the JWT. See https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section-4.1.1 Usually a URL or an email address. Example: https://securetoken.google.com Example: 1234567-compute@developer.gserviceaccount.com

• string jwks_uri = 3

  URL of the provider's public key set to validate signature of the JWT. See [OpenID Discovery](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata). Optional if the key set document: - can be retrieved from [OpenID Discovery](https://openid.net/specs/openid-connect-discovery-1_0.html of the issuer. - can be inferred from the email domain of the issuer (e.g. a Google service account). Example: https://www.googleapis.com/oauth2/v1/certs

• string audiences = 4

  The list of JWT [audiences](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section-4.1.3). that are allowed to access. A JWT containing any of these audiences will be accepted. When this setting is absent, only JWTs with audience "https://[Service_name][google.api.Service.name]/[API_name][google.protobuf.Api.name]" will be accepted. For example, if no audiences are in the setting, LibraryService API will only accept JWTs with the following audience "https://library-example.googleapis.com/google.example.library.v1.LibraryService". Example: audiences: bookstore_android.apps.googleusercontent.com, bookstore_web.apps.googleusercontent.com

• string authorization_url = 5

  Redirect URL if JWT token is required but no present or is expired. Implement authorizationUrl of securityDefinitions in OpenAPI spec.

User-defined authentication requirements, including support for [JSON Web Token (JWT)](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32).

Used in: AuthenticationRule

• string provider_id = 1

  [id][google.api.AuthProvider.id] from authentication provider. Example: provider_id: bookstore_auth

• string audiences = 2

  NOTE: This will be deprecated soon, once AuthProvider.audiences is implemented and accepted in all the runtime components. The list of JWT [audiences](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section-4.1.3). that are allowed to access. A JWT containing any of these audiences will be accepted. When this setting is absent, only JWTs with audience "https://[Service_name][google.api.Service.name]/[API_name][google.protobuf.Api.name]" will be accepted. For example, if no audiences are in the setting, LibraryService API will only accept JWTs with the following audience "https://library-example.googleapis.com/google.example.library.v1.LibraryService". Example: audiences: bookstore_android.apps.googleusercontent.com, bookstore_web.apps.googleusercontent.com

`Authentication` defines the authentication configuration for an API. Example for an API targeted for external use: name: calendar.googleapis.com authentication: providers: - id: google_calendar_auth jwks_uri: https://www.googleapis.com/oauth2/v1/certs issuer: https://securetoken.google.com rules: - selector: "*" requirements: provider_id: google_calendar_auth

Used in: Service

• repeated AuthenticationRule rules = 3

  A list of authentication rules that apply to individual API methods. **NOTE:** All service configuration rules follow "last one wins" order.

• repeated AuthProvider providers = 4

  Defines a set of authentication providers that a service supports.

Authentication rules for the service. By default, if a method has any authentication requirements, every request must include a valid credential matching one of the requirements. It's an error to include more than one kind of credential in a single request. If a method doesn't have any auth requirements, request credentials will be ignored.

Used in: Authentication

• string selector = 1

  Selects the methods to which this rule applies. Refer to [selector][google.api.DocumentationRule.selector] for syntax details.

• optional OAuthRequirements oauth = 2

  The requirements for OAuth credentials.

• bool allow_without_credential = 5

  If true, the service accepts API keys without any other credential.

• repeated AuthRequirement requirements = 7

  Requirements for additional authentication providers.

Configuration of authorization. This section determines the authorization provider, if unspecified, then no authorization check will be done. Example: experimental: authorization: provider: firebaserules.googleapis.com

Used in: Experimental

• string provider = 1

  The name of the authorization provider, such as firebaserules.googleapis.com.

`Backend` defines the backend configuration for a service.

Used in: Service

• repeated BackendRule rules = 1

  A list of API backend rules that apply to individual API methods. **NOTE:** All service configuration rules follow "last one wins" order.

A backend rule provides configuration for an individual API element.

Used in: Backend

• string selector = 1

  Selects the methods to which this rule applies. Refer to [selector][google.api.DocumentationRule.selector] for syntax details.

• string address = 2

  The address of the API backend.

• double deadline = 3

  The number of seconds to wait for a response from a request. The default deadline for gRPC is infinite (no deadline) and HTTP requests is 5 seconds.

• double min_deadline = 4

  Minimum deadline in seconds needed for this method. Calls having deadline value lower than this will be rejected.

Billing related configuration of the service. The following example shows how to configure monitored resources and metrics for billing: monitored_resources: - type: library.googleapis.com/branch labels: - key: /city description: The city where the library branch is located in. - key: /name description: The name of the branch. metrics: - name: library.googleapis.com/book/borrowed_count metric_kind: DELTA value_type: INT64 billing: consumer_destinations: - monitored_resource: library.googleapis.com/branch metrics: - library.googleapis.com/book/borrowed_count

Used in: Service

• repeated Billing.BillingDestination consumer_destinations = 8

  Billing configurations for sending metrics to the consumer project. There can be multiple consumer destinations per service, each one must have a different monitored resource type. A metric can be used in at most one consumer destination.

Configuration of a specific billing destination (Currently only support bill against consumer project).

Used in: Billing

• string monitored_resource = 1

  The monitored resource type. The type must be defined in [Service.monitored_resources][google.api.Service.monitored_resources] section.

• repeated string metrics = 2

  Names of the metrics to report to this billing destination. Each name must be defined in [Service.metrics][google.api.Service.metrics] section.

Classifies set of possible modifications to an object in the service configuration.

Used in: ConfigChange

• CHANGE_TYPE_UNSPECIFIED = 0

  No value was provided.

• ADDED = 1

  The changed object exists in the 'new' service configuration, but not in the 'old' service configuration.

• REMOVED = 2

  The changed object exists in the 'old' service configuration, but not in the 'new' service configuration.

• MODIFIED = 3

  The changed object exists in both service configurations, but its value is different.

Output generated from semantically comparing two versions of a service configuration. Includes detailed information about a field that have changed with applicable advice about potential consequences for the change, such as backwards-incompatibility.

Used in: servicemanagement.v1.ChangeReport

• string element = 1

  Object hierarchy path to the change, with levels separated by a '.' character. For repeated fields, an applicable unique identifier field is used for the index (usually selector, name, or id). For maps, the term 'key' is used. If the field has no unique identifier, the numeric index is used. Examples: - visibility.rules[selector=="google.LibraryService.CreateBook"].restriction - quota.metric_rules[selector=="google"].metric_costs[key=="reads"].value - logging.producer_destinations[0]

• string old_value = 2

  Value of the changed object in the old Service configuration, in JSON format. This field will not be populated if ChangeType == ADDED.

• string new_value = 3

  Value of the changed object in the new Service configuration, in JSON format. This field will not be populated if ChangeType == REMOVED.

• ChangeType change_type = 4

  The type for this change, either ADDED, REMOVED, or MODIFIED.

• repeated Advice advices = 5

  Collection of advice provided for this change, useful for determining the possible impact of this change.

`Context` defines which contexts an API requests. Example: context: rules: - selector: "*" requested: - google.rpc.context.ProjectContext - google.rpc.context.OriginContext The above specifies that all methods in the API request `google.rpc.context.ProjectContext` and `google.rpc.context.OriginContext`. Available context types are defined in package `google.rpc.context`.

Used in: Service

• repeated ContextRule rules = 1

  A list of RPC context rules that apply to individual API methods. **NOTE:** All service configuration rules follow "last one wins" order.

A context rule provides information about the context for an individual API element.

Used in: Context

• string selector = 1

  Selects the methods to which this rule applies. Refer to [selector][google.api.DocumentationRule.selector] for syntax details.

• repeated string requested = 2

  A list of full type names of requested contexts.

• repeated string provided = 3

  A list of full type names of provided contexts.

Selects and configures the service controller used by the service. The service controller handles features like abuse, quota, billing, logging, monitoring, etc.

Used in: Service

• string environment = 1

  The service control environment to use. If empty, no control plane feature (like quota and billing) will be enabled.

A custom pattern is used for defining custom HTTP verb.

Used in: HttpRule

• string kind = 1

  The name of this custom HTTP verb.

• string path = 2

  The path matched by this custom verb.

Distribution contains summary statistics for a population of values and, optionally, a histogram representing the distribution of those values across a specified set of histogram buckets. The summary statistics are the count, mean, sum of the squared deviation from the mean, the minimum, and the maximum of the set of population of values. The histogram is based on a sequence of buckets and gives a count of values that fall into each bucket. The boundaries of the buckets are given either explicitly or by specifying parameters for a method of computing them (buckets of fixed width or buckets of exponentially increasing width). Although it is not forbidden, it is generally a bad idea to include non-finite values (infinities or NaNs) in the population of values, as this will render the `mean` and `sum_of_squared_deviation` fields meaningless.

Used in: monitoring.v3.TypedValue

• int64 count = 1

  The number of values in the population. Must be non-negative.

• double mean = 2

  The arithmetic mean of the values in the population. If `count` is zero then this field must be zero.

• double sum_of_squared_deviation = 3

  The sum of squared deviations from the mean of the values in the population. For values x_i this is: Sum[i=1..n]((x_i - mean)^2) Knuth, "The Art of Computer Programming", Vol. 2, page 323, 3rd edition describes Welford's method for accumulating this sum in one pass. If `count` is zero then this field must be zero.

• optional Distribution.Range range = 4

  If specified, contains the range of the population values. The field must not be present if the `count` is zero.

• optional Distribution.BucketOptions bucket_options = 6

  Defines the histogram bucket boundaries.

• repeated int64 bucket_counts = 7

  If `bucket_options` is given, then the sum of the values in `bucket_counts` must equal the value in `count`. If `bucket_options` is not given, no `bucket_counts` fields may be given. Bucket counts are given in order under the numbering scheme described above (the underflow bucket has number 0; the finite buckets, if any, have numbers 1 through N-2; the overflow bucket has number N-1). The size of `bucket_counts` must be no greater than N as defined in `bucket_options`. Any suffix of trailing zero bucket_count fields may be omitted.

A Distribution may optionally contain a histogram of the values in the population. The histogram is given in `bucket_counts` as counts of values that fall into one of a sequence of non-overlapping buckets. The sequence of buckets is described by `bucket_options`. A bucket specifies an inclusive lower bound and exclusive upper bound for the values that are counted for that bucket. The upper bound of a bucket is strictly greater than the lower bound. The sequence of N buckets for a Distribution consists of an underflow bucket (number 0), zero or more finite buckets (number 1 through N - 2) and an overflow bucket (number N - 1). The buckets are contiguous: the lower bound of bucket i (i > 0) is the same as the upper bound of bucket i - 1. The buckets span the whole range of finite values: lower bound of the underflow bucket is -infinity and the upper bound of the overflow bucket is +infinity. The finite buckets are so-called because both bounds are finite. `BucketOptions` describes bucket boundaries in one of three ways. Two describe the boundaries by giving parameters for a formula to generate boundaries and one gives the bucket boundaries explicitly. If `bucket_boundaries` is not given, then no `bucket_counts` may be given.

Used in: Distribution, logging.v2.LogMetric

• oneof options

  Exactly one of these three fields must be set.

  • BucketOptions.Linear linear_buckets = 1

    The linear bucket.

  • BucketOptions.Exponential exponential_buckets = 2

    The exponential buckets.

  • BucketOptions.Explicit explicit_buckets = 3

    The explicit buckets.

A set of buckets with arbitrary widths. Defines `size(bounds) + 1` (= N) buckets with these boundaries for bucket i: Upper bound (0 <= i < N-1): bounds[i] Lower bound (1 <= i < N); bounds[i - 1] There must be at least one element in `bounds`. If `bounds` has only one element, there are no finite buckets, and that single element is the common boundary of the overflow and underflow buckets.

Used in: BucketOptions

• repeated double bounds = 1

  The values must be monotonically increasing.

Specify a sequence of buckets that have a width that is proportional to the value of the lower bound. Each bucket represents a constant relative uncertainty on a specific value in the bucket. Defines `num_finite_buckets + 2` (= N) buckets with these boundaries for bucket i: Upper bound (0 <= i < N-1): scale * (growth_factor ^ i). Lower bound (1 <= i < N): scale * (growth_factor ^ (i - 1)).

Used in: BucketOptions

• int32 num_finite_buckets = 1

  Must be greater than 0.

• double growth_factor = 2

  Must be greater than 1.

• double scale = 3

  Must be greater than 0.

Specify a sequence of buckets that all have the same width (except overflow and underflow). Each bucket represents a constant absolute uncertainty on the specific value in the bucket. Defines `num_finite_buckets + 2` (= N) buckets with these boundaries for bucket `i`: Upper bound (0 <= i < N-1): offset + (width * i). Lower bound (1 <= i < N): offset + (width * (i - 1)).

Used in: BucketOptions

• int32 num_finite_buckets = 1

  Must be greater than 0.

• double width = 2

  Must be greater than 0.

• double offset = 3

  Lower bound of the first bucket.

The range of the population values.

Used in: Distribution

• double min = 1

  The minimum of the population values.

• double max = 2

  The maximum of the population values.

`Documentation` provides the information for describing a service. Example: <pre><code>documentation: summary: > The Google Calendar API gives access to most calendar features. pages: - name: Overview content: &#40;== include google/foo/overview.md ==&#41; - name: Tutorial content: &#40;== include google/foo/tutorial.md ==&#41; subpages; - name: Java content: &#40;== include google/foo/tutorial_java.md ==&#41; rules: - selector: google.calendar.Calendar.Get description: > ... - selector: google.calendar.Calendar.Put description: > ... </code></pre> Documentation is provided in markdown syntax. In addition to standard markdown features, definition lists, tables and fenced code blocks are supported. Section headers can be provided and are interpreted relative to the section nesting of the context where a documentation fragment is embedded. Documentation from the IDL is merged with documentation defined via the config at normalization time, where documentation provided by config rules overrides IDL provided. A number of constructs specific to the API platform are supported in documentation text. In order to reference a proto element, the following notation can be used: <pre><code>&#91;fully.qualified.proto.name]&#91;]</code></pre> To override the display text used for the link, this can be used: <pre><code>&#91;display text]&#91;fully.qualified.proto.name]</code></pre> Text can be excluded from doc using the following notation: <pre><code>&#40;-- internal comment --&#41;</code></pre> A few directives are available in documentation. Note that directives must appear on a single line to be properly identified. The `include` directive includes a markdown file from an external source: <pre><code>&#40;== include path/to/file ==&#41;</code></pre> The `resource_for` directive marks a message to be the resource of a collection in REST view. If it is not specified, tools attempt to infer the resource from the operations in a collection: <pre><code>&#40;== resource_for v1.shelves.books ==&#41;</code></pre> The directive `suppress_warning` does not directly affect documentation and is documented together with service config validation.

Used in: Service

• string summary = 1

  A short summary of what the service does. Can only be provided by plain text.

• repeated Page pages = 5

  The top level pages for the documentation set.

• repeated DocumentationRule rules = 3

  A list of documentation rules that apply to individual API elements. **NOTE:** All service configuration rules follow "last one wins" order.

• string documentation_root_url = 4

  The URL to the root of documentation.

• string overview = 2

  Declares a single overview page. For example: <pre><code>documentation: summary: ... overview: &#40;== include overview.md ==&#41; </code></pre> This is a shortcut for the following declaration (using pages style): <pre><code>documentation: summary: ... pages: - name: Overview content: &#40;== include overview.md ==&#41; </code></pre> Note: you cannot specify both `overview` field and `pages` field.

A documentation rule provides information about individual API elements.

Used in: Documentation

• string selector = 1

  The selector is a comma-separated list of patterns. Each pattern is a qualified name of the element which may end in "*", indicating a wildcard. Wildcards are only allowed at the end and for a whole component of the qualified name, i.e. "foo.*" is ok, but not "foo.b*" or "foo.*.bar". To specify a default for all applicable elements, the whole pattern "*" is used.

• string description = 2

  Description of the selected API(s).

• string deprecation_description = 3

  Deprecation description of the selected element(s). It can be provided if an element is marked as `deprecated`.

`Endpoint` describes a network endpoint that serves a set of APIs. A service may expose any number of endpoints, and all endpoints share the same service configuration, such as quota configuration and monitoring configuration. Example service configuration: name: library-example.googleapis.com endpoints: # Below entry makes 'google.example.library.v1.Library' # API be served from endpoint address library-example.googleapis.com. # It also allows HTTP OPTIONS calls to be passed to the backend, for # it to decide whether the subsequent cross-origin request is # allowed to proceed. - name: library-example.googleapis.com allow_cors: true

Used in: Service

• string name = 1

  The canonical name of this endpoint.

• repeated string aliases = 2

  DEPRECATED: This field is no longer supported. Instead of using aliases, please specify multiple [google.api.Endpoint][google.api.Endpoint] for each of the intended aliases. Additional names that this endpoint will be hosted on.

• repeated string features = 4

  The list of features enabled on this endpoint.

• string target = 101

  The specification of an Internet routable address of API frontend that will handle requests to this [API Endpoint](https://cloud.google.com/apis/design/glossary). It should be either a valid IPv4 address or a fully-qualified domain name. For example, "8.8.8.8" or "myservice.appspot.com".

• bool allow_cors = 5

  Allowing [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing), aka cross-domain traffic, would allow the backends served from this endpoint to receive and respond to HTTP OPTIONS requests. The response will be used by the browser to determine whether the subsequent cross-origin request is allowed to proceed.

Experimental service configuration. These configuration options can only be used by whitelisted users.

Used in: Service

• optional AuthorizationConfig authorization = 8

  Authorization configuration.

Defines the HTTP configuration for an API service. It contains a list of [HttpRule][google.api.HttpRule], each specifying the mapping of an RPC method to one or more HTTP REST API methods.

Used in: Service

• repeated HttpRule rules = 1

  A list of HTTP configuration rules that apply to individual API methods. **NOTE:** All service configuration rules follow "last one wins" order.

• bool fully_decode_reserved_expansion = 2

  When set to true, URL path parmeters will be fully URI-decoded except in cases of single segment matches in reserved expansion, where "%2F" will be left encoded. The default behavior is to not decode RFC 6570 reserved characters in multi segment matches.

Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged.

Used as response type in: cloud.ml.v1.OnlinePredictionService.Predict

Used as field type in: cloud.ml.v1.PredictRequest

• string content_type = 1

  The HTTP Content-Type string representing the content type of the body.

• bytes data = 2

  HTTP body binary data.

• repeated protobuf.Any extensions = 3

  Application specific response metadata. Must be set in the first response for streaming APIs.

`HttpRule` defines the mapping of an RPC method to one or more HTTP REST API methods. The mapping specifies how different portions of the RPC request message are mapped to URL path, URL query parameters, and HTTP request body. The mapping is typically specified as an `google.api.http` annotation on the RPC method, see "google/api/annotations.proto" for details. The mapping consists of a field specifying the path template and method kind. The path template can refer to fields in the request message, as in the example below which describes a REST GET operation on a resource collection of messages: service Messaging { rpc GetMessage(GetMessageRequest) returns (Message) { option (google.api.http).get = "/v1/messages/{message_id}/{sub.subfield}"; } } message GetMessageRequest { message SubMessage { string subfield = 1; } string message_id = 1; // mapped to the URL SubMessage sub = 2; // `sub.subfield` is url-mapped } message Message { string text = 1; // content of the resource } The same http annotation can alternatively be expressed inside the `GRPC API Configuration` YAML file. http: rules: - selector: <proto_package_name>.Messaging.GetMessage get: /v1/messages/{message_id}/{sub.subfield} This definition enables an automatic, bidrectional mapping of HTTP JSON to RPC. Example: HTTP | RPC -----|----- `GET /v1/messages/123456/foo` | `GetMessage(message_id: "123456" sub: SubMessage(subfield: "foo"))` In general, not only fields but also field paths can be referenced from a path pattern. Fields mapped to the path pattern cannot be repeated and must have a primitive (non-message) type. Any fields in the request message which are not bound by the path pattern automatically become (optional) HTTP query parameters. Assume the following definition of the request message: service Messaging { rpc GetMessage(GetMessageRequest) returns (Message) { option (google.api.http).get = "/v1/messages/{message_id}"; } } message GetMessageRequest { message SubMessage { string subfield = 1; } string message_id = 1; // mapped to the URL int64 revision = 2; // becomes a parameter SubMessage sub = 3; // `sub.subfield` becomes a parameter } This enables a HTTP JSON to RPC mapping as below: HTTP | RPC -----|----- `GET /v1/messages/123456?revision=2&sub.subfield=foo` | `GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield: "foo"))` Note that fields which are mapped to HTTP parameters must have a primitive type or a repeated primitive type. Message types are not allowed. In the case of a repeated type, the parameter can be repeated in the URL, as in `...?param=A&param=B`. For HTTP method kinds which allow a request body, the `body` field specifies the mapping. Consider a REST update method on the message resource collection: service Messaging { rpc UpdateMessage(UpdateMessageRequest) returns (Message) { option (google.api.http) = { put: "/v1/messages/{message_id}" body: "message" }; } } message UpdateMessageRequest { string message_id = 1; // mapped to the URL Message message = 2; // mapped to the body } The following HTTP JSON to RPC mapping is enabled, where the representation of the JSON in the request body is determined by protos JSON encoding: HTTP | RPC -----|----- `PUT /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id: "123456" message { text: "Hi!" })` The special name `*` can be used in the body mapping to define that every field not bound by the path template should be mapped to the request body. This enables the following alternative definition of the update method: service Messaging { rpc UpdateMessage(Message) returns (Message) { option (google.api.http) = { put: "/v1/messages/{message_id}" body: "*" }; } } message Message { string message_id = 1; string text = 2; } The following HTTP JSON to RPC mapping is enabled: HTTP | RPC -----|----- `PUT /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id: "123456" text: "Hi!")` Note that when using `*` in the body mapping, it is not possible to have HTTP parameters, as all fields not bound by the path end in the body. This makes this option more rarely used in practice of defining REST APIs. The common usage of `*` is in custom methods which don't use the URL at all for transferring data. It is possible to define multiple HTTP methods for one RPC by using the `additional_bindings` option. Example: service Messaging { rpc GetMessage(GetMessageRequest) returns (Message) { option (google.api.http) = { get: "/v1/messages/{message_id}" additional_bindings { get: "/v1/users/{user_id}/messages/{message_id}" } }; } } message GetMessageRequest { string message_id = 1; string user_id = 2; } This enables the following two alternative HTTP JSON to RPC mappings: HTTP | RPC -----|----- `GET /v1/messages/123456` | `GetMessage(message_id: "123456")` `GET /v1/users/me/messages/123456` | `GetMessage(user_id: "me" message_id: "123456")` # Rules for HTTP mapping The rules for mapping HTTP path, query parameters, and body fields to the request message are as follows: 1. The `body` field specifies either `*` or a field path, or is omitted. If omitted, it indicates there is no HTTP request body. 2. Leaf fields (recursive expansion of nested messages in the request) can be classified into three types: (a) Matched in the URL template. (b) Covered by body (if body is `*`, everything except (a) fields; else everything under the body field) (c) All other fields. 3. URL query parameters found in the HTTP request are mapped to (c) fields. 4. Any body sent with an HTTP request can contain only (b) fields. The syntax of the path template is as follows: Template = "/" Segments [ Verb ] ; Segments = Segment { "/" Segment } ; Segment = "*" | "**" | LITERAL | Variable ; Variable = "{" FieldPath [ "=" Segments ] "}" ; FieldPath = IDENT { "." IDENT } ; Verb = ":" LITERAL ; The syntax `*` matches a single path segment. The syntax `**` matches zero or more path segments, which must be the last part of the path except the `Verb`. The syntax `LITERAL` matches literal text in the path. The syntax `Variable` matches part of the URL path as specified by its template. A variable template must not contain other variables. If a variable matches a single path segment, its template may be omitted, e.g. `{var}` is equivalent to `{var=*}`. If a variable contains exactly one path segment, such as `"{var}"` or `"{var=*}"`, when such a variable is expanded into a URL path, all characters except `[-_.~0-9a-zA-Z]` are percent-encoded. Such variables show up in the Discovery Document as `{var}`. If a variable contains one or more path segments, such as `"{var=foo/*}"` or `"{var=**}"`, when such a variable is expanded into a URL path, all characters except `[-_.~/0-9a-zA-Z]` are percent-encoded. Such variables show up in the Discovery Document as `{+var}`. NOTE: While the single segment variable matches the semantics of [RFC 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String Expansion, the multi segment variable **does not** match RFC 6570 Reserved Expansion. The reason is that the Reserved Expansion does not expand special characters like `?` and `#`, which would lead to invalid URLs. NOTE: the field paths in variables and in the `body` must not refer to repeated fields or map fields.

Used in: Http

• string selector = 1

  Selects methods to which this rule applies. Refer to [selector][google.api.DocumentationRule.selector] for syntax details.

• oneof pattern

  Determines the URL pattern is matched by this rules. This pattern can be used with any of the {get|put|post|delete|patch} methods. A custom method can be defined using the 'custom' field.

  • string get = 2

    Used for listing and getting information about resources.

  • string put = 3

    Used for updating a resource.

  • string post = 4

    Used for creating a resource.

  • string delete = 5

    Used for deleting a resource.

  • string patch = 6

    Used for updating a resource.

  • CustomHttpPattern custom = 8

    The custom pattern is used for specifying an HTTP method that is not included in the `pattern` field, such as HEAD, or "*" to leave the HTTP method unspecified for this rule. The wild-card rule is useful for services that provide content to Web (HTML) clients.

• string body = 7

  The name of the request field whose value is mapped to the HTTP body, or `*` for mapping all fields not captured by the path pattern to the HTTP body. NOTE: the referred field must not be a repeated field and must be present at the top-level of request message type.

• repeated HttpRule additional_bindings = 11

  Additional HTTP bindings for the selector. Nested bindings must not contain an `additional_bindings` field themselves (that is, the nesting may only be one level deep).

A description of a label.

Used in: LogDescriptor, MetricDescriptor, MonitoredResourceDescriptor, monitoring.v3.NotificationChannelDescriptor

• string key = 1

  The label key.

• LabelDescriptor.ValueType value_type = 2

  The type of data that can be assigned to the label.

• string description = 3

  A human-readable description for the label.

Value types that can be used as label values.

Used in: LabelDescriptor

• STRING = 0

  A variable-length string. This is the default.

• BOOL = 1

  Boolean; true or false.

• INT64 = 2

  A 64-bit signed integer.

A description of a log type. Example in YAML format: - name: library.googleapis.com/activity_history description: The history of borrowing and returning library items. display_name: Activity labels: - key: /customer_id description: Identifier of a library customer

Used in: Service

• string name = 1

  The name of the log. It must be less than 512 characters long and can include the following characters: upper- and lower-case alphanumeric characters [A-Za-z0-9], and punctuation characters including slash, underscore, hyphen, period [/_-.].

• repeated LabelDescriptor labels = 2

  The set of labels that are available to describe a specific log entry. Runtime requests that contain labels not specified here are considered invalid.

• string description = 3

  A human-readable description of this log. This information appears in the documentation and can contain details.

• string display_name = 4

  The human-readable name for this log. This information appears on the user interface and should be concise.

Logging configuration of the service. The following example shows how to configure logs to be sent to the producer and consumer projects. In the example, the `activity_history` log is sent to both the producer and consumer projects, whereas the `purchase_history` log is only sent to the producer project. monitored_resources: - type: library.googleapis.com/branch labels: - key: /city description: The city where the library branch is located in. - key: /name description: The name of the branch. logs: - name: activity_history labels: - key: /customer_id - name: purchase_history logging: producer_destinations: - monitored_resource: library.googleapis.com/branch logs: - activity_history - purchase_history consumer_destinations: - monitored_resource: library.googleapis.com/branch logs: - activity_history

Used in: Service

• repeated Logging.LoggingDestination producer_destinations = 1

  Logging configurations for sending logs to the producer project. There can be multiple producer destinations, each one must have a different monitored resource type. A log can be used in at most one producer destination.

• repeated Logging.LoggingDestination consumer_destinations = 2

  Logging configurations for sending logs to the consumer project. There can be multiple consumer destinations, each one must have a different monitored resource type. A log can be used in at most one consumer destination.

Configuration of a specific logging destination (the producer project or the consumer project).

Used in: Logging

• string monitored_resource = 3

  The monitored resource type. The type must be defined in the [Service.monitored_resources][google.api.Service.monitored_resources] section.

• repeated string logs = 1

  Names of the logs to be sent to this destination. Each name must be defined in the [Service.logs][google.api.Service.logs] section. If the log name is not a domain scoped name, it will be automatically prefixed with the service name followed by "/".

A specific metric, identified by specifying values for all of the labels of a [`MetricDescriptor`][google.api.MetricDescriptor].

Used in: monitoring.v3.TimeSeries

• string type = 3

  An existing metric type, see [google.api.MetricDescriptor][google.api.MetricDescriptor]. For example, `custom.googleapis.com/invoice/paid/amount`.

• map<string, string> labels = 2

  The set of label values that uniquely identify this metric. All labels listed in the `MetricDescriptor` must be assigned values.

Defines a metric type and its schema. Once a metric descriptor is created, deleting or altering it stops data collection and makes the metric type's existing data unusable.

Used as response type in: monitoring.v3.MetricService.CreateMetricDescriptor, monitoring.v3.MetricService.GetMetricDescriptor

Used as field type in: Service, logging.v2.LogMetric, monitoring.v3.CreateMetricDescriptorRequest, monitoring.v3.ListMetricDescriptorsResponse

• string name = 1

  The resource name of the metric descriptor.

• string type = 8

  The metric type, including its DNS name prefix. The type is not URL-encoded. All user-defined custom metric types have the DNS name `custom.googleapis.com`. Metric types should use a natural hierarchical grouping. For example: "custom.googleapis.com/invoice/paid/amount" "appengine.googleapis.com/http/server/response_latencies"

• repeated LabelDescriptor labels = 2

  The set of labels that can be used to describe a specific instance of this metric type. For example, the `appengine.googleapis.com/http/server/response_latencies` metric type has a label for the HTTP response code, `response_code`, so you can look at latencies for successful responses or just for responses that failed.

• MetricDescriptor.MetricKind metric_kind = 3

  Whether the metric records instantaneous values, changes to a value, etc. Some combinations of `metric_kind` and `value_type` might not be supported.

• MetricDescriptor.ValueType value_type = 4

  Whether the measurement is an integer, a floating-point number, etc. Some combinations of `metric_kind` and `value_type` might not be supported.

• string unit = 5

  The unit in which the metric value is reported. It is only applicable if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The supported units are a subset of [The Unified Code for Units of Measure](http://unitsofmeasure.org/ucum.html) standard: **Basic units (UNIT)** * `bit` bit * `By` byte * `s` second * `min` minute * `h` hour * `d` day **Prefixes (PREFIX)** * `k` kilo (10**3) * `M` mega (10**6) * `G` giga (10**9) * `T` tera (10**12) * `P` peta (10**15) * `E` exa (10**18) * `Z` zetta (10**21) * `Y` yotta (10**24) * `m` milli (10**-3) * `u` micro (10**-6) * `n` nano (10**-9) * `p` pico (10**-12) * `f` femto (10**-15) * `a` atto (10**-18) * `z` zepto (10**-21) * `y` yocto (10**-24) * `Ki` kibi (2**10) * `Mi` mebi (2**20) * `Gi` gibi (2**30) * `Ti` tebi (2**40) **Grammar** The grammar also includes these connectors: * `/` division (as an infix operator, e.g. `1/s`). * `.` multiplication (as an infix operator, e.g. `GBy.d`) The grammar for a unit is as follows: Expression = Component { "." Component } { "/" Component } ; Component = ( [ PREFIX ] UNIT | "%" ) [ Annotation ] | Annotation | "1" ; Annotation = "{" NAME "}" ; Notes: * `Annotation` is just a comment if it follows a `UNIT` and is equivalent to `1` if it is used alone. For examples, `{requests}/s == 1/s`, `By{transmitted}/s == By/s`. * `NAME` is a sequence of non-blank printable ASCII characters not containing '{' or '}'. * `1` represents dimensionless value 1, such as in `1/s`. * `%` represents dimensionless value 1/100, and annotates values giving a percentage.

• string description = 6

  A detailed description of the metric, which can be used in documentation.

• string display_name = 7

  A concise name for the metric, which can be displayed in user interfaces. Use sentence case without an ending period, for example "Request count". This field is optional but it is recommended to be set for any metrics associated with user-visible concepts, such as Quota.

The kind of measurement. It describes how the data is reported.

Used in: MetricDescriptor, monitoring.v3.TimeSeries

• METRIC_KIND_UNSPECIFIED = 0

  Do not use this default value.

• GAUGE = 1

  An instantaneous measurement of a value.

• DELTA = 2

  The change in a value during a time interval.

• CUMULATIVE = 3

  A value accumulated over a time interval. Cumulative measurements in a time series should have the same start time and increasing end times, until an event resets the cumulative value to zero and sets a new start time for the following points.

The value type of a metric.

Used in: MetricDescriptor, monitoring.v3.TimeSeries

• VALUE_TYPE_UNSPECIFIED = 0

  Do not use this default value.

• BOOL = 1

  The value is a boolean. This value type can be used only if the metric kind is `GAUGE`.

• INT64 = 2

  The value is a signed 64-bit integer.

• DOUBLE = 3

  The value is a double precision floating point number.

• STRING = 4

  The value is a text string. This value type can be used only if the metric kind is `GAUGE`.

• DISTRIBUTION = 5

  The value is a [`Distribution`][google.api.Distribution].

• MONEY = 6

  The value is money.

Bind API methods to metrics. Binding a method to a metric causes that metric's configured quota, billing, and monitoring behaviors to apply to the method call. Used by metric-based quotas only.

Used in: Quota

• string selector = 1

  Selects the methods to which this rule applies. Refer to [selector][google.api.DocumentationRule.selector] for syntax details.

• map<string, int64> metric_costs = 2

  Metrics to update when the selected methods are called, and the associated cost applied to each metric. The key of the map is the metric name, and the values are the amount increased for the metric against which the quota limits are defined. The value must not be negative.

An object representing a resource that can be used for monitoring, logging, billing, or other purposes. Examples include virtual machine instances, databases, and storage devices such as disks. The `type` field identifies a [MonitoredResourceDescriptor][google.api.MonitoredResourceDescriptor] object that describes the resource's schema. Information in the `labels` field identifies the actual resource and its attributes according to the schema. For example, a particular Compute Engine VM instance could be represented by the following object, because the [MonitoredResourceDescriptor][google.api.MonitoredResourceDescriptor] for `"gce_instance"` has labels `"instance_id"` and `"zone"`: { "type": "gce_instance", "labels": { "instance_id": "12345678901234", "zone": "us-central1-a" }}

Used in: logging.v2.LogEntry, logging.v2.WriteLogEntriesRequest, monitoring.v3.ListGroupMembersResponse, monitoring.v3.TimeSeries, monitoring.v3.UptimeCheckConfig

• string type = 1

  Required. The monitored resource type. This field must match the `type` field of a [MonitoredResourceDescriptor][google.api.MonitoredResourceDescriptor] object. For example, the type of a Compute Engine VM instance is `gce_instance`.

• map<string, string> labels = 2

  Required. Values for all of the labels listed in the associated monitored resource descriptor. For example, Compute Engine VM instances use the labels `"project_id"`, `"instance_id"`, and `"zone"`.

An object that describes the schema of a [MonitoredResource][google.api.MonitoredResource] object using a type name and a set of labels. For example, the monitored resource descriptor for Google Compute Engine VM instances has a type of `"gce_instance"` and specifies the use of the labels `"instance_id"` and `"zone"` to identify particular VM instances. Different APIs can support different monitored resource types. APIs generally provide a `list` method that returns the monitored resource descriptors used by the API.

Used as response type in: monitoring.v3.MetricService.GetMonitoredResourceDescriptor

Used as field type in: Service, logging.v2.ListMonitoredResourceDescriptorsResponse, monitoring.v3.ListMonitoredResourceDescriptorsResponse

• string name = 5

  Optional. The resource name of the monitored resource descriptor: `"projects/{project_id}/monitoredResourceDescriptors/{type}"` where {type} is the value of the `type` field in this object and {project_id} is a project ID that provides API-specific context for accessing the type. APIs that do not use project information can use the resource name format `"monitoredResourceDescriptors/{type}"`.

• string type = 1

  Required. The monitored resource type. For example, the type `"cloudsql_database"` represents databases in Google Cloud SQL. The maximum length of this value is 256 characters.

• string display_name = 2

  Optional. A concise name for the monitored resource type that might be displayed in user interfaces. It should be a Title Cased Noun Phrase, without any article or other determiners. For example, `"Google Cloud SQL Database"`.

• string description = 3

  Optional. A detailed description of the monitored resource type that might be used in documentation.

• repeated LabelDescriptor labels = 4

  Required. A set of labels used to describe instances of this monitored resource type. For example, an individual Google Cloud SQL database is identified by values for the labels `"database_id"` and `"zone"`.

Auxiliary metadata for a [MonitoredResource][google.api.MonitoredResource] object. [MonitoredResource][google.api.MonitoredResource] objects contain the minimum set of information to uniquely identify a monitored resource instance. There is some other useful auxiliary metadata. Google Stackdriver Monitoring & Logging uses an ingestion pipeline to extract metadata for cloud resources of all types , and stores the metadata in this message.

• optional protobuf.Struct system_labels = 1

  Output only. Values for predefined system metadata labels. System labels are a kind of metadata extracted by Google Stackdriver. Stackdriver determines what system labels are useful and how to obtain their values. Some examples: "machine_image", "vpc", "subnet_id", "security_group", "name", etc. System label values can be only strings, Boolean values, or a list of strings. For example: { "name": "my-test-instance", "security_group": ["a", "b", "c"], "spot_instance": false }

• map<string, string> user_labels = 2

  Output only. A map of user-defined metadata labels.

Monitoring configuration of the service. The example below shows how to configure monitored resources and metrics for monitoring. In the example, a monitored resource and two metrics are defined. The `library.googleapis.com/book/returned_count` metric is sent to both producer and consumer projects, whereas the `library.googleapis.com/book/overdue_count` metric is only sent to the consumer project. monitored_resources: - type: library.googleapis.com/branch labels: - key: /city description: The city where the library branch is located in. - key: /name description: The name of the branch. metrics: - name: library.googleapis.com/book/returned_count metric_kind: DELTA value_type: INT64 labels: - key: /customer_id - name: library.googleapis.com/book/overdue_count metric_kind: GAUGE value_type: INT64 labels: - key: /customer_id monitoring: producer_destinations: - monitored_resource: library.googleapis.com/branch metrics: - library.googleapis.com/book/returned_count consumer_destinations: - monitored_resource: library.googleapis.com/branch metrics: - library.googleapis.com/book/returned_count - library.googleapis.com/book/overdue_count

Used in: Service

• repeated Monitoring.MonitoringDestination producer_destinations = 1

  Monitoring configurations for sending metrics to the producer project. There can be multiple producer destinations, each one must have a different monitored resource type. A metric can be used in at most one producer destination.

• repeated Monitoring.MonitoringDestination consumer_destinations = 2

  Monitoring configurations for sending metrics to the consumer project. There can be multiple consumer destinations, each one must have a different monitored resource type. A metric can be used in at most one consumer destination.

Configuration of a specific monitoring destination (the producer project or the consumer project).

Used in: Monitoring

• string monitored_resource = 1

  The monitored resource type. The type must be defined in [Service.monitored_resources][google.api.Service.monitored_resources] section.

• repeated string metrics = 2

  Names of the metrics to report to this monitoring destination. Each name must be defined in [Service.metrics][google.api.Service.metrics] section.

OAuth scopes are a way to define data and permissions on data. For example, there are scopes defined for "Read-only access to Google Calendar" and "Access to Cloud Platform". Users can consent to a scope for an application, giving it permission to access that data on their behalf. OAuth scope specifications should be fairly coarse grained; a user will need to see and understand the text description of what your scope means. In most cases: use one or at most two OAuth scopes for an entire family of products. If your product has multiple APIs, you should probably be sharing the OAuth scope across all of those APIs. When you need finer grained OAuth consent screens: talk with your product management about how developers will use them in practice. Please note that even though each of the canonical scopes is enough for a request to be accepted and passed to the backend, a request can still fail due to the backend requiring additional scopes or permissions.

Used in: AuthenticationRule

• string canonical_scopes = 1

  The list of publicly documented OAuth scopes that are allowed access. An OAuth token containing any of these scopes will be accepted. Example: canonical_scopes: https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/calendar.read

Represents a documentation page. A page can contain subpages to represent nested documentation set structure.

Used in: Documentation

• string name = 1

  The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: <pre><code>pages: - name: Tutorial content: &#40;== include tutorial.md ==&#41; subpages: - name: Java content: &#40;== include tutorial_java.md ==&#41; </code></pre> You can reference `Java` page using Markdown reference link syntax: `[Java][Tutorial.Java]`.

• string content = 2

  The Markdown content of the page. You can use <code>&#40;== include {path} ==&#41;</code> to include content from a Markdown file.

• repeated Page subpages = 3

  Subpages of this page. The order of subpages specified here will be honored in the generated docset.

A descriptor for defining project properties for a service. One service may have many consumer projects, and the service may want to behave differently depending on some properties on the project. For example, a project may be associated with a school, or a business, or a government agency, a business type property on the project may affect how a service responds to the client. This descriptor defines which properties are allowed to be set on a project. Example: project_properties: properties: - name: NO_WATERMARK type: BOOL description: Allows usage of the API without watermarks. - name: EXTENDED_TILE_CACHE_PERIOD type: INT64

• repeated Property properties = 1

  List of per consumer project-specific properties.

Defines project properties. API services can define properties that can be assigned to consumer projects so that backends can perform response customization without having to make additional calls or maintain additional storage. For example, Maps API defines properties that controls map tile cache period, or whether to embed a watermark in a result. These values can be set via API producer console. Only API providers can define and set these properties.

Used in: ProjectProperties

• string name = 1

  The name of the property (a.k.a key).

• Property.PropertyType type = 2

  The type of this property.

• string description = 3

  The description of the property

Supported data type of the property values

Used in: Property

• UNSPECIFIED = 0

  The type is unspecified, and will result in an error.

• INT64 = 1

  The type is `int64`.

• BOOL = 2

  The type is `bool`.

• STRING = 3

  The type is `string`.

• DOUBLE = 4

  The type is 'double'.

Quota configuration helps to achieve fairness and budgeting in service usage. The quota configuration works this way: - The service configuration defines a set of metrics. - For API calls, the quota.metric_rules maps methods to metrics with corresponding costs. - The quota.limits defines limits on the metrics, which will be used for quota checks at runtime. An example quota configuration in yaml format: quota: limits: - name: apiWriteQpsPerProject metric: library.googleapis.com/write_calls unit: "1/min/{project}" # rate limit for consumer projects values: STANDARD: 10000 # The metric rules bind all methods to the read_calls metric, # except for the UpdateBook and DeleteBook methods. These two methods # are mapped to the write_calls metric, with the UpdateBook method # consuming at twice rate as the DeleteBook method. metric_rules: - selector: "*" metric_costs: library.googleapis.com/read_calls: 1 - selector: google.example.library.v1.LibraryService.UpdateBook metric_costs: library.googleapis.com/write_calls: 2 - selector: google.example.library.v1.LibraryService.DeleteBook metric_costs: library.googleapis.com/write_calls: 1 Corresponding Metric definition: metrics: - name: library.googleapis.com/read_calls display_name: Read requests metric_kind: DELTA value_type: INT64 - name: library.googleapis.com/write_calls display_name: Write requests metric_kind: DELTA value_type: INT64

Used in: Service

• repeated QuotaLimit limits = 3

  List of `QuotaLimit` definitions for the service. Used by metric-based quotas only.

• repeated MetricRule metric_rules = 4

  List of `MetricRule` definitions, each one mapping a selected method to one or more metrics. Used by metric-based quotas only.

`QuotaLimit` defines a specific limit that applies over a specified duration for a limit type. There can be at most one limit for a duration and limit type combination defined within a `QuotaGroup`.

Used in: Quota

• string name = 6

  Name of the quota limit. The name is used to refer to the limit when overriding the default limit on per-consumer basis. For group-based quota limits, the name must be unique within the quota group. If a name is not provided, it will be generated from the limit_by and duration fields. For metric-based quota limits, the name must be provided, and it must be unique within the service. The name can only include alphanumeric characters as well as '-'. The maximum length of the limit name is 64 characters. The name of a limit is used as a unique identifier for this limit. Therefore, once a limit has been put into use, its name should be immutable. You can use the display_name field to provide a user-friendly name for the limit. The display name can be evolved over time without affecting the identity of the limit.

• string description = 2

  Optional. User-visible, extended description for this quota limit. Should be used only when more context is needed to understand this limit than provided by the limit's display name (see: `display_name`).

• int64 default_limit = 3

  Default number of tokens that can be consumed during the specified duration. This is the number of tokens assigned when a client application developer activates the service for his/her project. Specifying a value of 0 will block all requests. This can be used if you are provisioning quota to selected consumers and blocking others. Similarly, a value of -1 will indicate an unlimited quota. No other negative values are allowed. Used by group-based quotas only.

• int64 max_limit = 4

  Maximum number of tokens that can be consumed during the specified duration. Client application developers can override the default limit up to this maximum. If specified, this value cannot be set to a value less than the default limit. If not specified, it is set to the default limit. To allow clients to apply overrides with no upper bound, set this to -1, indicating unlimited maximum quota. Used by group-based quotas only.

• int64 free_tier = 7

  Free tier value displayed in the Developers Console for this limit. The free tier is the number of tokens that will be subtracted from the billed amount when billing is enabled. This field can only be set on a limit with duration "1d", in a billable group; it is invalid on any other limit. If this field is not set, it defaults to 0, indicating that there is no free tier for this service. Used by group-based quotas only.

• string duration = 5

  Duration of this limit in textual notation. Example: "100s", "24h", "1d". For duration longer than a day, only multiple of days is supported. We support only "100s" and "1d" for now. Additional support will be added in the future. "0" indicates indefinite duration. Used by group-based quotas only.

• string metric = 8

  The name of the metric this quota limit applies to. The quota limits with the same metric will be checked together during runtime. The metric must be defined within the service config. Used by metric-based quotas only.

• string unit = 9

  Specify the unit of the quota limit. It uses the same syntax as [Metric.unit][]. The supported unit kinds are determined by the quota backend system. The [Google Service Control](https://cloud.google.com/service-control) supports the following unit components: * One of the time intevals: * "/min" for quota every minute. * "/d" for quota every 24 hours, starting 00:00 US Pacific Time. * Otherwise the quota won't be reset by time, such as storage limit. * One and only one of the granted containers: * "/{organization}" quota for an organization. * "/{project}" quota for a project. * "/{folder}" quota for a folder. * "/{resource}" quota for a universal resource. * Zero or more quota segmentation dimension. Not all combos are valid. * "/{region}" quota for every region. Not to be used with time intervals. * Otherwise the resources granted on the target is not segmented. * "/{zone}" quota for every zone. Not to be used with time intervals. * Otherwise the resources granted on the target is not segmented. * "/{resource}" quota for a resource associated with a project or org. Here are some examples: * "1/min/{project}" for quota per minute per project. * "1/min/{user}" for quota per minute per user. * "1/min/{organization}" for quota per minute per organization. Note: the order of unit components is insignificant. The "1" at the beginning is required to follow the metric unit syntax. Used by metric-based quotas only.

• map<string, int64> values = 10

  Tiered limit values. Also allows for regional or zone overrides for these values if "/{region}" or "/{zone}" is specified in the unit field. Currently supported tiers from low to high: VERY_LOW, LOW, STANDARD, HIGH, VERY_HIGH To apply different limit values for users according to their tiers, specify the values for the tiers you want to differentiate. For example: {LOW:100, STANDARD:500, HIGH:1000, VERY_HIGH:5000} The limit value for each tier is optional except for the tier STANDARD. The limit value for an unspecified tier falls to the value of its next tier towards tier STANDARD. For the above example, the limit value for tier STANDARD is 500. To apply the same limit value for all users, just specify limit value for tier STANDARD. For example: {STANDARD:500}. To apply a regional overide for a tier, add a map entry with key "<TIER>/<region>", where <region> is a region name. Similarly, for a zone override, add a map entry with key "<TIER>/{zone}". Further, a wildcard can be used at the end of a zone name in order to specify zone level overrides. For example: LOW: 10, STANDARD: 50, HIGH: 100, LOW/us-central1: 20, STANDARD/us-central1: 60, HIGH/us-central1: 200, LOW/us-central1-*: 10, STANDARD/us-central1-*: 20, HIGH/us-central1-*: 80 The regional overrides tier set for each region must be the same as the tier set for default limit values. Same rule applies for zone overrides tier as well. Used by metric-based quotas only.

• string display_name = 12

  User-visible display name for this limit. Optional. If not set, the UI will provide a default display name based on the quota configuration. This field can be used to override the default display name generated from the configuration.

`Service` is the root object of Google service configuration schema. It describes basic information about a service, such as the name and the title, and delegates other aspects to sub-sections. Each sub-section is either a proto message or a repeated proto message that configures a specific aspect, such as auth. See each proto message definition for details. Example: type: google.api.Service config_version: 3 name: calendar.googleapis.com title: Google Calendar API apis: - name: google.calendar.v3.Calendar authentication: providers: - id: google_calendar_auth jwks_uri: https://www.googleapis.com/oauth2/v1/certs issuer: https://securetoken.google.com rules: - selector: "*" requirements: provider_id: google_calendar_auth

Used as response type in: servicemanagement.v1.ServiceManager.CreateServiceConfig, servicemanagement.v1.ServiceManager.GetServiceConfig

Used as field type in: servicemanagement.v1.CreateServiceConfigRequest, servicemanagement.v1.ListServiceConfigsResponse, servicemanagement.v1.SubmitConfigSourceResponse

• optional protobuf.UInt32Value config_version = 20

  The semantic version of the service configuration. The config version affects the interpretation of the service configuration. For example, certain features are enabled by default for certain config versions. The latest config version is `3`.

• string name = 1

  The DNS address at which this service is available, e.g. `calendar.googleapis.com`.

• string id = 33

  A unique ID for a specific instance of this message, typically assigned by the client for tracking purpose. If empty, the server may choose to generate one instead.

• string title = 2

  The product title for this service.

• string producer_project_id = 22

  The Google project that owns this service.

• repeated protobuf.Api apis = 3

  A list of API interfaces exported by this service. Only the `name` field of the [google.protobuf.Api][google.protobuf.Api] needs to be provided by the configuration author, as the remaining fields will be derived from the IDL during the normalization process. It is an error to specify an API interface here which cannot be resolved against the associated IDL files.

• repeated protobuf.Type types = 4

  A list of all proto message types included in this API service. Types referenced directly or indirectly by the `apis` are automatically included. Messages which are not referenced but shall be included, such as types used by the `google.protobuf.Any` type, should be listed here by name. Example: types: - name: google.protobuf.Int32

• repeated protobuf.Enum enums = 5

  A list of all enum types included in this API service. Enums referenced directly or indirectly by the `apis` are automatically included. Enums which are not referenced but shall be included should be listed here by name. Example: enums: - name: google.someapi.v1.SomeEnum

• optional Documentation documentation = 6

  Additional API documentation.

• optional Backend backend = 8

  API backend configuration.

• optional Http http = 9

  HTTP configuration.

• optional Quota quota = 10

  Quota configuration.

• optional Authentication authentication = 11

  Auth configuration.

• optional Context context = 12

  Context configuration.

• optional Usage usage = 15

  Configuration controlling usage of this service.

• repeated Endpoint endpoints = 18

  Configuration for network endpoints. If this is empty, then an endpoint with the same name as the service is automatically generated to service all defined APIs.

• optional Control control = 21

  Configuration for the service control plane.

• repeated LogDescriptor logs = 23

  Defines the logs used by this service.

• repeated MetricDescriptor metrics = 24

  Defines the metrics used by this service.

• repeated MonitoredResourceDescriptor monitored_resources = 25

  Defines the monitored resources used by this service. This is required by the [Service.monitoring][google.api.Service.monitoring] and [Service.logging][google.api.Service.logging] configurations.

• optional Billing billing = 26

  Billing configuration.

• optional Logging logging = 27

  Logging configuration.

• optional Monitoring monitoring = 28

  Monitoring configuration.

• optional SystemParameters system_parameters = 29

  System parameter configuration.

• optional SourceInfo source_info = 37

  Output only. The source information for this configuration if available.

• optional Experimental experimental = 101

  Experimental configuration.

Source information used to create a Service Config

Used in: Service

• repeated protobuf.Any source_files = 1

  All files used during config generation.

Define a parameter's name and location. The parameter may be passed as either an HTTP header or a URL query parameter, and if both are passed the behavior is implementation-dependent.

Used in: SystemParameterRule

• string name = 1

  Define the name of the parameter, such as "api_key" . It is case sensitive.

• string http_header = 2

  Define the HTTP header name to use for the parameter. It is case insensitive.

• string url_query_parameter = 3

  Define the URL query parameter name to use for the parameter. It is case sensitive.

Define a system parameter rule mapping system parameter definitions to methods.

Used in: SystemParameters

• string selector = 1

  Selects the methods to which this rule applies. Use '*' to indicate all methods in all APIs. Refer to [selector][google.api.DocumentationRule.selector] for syntax details.

• repeated SystemParameter parameters = 2

  Define parameters. Multiple names may be defined for a parameter. For a given method call, only one of them should be used. If multiple names are used the behavior is implementation-dependent. If none of the specified names are present the behavior is parameter-dependent.

### System parameter configuration A system parameter is a special kind of parameter defined by the API system, not by an individual API. It is typically mapped to an HTTP header and/or a URL query parameter. This configuration specifies which methods change the names of the system parameters.

Used in: Service

• repeated SystemParameterRule rules = 1

  Define system parameters. The parameters defined here will override the default parameters implemented by the system. If this field is missing from the service config, default system parameters will be used. Default system parameters and names is implementation-dependent. Example: define api key for all methods system_parameters rules: - selector: "*" parameters: - name: api_key url_query_parameter: api_key Example: define 2 api key names for a specific method. system_parameters rules: - selector: "/ListShelves" parameters: - name: api_key http_header: Api-Key1 - name: api_key http_header: Api-Key2 **NOTE:** All service configuration rules follow "last one wins" order.

Configuration controlling usage of a service.

Used in: Service

• repeated string requirements = 1

  Requirements that must be satisfied before a consumer project can use the service. Each requirement is of the form <service.name>/<requirement-id>; for example 'serviceusage.googleapis.com/billing-enabled'.

• repeated UsageRule rules = 6

  A list of usage rules that apply to individual API methods. **NOTE:** All service configuration rules follow "last one wins" order.

• string producer_notification_channel = 7

  The full resource name of a channel used for sending notifications to the service producer. Google Service Management currently only supports [Google Cloud Pub/Sub](https://cloud.google.com/pubsub) as a notification channel. To use Google Cloud Pub/Sub as the channel, this must be the name of a Cloud Pub/Sub topic that uses the Cloud Pub/Sub topic name format documented in https://cloud.google.com/pubsub/docs/overview.

Usage configuration rules for the service. NOTE: Under development. Use this rule to configure unregistered calls for the service. Unregistered calls are calls that do not contain consumer project identity. (Example: calls that do not contain an API key). By default, API methods do not allow unregistered calls, and each method call must be identified by a consumer project identity. Use this rule to allow/disallow unregistered calls. Example of an API that wants to allow unregistered calls for entire service. usage: rules: - selector: "*" allow_unregistered_calls: true Example of a method that wants to allow unregistered calls. usage: rules: - selector: "google.example.library.v1.LibraryService.CreateBook" allow_unregistered_calls: true

Used in: Usage

• string selector = 1

  Selects the methods to which this rule applies. Use '*' to indicate all methods in all APIs. Refer to [selector][google.api.DocumentationRule.selector] for syntax details.

• bool allow_unregistered_calls = 2

  If true, the selected method allows unregistered calls, e.g. calls that don't identify any user or application.

• bool skip_service_control = 3

  If true, the selected method should skip service control and the control plane features, such as quota and billing, will not be available. This flag is used by Google Cloud Endpoints to bypass checks for internal methods, such as service health check methods.