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

Nasuni Edge Appliances (Edge) API

The Edge Appliances (Edge) API from Nasuni — 4 operation(s) for edge appliances (edge).

Nasuni Edge Appliances (Edge) API is one of 30 APIs that Nasuni publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Edge Appliances (Edge). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.

This API exposes 6 operations across 4 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 3 base URLs: https://am1.portal.api.nasuni.com, https://eu1.portal.api.nasuni.com, https://ap1.portal.api.nasuni.com.

6 operations 4 paths 12 schemas 4 GET2 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://hostname/api/v1.2
Authentication
API Key, API Key, API Key, HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 5

Nasuni Edge Appliances (Edge) API declares 5 security schemes for authenticating requests. An API key is passed in the header as x-service-key (ServiceKeyHeader). An API key is passed in the header as x-service-secret (ServiceSecretHeader). An API key is passed in the header as x-user-key (UserKeyHeader). It accepts HTTP bearer tokens (JWT) (HTTPBearer). It supports OAuth 2.0 (OAuth2ClientCredentials) using the clientCredentials flow. By default, every request must be authenticated.

  • ServiceKeyHeader — Service key for programmatic API access. Must be used together with x-service-secret.
  • ServiceSecretHeader — Service secret for programmatic API access. Must be used together with x-service-key.
  • UserKeyHeader — User key for user-specific API access.
  • HTTPBearer — Bearer token obtained from /auth/token endpoint.
  • OAuth2ClientCredentials — Standard OAuth2 Client Credentials flow (RFC 6749 §4.4). Send clientid (service key) and clientsecret (service secret) as form-encoded body parameters to the t…

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 2 PATCH. Each is listed below with its method, path, parameters, and response codes.

Edge Appliances (Edge) 6
GET
/edges
Get Edges
get_edges_edges_get 2 params → 200401403409422500
GET
/edges/{edge_id}
Get Edge
get_edges_edge_edges__edge_id__get 1 param → 200401403404409422500
GET
/edges/{edge_id}/services/fiq
Get Edge FIQ Service
get_edges_edge_fiq_edges__edge_id__services_fiq_get 1 param → 200401403404409422500
PATCH
/edges/{edge_id}/services/fiq
Update Edge FIQ Service
update_edges_edge_fiq_edges__edge_id__services_fiq_patch 1 param body → 200401403404409422500
GET
/edges/{edge_id}/services/s3_edge
Get S3 Edge Status
get_edge_s3_edge_status_edges__edge_id__services_s3_edge_get 1 param → 200401403404409422500
PATCH
/edges/{edge_id}/services/s3_edge
Enable/Disable S3 Edge Status
update_edge_s3_edge_status_edges__edge_id__services_s3_edge_patch 1 param body → 200401403404409422500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are EdgeDto (15 properties), EdgeMachine (9 properties), SimpleEdgeDto (8 properties), EdgeBuild (3 properties). Each schema is shown below with its type and property counts.

ValidationErrorResponse
object
2 properties 2 required
EdgeDto
object
15 properties 8 required
UpdateEdgeFiqServiceDto
object
2 properties
EdgesDto
object
1 property
EdgeServicesDto
object
2 properties
EdgeS3EdgeConfigDto
object
1 property 1 required
ErrorResponse
object
2 properties 2 required
SimpleEdgeDto
object
8 properties 4 required
EdgeVolumes
object
2 properties 2 required
EdgeMachine
object
9 properties 6 required
EdgeBuild
object
3 properties 1 required
EdgeFiqServiceDto
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nasuni-edge-appliances-edge-api-openapi.yml Raw ↑

Other APIs Nasuni publishes across the network.

Nasuni Data API
Nasuni Portal MCP Server
Nasuni Account API
Nasuni Account Management API
Nasuni Activity Logs API
Nasuni AI Activate API
Nasuni Auth API
Nasuni Cloud Credentials API
Nasuni Configuration API
Nasuni Data API
Nasuni File IQ Appliances (File IQ) API
Nasuni Filers API
Where this information came from

This is an independent, third-party profile of Nasuni Edge Appliances (Edge) 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.