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 Account Management API

The Account Management API from Nasuni — 3 operation(s) for account management.

Nasuni Account Management API is one of 30 APIs that Nasuni publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Account Management. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.

This API exposes 4 operations across 3 paths, and defines 11 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.

4 operations 3 paths 11 schemas 3 GET1 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 Account Management 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 4

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

Account Management 4
GET
/account
Get Account Information
get_account_information_account_get → 200401403408422500
PATCH
/account
Update Account Information
update_account_information_account_patch body → 200401403404408409422500
GET
/account/license
Get Account License Information
get_account_license_account_license_get → 200401403408422500
GET
/account/ai_activate
Get AI Activate Account Info
get_account_ai_activate_info_account_ai_activate_get → 200401403408422500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are AccountLicenseDto (21 properties), AccountInformationDto (7 properties), CloudProviderEntryDto (4 properties), UpdateAccountInformationDto (4 properties). Each schema is shown below with its type and property counts.

ValidationErrorResponse
object
2 properties 2 required
CloudProviderEntryDto
object
A cloud provider available to the account.
4 properties 4 required
NocCloudStorageProtocol
string
The underlying storage API/protocol (maps to 'type' in NOC response).
AccountLicenseDto
object
21 properties 11 required
AccountInformationDto
object
Response model for account infromation for webbff/account
7 properties 7 required
ErrorResponse
object
2 properties 2 required
UpdateAccountInformationDto
object
Request model for account information change for WebApi route /account
4 properties 4 required
NocCloudVendor
string
Who provisions the cloud infrastructure.
NocCloudProvider
string
Cloud provider identity as used by NOC (shortname).
AiActivateAccountInfoDto
object
Account-level AI Activate subscription summary. MCP is currently the only AI Activate workload. A Search subscription will be reintroduced here once that workl…
1 property 1 required
AiActivateAccountSubscriptionDto
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nasuni-account-management-api-openapi.yml Raw ↑

Other APIs Nasuni publishes across the network.

Nasuni Data API
Nasuni Portal MCP Server
Nasuni Account API
Nasuni Activity Logs API
Nasuni AI Activate API
Nasuni Auth API
Nasuni Cloud Credentials API
Nasuni Configuration API
Nasuni Data API
Nasuni Edge Appliances (Edge) 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 Account Management 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.