| OLD | NEW |
| 1 { | 1 { |
| 2 "auth": { | 2 "auth": { |
| 3 "oauth2": { | 3 "oauth2": { |
| 4 "scopes": { | 4 "scopes": { |
| 5 "https://www.googleapis.com/auth/cloud-platform": { | 5 "https://www.googleapis.com/auth/cloud-platform": { |
| 6 "description": "View and manage your data across Google Clou
d Platform services" | 6 "description": "View and manage your data across Google Clou
d Platform services" |
| 7 } | 7 } |
| 8 } | 8 } |
| 9 } | 9 } |
| 10 }, | 10 }, |
| (...skipping 250 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 261 "response": { | 261 "response": { |
| 262 "$ref": "Empty" | 262 "$ref": "Empty" |
| 263 }, | 263 }, |
| 264 "scopes": [ | 264 "scopes": [ |
| 265 "https://www.googleapis.com/auth/cloud-platform" | 265 "https://www.googleapis.com/auth/cloud-platform" |
| 266 ] | 266 ] |
| 267 } | 267 } |
| 268 } | 268 } |
| 269 } | 269 } |
| 270 }, | 270 }, |
| 271 "revision": "20160726", | 271 "revision": "20160824", |
| 272 "rootUrl": "https://speech.googleapis.com/", | 272 "rootUrl": "https://speech.googleapis.com/", |
| 273 "schemas": { | 273 "schemas": { |
| 274 "Status": { | 274 "Status": { |
| 275 "description": "The `Status` type defines a logical error model that
is suitable for different\nprogramming environments, including REST APIs and RP
C APIs. It is used by\n[gRPC](https://github.com/grpc). The error model is desig
ned to be:\n\n- Simple to use and understand for most users\n- Flexible enough t
o meet unexpected needs\n\n# Overview\n\nThe `Status` message contains three pie
ces of data: error code, error message,\nand error details. The error code shoul
d be an enum value of\ngoogle.rpc.Code, but it may accept additional error codes
if needed. The\nerror message should be a developer-facing English message tha
t helps\ndevelopers *understand* and *resolve* the error. If a localized user-fa
cing\nerror message is needed, put the localized message in the error details or
\nlocalize it in the client. The optional error details may contain arbitrary\ni
nformation about the error. There is a predefined set of error detail types\nin
the package `google.rpc` which can be used for common error conditions.\n\n# Lan
guage mapping\n\nThe `Status` message is the logical representation of the error
model, but it\nis not necessarily the actual wire format. When the `Status` mes
sage is\nexposed in different client libraries and different wire protocols, it
can be\nmapped differently. For example, it will likely be mapped to some except
ions\nin Java, but more likely mapped to some error codes in C.\n\n# Other uses\
n\nThe error model and the `Status` message can be used in a variety of\nenviron
ments, either with or without APIs, to provide a\nconsistent developer experienc
e across different environments.\n\nExample uses of this error model include:\n\
n- Partial errors. If a service needs to return partial errors to the client,\n
it may embed the `Status` in the normal response to indicate the partial\n
errors.\n\n- Workflow errors. A typical workflow has multiple steps. Each step
may\n have a `Status` message for error reporting purpose.\n\n- Batch operati
ons. If a client uses batch request and batch response, the\n `Status` messag
e should be used directly inside batch response, one for\n each error sub-res
ponse.\n\n- Asynchronous operations. If an API call embeds asynchronous operatio
n\n results in its response, the status of those operations should be\n re
presented directly using the `Status` message.\n\n- Logging. If some API errors
are stored in logs, the message `Status` could\n be used directly after any s
tripping needed for security/privacy reasons.", | 275 "description": "The `Status` type defines a logical error model that
is suitable for different\nprogramming environments, including REST APIs and RP
C APIs. It is used by\n[gRPC](https://github.com/grpc). The error model is desig
ned to be:\n\n- Simple to use and understand for most users\n- Flexible enough t
o meet unexpected needs\n\n# Overview\n\nThe `Status` message contains three pie
ces of data: error code, error message,\nand error details. The error code shoul
d be an enum value of\ngoogle.rpc.Code, but it may accept additional error codes
if needed. The\nerror message should be a developer-facing English message tha
t helps\ndevelopers *understand* and *resolve* the error. If a localized user-fa
cing\nerror message is needed, put the localized message in the error details or
\nlocalize it in the client. The optional error details may contain arbitrary\ni
nformation about the error. There is a predefined set of error detail types\nin
the package `google.rpc` which can be used for common error conditions.\n\n# Lan
guage mapping\n\nThe `Status` message is the logical representation of the error
model, but it\nis not necessarily the actual wire format. When the `Status` mes
sage is\nexposed in different client libraries and different wire protocols, it
can be\nmapped differently. For example, it will likely be mapped to some except
ions\nin Java, but more likely mapped to some error codes in C.\n\n# Other uses\
n\nThe error model and the `Status` message can be used in a variety of\nenviron
ments, either with or without APIs, to provide a\nconsistent developer experienc
e across different environments.\n\nExample uses of this error model include:\n\
n- Partial errors. If a service needs to return partial errors to the client,\n
it may embed the `Status` in the normal response to indicate the partial\n
errors.\n\n- Workflow errors. A typical workflow has multiple steps. Each step
may\n have a `Status` message for error reporting purpose.\n\n- Batch operati
ons. If a client uses batch request and batch response, the\n `Status` messag
e should be used directly inside batch response, one for\n each error sub-res
ponse.\n\n- Asynchronous operations. If an API call embeds asynchronous operatio
n\n results in its response, the status of those operations should be\n re
presented directly using the `Status` message.\n\n- Logging. If some API errors
are stored in logs, the message `Status` could\n be used directly after any s
tripping needed for security/privacy reasons.", |
| 276 "id": "Status", | 276 "id": "Status", |
| 277 "properties": { | 277 "properties": { |
| 278 "code": { | 278 "code": { |
| 279 "description": "The status code, which should be an enum val
ue of google.rpc.Code.", | 279 "description": "The status code, which should be an enum val
ue of google.rpc.Code.", |
| 280 "format": "int32", | 280 "format": "int32", |
| 281 "type": "integer" | 281 "type": "integer" |
| (...skipping 10 matching lines...) Expand all Loading... |
| 292 "type": "array" | 292 "type": "array" |
| 293 }, | 293 }, |
| 294 "message": { | 294 "message": { |
| 295 "description": "A developer-facing error message, which shou
ld be in English. Any\nuser-facing error message should be localized and sent in
the\ngoogle.rpc.Status.details field, or localized by the client.", | 295 "description": "A developer-facing error message, which shou
ld be in English. Any\nuser-facing error message should be localized and sent in
the\ngoogle.rpc.Status.details field, or localized by the client.", |
| 296 "type": "string" | 296 "type": "string" |
| 297 } | 297 } |
| 298 }, | 298 }, |
| 299 "type": "object" | 299 "type": "object" |
| 300 }, | 300 }, |
| 301 "RecognitionAudio": { | 301 "RecognitionAudio": { |
| 302 "description": "Contains audio data in the encoding specified in the
`RecognitionConfig`.\nEither `content` or `uri` must be supplied. Supplying bot
h or neither\nreturns google.rpc.Code.INVALID_ARGUMENT.", | 302 "description": "Contains audio data in the encoding specified in the
`RecognitionConfig`.\nEither `content` or `uri` must be supplied. Supplying bot
h or neither\nreturns google.rpc.Code.INVALID_ARGUMENT. See\n[audio limits](http
s://cloud.google.com/speech/limits#content).", |
| 303 "id": "RecognitionAudio", | 303 "id": "RecognitionAudio", |
| 304 "properties": { | 304 "properties": { |
| 305 "content": { | 305 "content": { |
| 306 "description": "The audio data bytes encoded as specified in
\n`RecognitionConfig`. Note: as with all bytes fields, protobuffers use a\npure
binary representation, whereas JSON representations use base64.", | 306 "description": "The audio data bytes encoded as specified in
\n`RecognitionConfig`. Note: as with all bytes fields, protobuffers use a\npure
binary representation, whereas JSON representations use base64.", |
| 307 "format": "byte", | 307 "format": "byte", |
| 308 "type": "string" | 308 "type": "string" |
| 309 }, | 309 }, |
| 310 "uri": { | 310 "uri": { |
| 311 "description": "URI that points to a file that contains audi
o data bytes as specified in\n`RecognitionConfig`. Currently, only Google Cloud
Storage URIs are\nsupported, which must be specified in the following format:\n`
gs://bucket_name/object_name` (other URI formats return\ngoogle.rpc.Code.INVALID
_ARGUMENT). For more information, see\n[Request URIs](/storage/docs/reference-ur
is).", | 311 "description": "URI that points to a file that contains audi
o data bytes as specified in\n`RecognitionConfig`. Currently, only Google Cloud
Storage URIs are\nsupported, which must be specified in the following format:\n`
gs://bucket_name/object_name` (other URI formats return\ngoogle.rpc.Code.INVALID
_ARGUMENT). For more information, see\n[Request URIs](https://cloud.google.com/s
torage/docs/reference-uris).", |
| 312 "type": "string" | 312 "type": "string" |
| 313 } | 313 } |
| 314 }, | 314 }, |
| 315 "type": "object" | 315 "type": "object" |
| 316 }, | 316 }, |
| 317 "Operation": { | 317 "Operation": { |
| 318 "description": "This resource represents a long-running operation th
at is the result of a\nnetwork API call.", | 318 "description": "This resource represents a long-running operation th
at is the result of a\nnetwork API call.", |
| 319 "id": "Operation", | 319 "id": "Operation", |
| 320 "properties": { | 320 "properties": { |
| 321 "error": { | 321 "error": { |
| (...skipping 52 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 374 "RecognitionConfig": { | 374 "RecognitionConfig": { |
| 375 "description": "The `RecognitionConfig` message provides information
to the recognizer\nthat specifies how to process the request.", | 375 "description": "The `RecognitionConfig` message provides information
to the recognizer\nthat specifies how to process the request.", |
| 376 "id": "RecognitionConfig", | 376 "id": "RecognitionConfig", |
| 377 "properties": { | 377 "properties": { |
| 378 "maxAlternatives": { | 378 "maxAlternatives": { |
| 379 "description": "[Optional] Maximum number of recognition hyp
otheses to be returned.\nSpecifically, the maximum number of `SpeechRecognitionA
lternative` messages\nwithin each `SpeechRecognitionResult`.\nThe server may ret
urn fewer than `max_alternatives`.\nValid values are `0`-`30`. A value of `0` or
`1` will return a maximum of\n`1`. If omitted, defaults to `1`.", | 379 "description": "[Optional] Maximum number of recognition hyp
otheses to be returned.\nSpecifically, the maximum number of `SpeechRecognitionA
lternative` messages\nwithin each `SpeechRecognitionResult`.\nThe server may ret
urn fewer than `max_alternatives`.\nValid values are `0`-`30`. A value of `0` or
`1` will return a maximum of\n`1`. If omitted, defaults to `1`.", |
| 380 "format": "int32", | 380 "format": "int32", |
| 381 "type": "integer" | 381 "type": "integer" |
| 382 }, | 382 }, |
| 383 "languageCode": { | 383 "languageCode": { |
| 384 "description": "[Optional] The language of the supplied audi
o as a BCP-47 language tag.\nExample: \"en-GB\" https://www.rfc-editor.org/rfc/
bcp/bcp47.txt\nIf omitted, defaults to \"en-US\". See\n[Language Support](/speec
h/docs/best-practices#language_support) for\na list of the currently supported l
anguage codes.", | 384 "description": "[Optional] The language of the supplied audi
o as a BCP-47 language tag.\nExample: \"en-GB\" https://www.rfc-editor.org/rfc/
bcp/bcp47.txt\nIf omitted, defaults to \"en-US\". See\n[Language Support](https:
//cloud.google.com/speech/docs/best-practices#language_support)\nfor a list of t
he currently supported language codes.", |
| 385 "type": "string" | 385 "type": "string" |
| 386 }, | 386 }, |
| 387 "speechContext": { | 387 "speechContext": { |
| 388 "$ref": "SpeechContext", | 388 "$ref": "SpeechContext", |
| 389 "description": "[Optional] A means to provide context to ass
ist the speech recognition." | 389 "description": "[Optional] A means to provide context to ass
ist the speech recognition." |
| 390 }, | 390 }, |
| 391 "encoding": { | 391 "encoding": { |
| 392 "description": "[Required] Encoding of audio data sent in al
l `RecognitionAudio` messages.", | 392 "description": "[Required] Encoding of audio data sent in al
l `RecognitionAudio` messages.", |
| 393 "enum": [ | 393 "enum": [ |
| 394 "ENCODING_UNSPECIFIED", | 394 "ENCODING_UNSPECIFIED", |
| (...skipping 90 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 485 "description": "A generic empty message that you can re-use to avoid
defining duplicated\nempty messages in your APIs. A typical example is to use i
t as the request\nor the response type of an API method. For instance:\n\n se
rvice Foo {\n rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty
);\n }\n\nThe JSON representation for `Empty` is empty JSON object `{}`.", | 485 "description": "A generic empty message that you can re-use to avoid
defining duplicated\nempty messages in your APIs. A typical example is to use i
t as the request\nor the response type of an API method. For instance:\n\n se
rvice Foo {\n rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty
);\n }\n\nThe JSON representation for `Empty` is empty JSON object `{}`.", |
| 486 "id": "Empty", | 486 "id": "Empty", |
| 487 "properties": {}, | 487 "properties": {}, |
| 488 "type": "object" | 488 "type": "object" |
| 489 }, | 489 }, |
| 490 "SpeechContext": { | 490 "SpeechContext": { |
| 491 "description": "Provides \"hints\" to the speech recognizer to favor
specific words and phrases\nin the results.", | 491 "description": "Provides \"hints\" to the speech recognizer to favor
specific words and phrases\nin the results.", |
| 492 "id": "SpeechContext", | 492 "id": "SpeechContext", |
| 493 "properties": { | 493 "properties": { |
| 494 "phrases": { | 494 "phrases": { |
| 495 "description": "[Optional] A list of up to 50 phrases of up
to 100 characters each to\nprovide words and phrases \"hints\" to the speech rec
ognition so that it is\nmore likely to recognize them.", | 495 "description": "[Optional] A list of strings containing word
s and phrases \"hints\" so that\nthe speech recognition is more likely to recogn
ize them. This can be used\nto improve the accuracy for specific words and phras
es, for example, if\nspecific commands are typically spoken by the user. This ca
n also be used\nto add additional words to the vocabulary of the recognizer. See
\n[usage limits](https://cloud.google.com/speech/limits#content).", |
| 496 "items": { | 496 "items": { |
| 497 "type": "string" | 497 "type": "string" |
| 498 }, | 498 }, |
| 499 "type": "array" | 499 "type": "array" |
| 500 } | 500 } |
| 501 }, | 501 }, |
| 502 "type": "object" | 502 "type": "object" |
| 503 }, | 503 }, |
| 504 "AsyncRecognizeRequest": { | 504 "AsyncRecognizeRequest": { |
| 505 "description": "`AsyncRecognizeRequest` is the top-level message sen
t by the client for\nthe `AsyncRecognize` method.", | 505 "description": "`AsyncRecognizeRequest` is the top-level message sen
t by the client for\nthe `AsyncRecognize` method.", |
| 506 "id": "AsyncRecognizeRequest", | 506 "id": "AsyncRecognizeRequest", |
| 507 "properties": { | 507 "properties": { |
| 508 "audio": { | 508 "audio": { |
| 509 "$ref": "RecognitionAudio", | 509 "$ref": "RecognitionAudio", |
| 510 "description": "[Required] The audio data to be recognized." | 510 "description": "[Required] The audio data to be recognized." |
| 511 }, | 511 }, |
| 512 "config": { | 512 "config": { |
| 513 "$ref": "RecognitionConfig", | 513 "$ref": "RecognitionConfig", |
| 514 "description": "[Required] The `config` message provides inf
ormation to the recognizer\nthat specifies how to process the request." | 514 "description": "[Required] The `config` message provides inf
ormation to the recognizer\nthat specifies how to process the request." |
| 515 } | 515 } |
| 516 }, | 516 }, |
| 517 "type": "object" | 517 "type": "object" |
| 518 } | 518 } |
| 519 }, | 519 }, |
| 520 "servicePath": "", | 520 "servicePath": "", |
| 521 "title": "Google Cloud Speech API", | 521 "title": "Google Cloud Speech API", |
| 522 "version": "v1beta1" | 522 "version": "v1beta1" |
| 523 } | 523 } |
| OLD | NEW |