Skip to main content

Referrer_ExportParodies​

Referrer_ExportParodies

Responses

OK

Schema
  • name string

    The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the name should be a resource name ending with operations/{unique_id}.

  • metadata object

    Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

    • @type string

      The type of the serialized message.

  • done boolean

    If the value is false, it means the operation is still in progress. If true, the operation is completed, and either error or response is available.

  • error object

    The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

    • code int32

      The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

    • message string

      A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

    • details object[]

      A list of messages that carry the error details. There is a common set of message types for APIs to use.

      • @type string

        The type of the serialized message.

  • response object

    Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

    • @type string

      The type of the serialized message.