How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zededa CloudDiagnostics API

The CloudDiagnostics API from Zededa — 8 operation(s) for clouddiagnostics.

Zededa CloudDiagnostics API is one of 35 APIs that Zededa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include CloudDiagnostics. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 8 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, /api.

10 operations 8 paths 23 schemas 1 DELETE6 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://zedcontrol.zededa.net/api
Authentication
API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Zededa CloudDiagnostics API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (BearerToken). By default, every request must be authenticated.

  • BearerToken — Bearer token for user session

Paths & Operations 10

Across 8 paths, the API surfaces 10 operations — 1 DELETE, 6 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

CloudDiagnostics 10
GET
/v1/cloud/healthreport
Get Cloud services health report
CloudDiagnostics_GetClusterHealthReport 1 param → 200500504default
GET
/v1/cloud/ping
Check Cloud reachability
CloudDiagnostics_checkClusterHealth 2 params → 200500504default
GET
/v1/cloud/ping/id/{pingId}
Check Cloud reachability
CloudDiagnostics_checkClusterHealth2 2 params → 200500504default
GET
/v1/cloud/policies
Query Cloud policies
CloudDiagnostics_QueryCloudPolicies 2 params → 200500504default
POST
/v1/cloud/policies
Create Cloud policy document
CloudDiagnostics_CreateCloudPolicyDocument 1 param body → 200400500504default
GET
/v1/cloud/policies/id/{id}
Get Cloud policy document
CloudDiagnostics_GetCloudPolicyDocument 2 params → 200404500504default
DELETE
/v1/cloud/policies/id/{id}
Delete Cloud policy specific version
CloudDiagnostics_DeleteCloudPolicyDocument 2 params → 200404500504default
PUT
/v1/cloud/policies/latest
Update Cloud policy specific version
CloudDiagnostics_MarkCloudPolicyLatest 1 param body → 200400401403404500504default
GET
/v1/cloud/version
Get Cloud controller software version
CloudDiagnostics_GetClusterVersion 1 param → 200500504default
POST
/v1/hello
Check Cloud services health
CloudDiagnostics_checkMicroserviceHealth 1 param body → 200400500504default

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are ZsrvResponse (15 properties), ObjectRevision (6 properties), HealthDesc (5 properties), Cursor (5 properties). Each schema is shown below with its type and property counts.

HealthServiceSubType
string
ZsrvResponse
object
15 properties
HelloResp
object
1 property
ZsrvErrorCode
string
- zMsgErrorNone: common validation errors - IncompleteData: message had fields that weren't filled in - InvalidData: message contained the field that wasn't ex…
HelloName
object
4 properties
PingMsgSendResp
object
1 property
Summary
object
Summary is used to store the Summary details
3 properties
ObjectType
string
ZcOpsType
string
CloudVersion
object
2 properties
Cursor
object
Cursor helps in filtering the various list response like edge-app bundle list, model list, bundle list etc.
5 properties
PolicyDocVersionResp
object
3 properties
protobufAny
object
2 properties
PolicyDocVersionList
object
3 properties
HealthServiceResp
object
3 properties
googlerpcStatus
object
3 properties
ZsrvError
object
3 properties
ObjectRevision
object
ObjectRevision store the user details, who has doent the necessary operation like Create Operation or update operation
6 properties 5 required
CloudVersionResp
object
2 properties
HealthDesc
object
5 properties
PolicyDocVersion
object
4 properties
BriefHealth
object
1 property
ZcOpsStatus
string
- OPSSTATUSPENDING: In rare cases, system may not start operation when it was requested. Client will be notified that operation is PENDING - OPSSTATUSONGOING:…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zededa-clouddiagnostics-api-openapi.yml Raw ↑

Other APIs Zededa publishes across the network.

Zededa AppProfileService API
Zededa ArtifactManager API
Zededa AssetGroupService API
Zededa BulkJobOps API
Zededa CertificateEnrollmentProfileConfiguration API
Zededa ClusterStatus API
Zededa DatastoreConfiguration API
Zededa EdgeApplicationConfiguration API
Zededa EdgeApplicationInstanceConfiguration API
Zededa EdgeApplicationInstanceStatus API
Zededa EdgeDiagnostics API
Zededa EdgeNetworkConfiguration API
Where this information came from

This is an independent, third-party profile of Zededa CloudDiagnostics API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.