​

ves-io-schema-status_at_site-CustomAPI-GetStatus

Published April 5, 2023 | Last modified October 28, 2026

Examples of performing status_at_site CustomAPI GetStatus

Usecase:

Perform GetStatus on status_at_site

Request:

Request using vesctl:

vesctl request rpc status_at_site.CustomAPI.GetStatus -i request.yaml --uri /public/namespaces/namespace-literal/kind-literal/name-literal/status_at_site --http-method GET

where file request.yaml has following contents:

{}

vesctl yaml response:

conditions: []

Request using curl:

curl -X 'GET' -H 'Content-Type: application/json' -H 'X-Volterra-Useragent: v1/pgm=_var_folders_q2_3kp8z3zs0x5_m7pk1bgb0_ph0000gp_T_go-build3348201650_b001_apidocs.test/host=MTY6VVHQPH/svc=S:examplesvc/site=mytestce01' 'https://acmecorp.console.ves.volterra.io/api/data/namespaces/namespace-literal/kind-literal/name-literal/status_at_site?kind=&name=&namespace=&site=&site_type=INVALID'

curl response:

HTTP/1.1 200 OK
Content-Length: 42
Content-Type: application/json
Date: Mon, 28 Sep 2026 04:30:02 GMT
Vary: Accept-Encoding


{
  "error": null,
  "conditions": [
  ]
}
On this page: