Zededa DatastoreConfiguration API
The DatastoreConfiguration API from Zededa — 4 operation(s) for datastoreconfiguration.
The DatastoreConfiguration API from Zededa — 4 operation(s) for datastoreconfiguration.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/zededa-datastoreconfiguration-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: ZEDEDA App Profiles Service AppProfileService Datastore Configuration API
description: The ZEDEDA App Profiles Service is part of ZEDEDA Edge Orchestration Platform. This service enables customers to define their app profiles on ZEDEDA platform and to manage them remotely.
termsOfService: https://www.zededa.com/terms
version: '1.0'
contact:
name: ZEDEDA API Support
url: https://www.zededa.com/support
email: support@zededa.com
license:
name: Apache 2.0
url: http://www.apache.org/licenses/LICENSE-2.0.html
servers:
- url: /api
security:
- BearerToken: []
tags:
- name: DatastoreConfiguration
paths:
/v1/datastores:
get:
summary: Query datastores
description: Query the datastore records.
operationId: DatastoreConfiguration_QueryDatastores
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/Datastores'
'400':
description: Bad Request. The API gateway did not process the request because of invalid value of filter parameters.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'401':
description: Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'403':
description: Forbidden. The API gateway did not process the request because the requestor does not have edge-node level access permission for the operation or does not have access scope to the project.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'500':
description: Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'504':
description: Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
default:
description: An unexpected error response.
content:
application/json:
schema:
$ref: '#/components/schemas/googlerpcStatus'
parameters:
- name: summary
description: Only summary of the records required
in: query
required: false
schema:
type: boolean
- name: namePattern
description: Datastore name pattern to be matched.
in: query
required: false
schema:
type: string
- name: dsType
description: Datastore type to be matched
in: query
required: false
schema:
type: integer
format: int32
- name: originType
description: origin of datastore
in: query
required: false
schema:
type: integer
format: int32
- name: next.pageToken
description: Page Token
in: query
required: false
schema:
type: string
- name: next.orderBy
description: OrderBy helps in sorting the list response
in: query
required: false
style: form
explode: true
schema:
type: array
items:
type: string
- name: next.pageNum
description: Page Number
in: query
required: false
schema:
type: number
format: int64
- name: next.pageSize
description: Defines the page size
in: query
required: false
schema:
type: number
format: int64
- name: next.totalPages
description: Total number of pages to be fetched.
in: query
required: false
schema:
type: number
format: int64
- name: X-Request-Id
in: header
required: false
description: User-Agent specified id to track a request
schema:
type: string
tags:
- DatastoreConfiguration
externalDocs:
description: ZEDEDA Product Documentation
url: https://docs.zededa.com/-M-8m8d8KqdLpfOgY_jo/storage
post:
summary: Create Datastore
description: Create a Datastore record.
operationId: DatastoreConfiguration_CreateDatastore
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'400':
description: Bad Request. The API gateway did not process the request because of missing parameter or invalid value of parameters.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'401':
description: Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'403':
description: Forbidden. The API gateway did not process the request because the requestor does not have edge-node level access permission for the operation or does not have access scope to the project.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'409':
description: Conflict. The API gateway did not process the request because this datastore record will conflict with an already existing datastore record.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'500':
description: Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'504':
description: Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
default:
description: An unexpected error response.
content:
application/json:
schema:
$ref: '#/components/schemas/googlerpcStatus'
parameters:
- name: X-Request-Id
in: header
required: false
description: User-Agent specified id to track a request
schema:
type: string
tags:
- DatastoreConfiguration
externalDocs:
description: ZEDEDA Product Documentation
url: https://docs.zededa.com/-M-8m8d8KqdLpfOgY_jo/storage
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/DatastoreInfo'
required: true
/v1/datastores/id/{id}:
get:
summary: Get datastore
description: Get the configuration (without security details) of a datastore record.
operationId: DatastoreConfiguration_GetDatastore
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/DatastoreInfo'
'401':
description: Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'403':
description: Forbidden. The API gateway did not process the request because the requestor does not have edge-node level access permission for the operation or does not have access scope to the project.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'404':
description: Not Found. The API gateway did not process the request because the requested resource could not be found.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'500':
description: Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'504':
description: Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
default:
description: An unexpected error response.
content:
application/json:
schema:
$ref: '#/components/schemas/googlerpcStatus'
parameters:
- name: id
description: System defined universally unique Id of the datastore
in: path
required: true
schema:
type: string
- name: X-Request-Id
in: header
required: false
description: User-Agent specified id to track a request
schema:
type: string
tags:
- DatastoreConfiguration
externalDocs:
description: ZEDEDA Product Documentation
url: https://docs.zededa.com/-M-8m8d8KqdLpfOgY_jo/storage
delete:
summary: Delete datastore
description: Delete a datastore record.
operationId: DatastoreConfiguration_DeleteDatastore
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'401':
description: Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'403':
description: Forbidden. The API gateway did not process the request because the requestor does not have edge-node level access permission for the operation or does not have access scope to the project.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'404':
description: Not Found. The API gateway did not process the request because the requested resource could not be found.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'409':
description: Conflict. The API gateway did not process the request because there are edge application images using this datastore
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'500':
description: Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'504':
description: Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
default:
description: An unexpected error response.
content:
application/json:
schema:
$ref: '#/components/schemas/googlerpcStatus'
parameters:
- name: id
description: System defined universally unique Id of the datastore
in: path
required: true
schema:
type: string
- name: X-Request-Id
in: header
required: false
description: User-Agent specified id to track a request
schema:
type: string
tags:
- DatastoreConfiguration
externalDocs:
description: ZEDEDA Product Documentation
url: https://docs.zededa.com/-M-8m8d8KqdLpfOgY_jo/storage
put:
summary: Update datastore
description: Update a datastore record. The usual pattern to update a datastore record is to retrieve the record and update with the modified values in a new body to update the datastore record.
operationId: DatastoreConfiguration_UpdateDatastore
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'401':
description: Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'403':
description: Forbidden. The API gateway did not process the request because the requestor does not have edge-node level access permission for the operation or does not have access scope to the project.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'404':
description: Not Found. The API gateway did not process the request because the requested resource could not be found.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'409':
description: Conflict. The API gateway did not process the request because this operation will conflict with an already existing datastore record.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'500':
description: Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'504':
description: Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
default:
description: An unexpected error response.
content:
application/json:
schema:
$ref: '#/components/schemas/googlerpcStatus'
parameters:
- name: id
description: System defined universally unique Id of the datastore.
in: path
required: true
schema:
type: string
- name: X-Request-Id
in: header
required: false
description: User-Agent specified id to track a request
schema:
type: string
tags:
- DatastoreConfiguration
externalDocs:
description: ZEDEDA Product Documentation
url: https://docs.zededa.com/-M-8m8d8KqdLpfOgY_jo/storage
requestBody:
content:
application/json:
schema:
type: object
properties:
name:
type: string
description: User defined name of the datastore, unique across the enterprise. Once datastore is created, name can’t be changed.
maxLength: 256
minLength: 3
pattern: '[a-zA-Z0-9][a-zA-Z0-9_.-]+'
uniqueItems: true
title:
type: string
description: User defined title of the datastore. Title can be changed at any time.
maxLength: 256
minLength: 3
pattern: '[a-zA-Z0-9]+[a-zA-Z0-9!-~ ]+'
description:
type: string
description: Detailed description of the datastore.
maxLength: 256
revision:
$ref: '#/components/schemas/ObjectRevision'
description: system defined info
readOnly: true
enterpriseId:
type: string
dsType:
$ref: '#/components/schemas/DatastoreType'
description: Datastore type
dsFQDN:
type: string
description: Datastore Fully Qualified Domain Name
dsPath:
type: string
description: Datastore relative path w.r.t. Datastore root
apiKey:
type: string
region:
type: string
description: Datastore region - valid for AWS S3 and Azure BlobStorage
dsStatus:
$ref: '#/components/schemas/DatastoreStatus'
description: Datastore status
dsErr:
type: string
description: Datastore validation detailed error/status message
readOnly: true
secret:
$ref: '#/components/schemas/DatastoreInfoSecrets'
description: Plain-text sensitive data
encryptedSecrets:
type: object
additionalProperties:
type: string
description: Internal - Encrypted sensitive data
readOnly: true
cryptoKey:
type: string
description: Internal - Encryption Key context
readOnly: true
originType:
$ref: '#/components/schemas/Origin'
description: Origin type of datastore.
readOnly: true
certificateChain:
$ref: '#/components/schemas/CertificateChain'
description: Certificate chain of the certificate
needClearText:
type: boolean
description: knob for sending creds in clear text
projectAccessList:
type: array
items:
type: string
description: project access list of the datastore
description: Datastore idetail
title: Datastore
required:
- name
- title
- dsType
- dsFQDN
- dsPath
required: true
/v1/datastores/name/{name}:
get:
summary: Get datastore
description: Get the configuration (without security details) of a datastore record.
operationId: DatastoreConfiguration_GetDatastoreByName
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/DatastoreInfo'
'401':
description: Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'403':
description: Forbidden. The API gateway did not process the request because the requestor does not have edge-node level access permission for the operation or does not have access scope to the project.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'404':
description: Not Found. The API gateway did not process the request because the requested resource could not be found.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'500':
description: Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'504':
description: Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
default:
description: An unexpected error response.
content:
application/json:
schema:
$ref: '#/components/schemas/googlerpcStatus'
parameters:
- name: name
description: User defined name of the datastore, unique across the enterprise. Once datastore is created, name can’t be changed.
in: path
required: true
schema:
type: string
- name: X-Request-Id
in: header
required: false
description: User-Agent specified id to track a request
schema:
type: string
tags:
- DatastoreConfiguration
externalDocs:
description: ZEDEDA Product Documentation
url: https://docs.zededa.com/-M-8m8d8KqdLpfOgY_jo/storage
/v1/datastores/projects:
get:
summary: Query the project access list among a list of datastore
description: Query the project access list among a list of datastore
operationId: DatastoreConfiguration_QueryDatastoreProjectList
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/DatastoreProjectList'
'400':
description: Bad Request. The API gateway did not process the request because of invalid value of filter parameters.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'401':
description: Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'403':
description: Forbidden. The API gateway did not process the request because the requestor does not have edge-node level access permission for the operation or does not have access scope to the project.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'500':
description: Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
'504':
description: Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request.
content:
application/json:
schema:
$ref: '#/components/schemas/ZsrvResponse'
default:
description: An unexpected error response.
content:
application/json:
schema:
$ref: '#/components/schemas/googlerpcStatus'
parameters:
- name: ids
description: List of datastore IDs
in: query
required: false
style: form
explode: true
schema:
type: array
items:
type: string
- name: next.pageToken
description: Page Token
in: query
required: false
schema:
type: string
- name: next.orderBy
description: OrderBy helps in sorting the list response
in: query
required: false
style: form
explode: true
schema:
type: array
items:
type: string
- name: next.pageNum
description: Page Number
in: query
required: false
schema:
type: number
format: int64
- name: next.pageSize
description: Defines the page size
in: query
required: false
schema:
type: number
format: int64
- name: next.totalPages
description: Total number of pages to be fetched.
in: query
required: false
schema:
type: number
format: int64
- name: X-Request-Id
in: header
required: false
description: User-Agent specified id to track a request
schema:
type: string
tags:
- DatastoreConfiguration
externalDocs:
description: ZEDEDA Product Documentation
url: https://docs.zededa.com/-M-8m8d8KqdLpfOgY_jo/storage
components:
schemas:
ZsrvError:
type: object
properties:
ec:
$ref: '#/components/schemas/ZsrvErrorCode'
title: 'Enumrated error code, describes more granular numerical
value than just httpStatus'
location:
type: string
title: 'Ignore: Internal field only'
details:
type: string
title: Field captures string description of details
Origin:
type: string
enum:
- ORIGIN_UNSPECIFIED
- ORIGIN_IMPORTED
- ORIGIN_LOCAL
- ORIGIN_GLOBAL
- ORIGIN_APP_PROFILE_LOCAL
default: ORIGIN_UNSPECIFIED
description: "- ORIGIN_UNSPECIFIED: default options, which says no Operation/Invalid Operation\n - ORIGIN_IMPORTED: Object imported from global enterprise.\n - ORIGIN_LOCAL: Objectl created locally.\n - ORIGIN_GLOBAL: Object created in global store,\nto use this type user should have root previlage.\n - ORIGIN_APP_PROFILE_LOCAL: Object created via App profile"
title: 'OriginType : enum specifies the Object orgigin type'
Datastores:
type: object
properties:
summaryByType:
$ref: '#/components/schemas/Summary'
description: Type distribution summary of filtered Datastore records
list:
type: array
items:
$ref: '#/components/schemas/DatastoreInfo'
description: List of filtered Datastore records
summaryByCategory:
$ref: '#/components/schemas/Summary'
description: Category distribution summary of filtered Datastore records
summaryByOrigin:
$ref: '#/components/schemas/Summary'
description: datstore by origin summary
next:
$ref: '#/components/schemas/Cursor'
description: Responded page details of filtered records
CertificateChain:
type: object
properties:
certificates:
type: array
items:
$ref: '#/components/schemas/Certificate'
description: List of Certificate object holds the details of certificate like cert block, encryption type, validity, subject etc
Summary:
type: object
properties:
description:
type: string
description: Summary description
total:
type: number
format: int64
description: Total
values:
type: object
additionalProperties:
type: integer
format: int64
description: 'Values: Map for storing <string, uint32>'
description: Summary is used to store the Summary details
title: Summary is used to store the Summary details
protobufAny:
type: object
properties:
typeUrl:
type: string
value:
type: string
format: byte
Certificate:
type: object
properties:
cert:
type: string
description: base64 string of the parent certificate
title: certificate details
pvtKey:
type: string
description: base64 string of the parent pvt key
publicKey:
type: string
description: base63 string of the public key
passPhrase:
type: string
description: pass phase for the pvt key, this has to be filled if pvt key is encrypted with a pass phrase
exportable:
type: boolean
description: Indicates if the private key can be exported.
reuseKey:
type: boolean
description: Indicates if the same key pair will be used on certificate renewal.
encryptedSecrets:
type: object
additionalProperties:
type: string
description: user encrypted secrets map
title: secrets encryption
cryptoKey:
type: string
description: Crypto Key for decrypting user secret information
publicKeyAlgorithm:
type: string
description: Public key algorithm.
title: encryption algorithm
rsaEcryption:
$ref: '#/components/schemas/RSA'
description: RSA encryption algorithm of the certificate
ecdsaEncryption:
$ref: '#/components/schemas/ECDSA'
description: ECDSA encryption algorithm of the certificate
validFrom:
type: string
format: date-time
description: Certificate validatity start time
title: certificate validity
validTill:
type: string
format: date-time
description: Certificate validatity start time
sanValues:
$ref: '#/components/schemas/SANValues'
description: This holds the alternative name values like URIs, domain names IPs etc.
title: Subject alternative name values
subject:
$ref: '#/components/schemas/Subject'
description: Parameters for the subject of the X509 component of a certificate.
issuer:
$ref: '#/components/schemas/Subject'
description: Parameters for the issuer of the X509 component of a certificate.
serialNumber:
type: string
description: 'Unique identifier for each Certificate generated by an Certificate Issuer. '
basicContraintsValid:
type: boolean
description: This fields tells the basic constraints like isCA are correct.
keyUsage:
type: integer
format: int32
description: Key usage e
# --- truncated at 32 KB (47 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/zededa/refs/heads/main/openapi/zededa-datastoreconfiguration-api-openapi.yml