---
title: "POST /v1/{+appConnector}:reportStatus"
method: POST
path: "/v1/{+appConnector}:reportStatus"
tags: ["projects"]
---

# POST /v1/{+appConnector}:reportStatus

`POST /v1/{+appConnector}:reportStatus`

Report status for a given connector.

## Path parameters

- `appConnector` string, required

## Request body

- GoogleCloudBeyondcorpAppconnectorsV1ReportStatusRequest — Request report the connector status.
  - `validateOnly` boolean — Optional. If set, validates request by executing a dry-run which would not alter the resource in any way.
  - `resourceInfo` GoogleCloudBeyondcorpAppconnectorsV1ResourceInfo — ResourceInfo represents the information or status of an app connector resource component that's used to report on various parts of the system. For example, ResourceInfo can be used to convey the status of a remote_agent, including the status of an appgateway for an runtime environment in a container instance.
    - `time` string, google-datetime — The timestamp to collect the info. It is suggested to be set by the topmost level resource only.
    - `resource` object — Specific details for the resource. This is for internal use only.
    - `sub` GoogleCloudBeyondcorpAppconnectorsV1ResourceInfo[] — List of Info for the sub level resources.
    - `id` string — Required. Unique Id for the resource.
    - `status` 'HEALTH_STATUS_UNSPECIFIED' | 'HEALTHY' | 'UNHEALTHY' | 'UNRESPONSIVE' | 'DEGRADED' — Overall health status. Overall status is derived based on the status of each sub level resources.
  - `requestId` string — Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).

## Response `200`

Successful response

---

[API](https://skmtc.dev/google/apis/beyondcorp.md) · [All operations](https://skmtc.dev/google/apis/beyondcorp/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/google/beyondcorp/revisions/e86980a523a5/schema)
