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 PatchEnvelopeConfiguration API

The PatchEnvelopeConfiguration API from Zededa — 4 operation(s) for patchenvelopeconfiguration.

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

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

This API exposes 7 operations across 4 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

7 operations 4 paths 21 schemas 1 DELETE4 GET1 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 PatchEnvelopeConfiguration 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 7

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

PatchEnvelopeConfiguration 7
GET
/v1/patch-envelope
Get all the patch envelopes
PatchEnvelopeConfiguration_GetPatchEnvelope 9 params → 200401403500504default
POST
/v1/patch-envelope
Create patch envelope
PatchEnvelopeConfiguration_CreatePatchEnvelope 1 param body → 200401403500504default
GET
/v1/patch-envelope/id/{id}
Get patch envelope by id
PatchEnvelopeConfiguration_GetPatchEnvelopeById 2 params → 200401403404500504default
DELETE
/v1/patch-envelope/id/{id}
Delete patch envelope
PatchEnvelopeConfiguration_DeleteAppInstanceSnapshot 2 params → 200401403404500504default
PUT
/v1/patch-envelope/id/{id}
Update patch envelope
PatchEnvelopeConfiguration_UpdatePatchEnvelope 2 params body → 200401403404500504default
GET
/v1/patch-envelope/name/{name}
Get patch envelope by name
PatchEnvelopeConfiguration_GetPatchEnvelopeByName 2 params → 200401403404500504default
GET
/v1/patch-envelope/status
Get patch envelope status
PatchEnvelopeConfiguration_GetPatchEnvelopeStatus 9 params → 200401403500504default

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are ZsrvResponse (15 properties), PatchEnvelope (11 properties), PatchEnvelopeStatus (9 properties), ObjectRevision (6 properties). Each schema is shown below with its type and property counts.

BinaryArtifact
object
5 properties
PatchEnvelope
object
PatchEnvelope is a proto that should be used by user-agents to create/update opaque data for application instances.
11 properties 4 required
PatchEnvelopeStatus
object
PatchEnvelopeStatus encapsulates the status of an patch envelope
9 properties
ZsrvError
object
3 properties
Summary
object
Summary is used to store the Summary details
3 properties
protobufAny
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
PatchEnvelopeState
string
InlineOpaqueBase64Data
object
3 properties
ZcOpsType
string
ZsrvResponse
object
15 properties
ObjectType
string
ZcOpsStatus
string
- OPSSTATUSPENDING: In rare cases, system may not start operation when it was requested. Client will be notified that operation is PENDING - OPSSTATUSONGOING:…
PatchStatusListMsg
object
3 properties
googlerpcStatus
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
ZsrvErrorCode
string
- zMsgErrorNone: common validation errors - IncompleteData: message had fields that weren't filled in - InvalidData: message contained the field that wasn't ex…
ExternalOpaqueBinaryBlob
object
4 properties
OpaqueObjectCategory
string
PatchEnvelopeList
object
4 properties
PatchEnvelopeAction
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zededa-patchenvelopeconfiguration-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 CloudDiagnostics API
Zededa ClusterGroups API
Zededa ClusterStatus API
Zededa DatastoreConfiguration API
Zededa EdgeApplicationConfiguration API
Zededa EdgeApplicationInstanceConfiguration API
Zededa EdgeApplicationInstanceStatus API
Where this information came from

This is an independent, third-party profile of Zededa PatchEnvelopeConfiguration 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.