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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Nasuni

Nasuni IAM API

The IAM API from Nasuni — 13 operation(s) for iam.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 21 operations across 13 paths, and defines 21 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.

21 operations 13 paths 21 schemas 3 DELETE12 GET2 PATCH4 POST

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 IAM 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 21

Across 13 paths, the API surfaces 21 operations — 3 DELETE, 12 GET, 2 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

IAM 21
GET
/iam/users
Get Users
get_users_iam_users_get → 200401403422500
GET
/iam/users/{user_id}
Get User
get_user_iam_users__user_id__get 1 param → 200401403404422500
GET
/iam/users/{user_id}/roles
Get User Roles
get_user_roles_iam_users__user_id__roles_get 1 param → 200401403404422500
GET
/iam/roles
Get Roles
get_roles_iam_roles_get → 200401403422500
POST
/iam/roles
Create Role
create_role_iam_roles_post body → 200401403409422500
POST
/iam/roles/duplicate
Duplicate Role
duplicate_role_iam_roles_duplicate_post body → 200401403409422500
PATCH
/iam/roles/{role_id}
Update Role
update_role_iam_roles__role_id__patch 1 param body → 200401403404409422500
DELETE
/iam/roles/{role_id}
Delete Role
delete_role_iam_roles__role_id__delete 1 param → 200401403404422500
GET
/iam/roles/{role_id}
Get Role
get_role_iam_roles__role_id__get 1 param → 200401403404422500
GET
/iam/roles/{role_id}/permissions
Get Role Permissions
get_permissions_for_role_iam_roles__role_id__permissions_get 1 param → 200401403404422500
GET
/iam/permissions
Get Permissions
get_permissions_iam_permissions_get → 200401403422500
GET
/iam/me
Get My Roles and Permissions
get_my_roles_and_permissions_iam_me_get → 200
GET
/iam/service_keys
Get Service Keys
get_service_keys_iam_service_keys_get → 200401403422500
POST
/iam/service_keys
Create Service Key
create_service_key_iam_service_keys_post body → 200400401403409422500
GET
/iam/service_keys/{service_key_id}
Get Service Key
get_service_key_iam_service_keys__service_key_id__get 1 param → 200401403404422500
PATCH
/iam/service_keys/{service_key_id}
Update Service Key
update_service_key_iam_service_keys__service_key_id__patch 1 param body → 200400401403404409422500
DELETE
/iam/service_keys/{service_key_id}
Delete Service Key
delete_service_key_iam_service_keys__service_key_id__delete 1 param → 200401403404422500
GET
/iam/user_keys
Get User Keys
get_user_keys_iam_user_keys_get → 200401403422500
POST
/iam/user_keys
Create User Key
create_user_key_iam_user_keys_post → 200400401403422500
GET
/iam/user_keys/{user_key_id}
Get User Key
get_user_key_iam_user_keys__user_key_id__get 1 param → 200401403404422500
DELETE
/iam/user_keys/{user_key_id}
Delete User Key
delete_user_key_iam_user_keys__user_key_id__delete 1 param → 200401403404422500

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are RoleDto (8 properties), UserKeyDto (7 properties), CreateServiceKeyResponseDto (7 properties), BaseRoleDto (7 properties). Each schema is shown below with its type and property counts.

RolesDto
object
1 property 1 required
PermissionKey
string
Enum representing all possible permission keys for the Portal API, including NDS (Nasuni Data Service) permissions. This enum is used to define and manage acce…
ServiceKeysDto
object
1 property 1 required
PermissionDto
object
3 properties 3 required
BaseRoleDto
object
7 properties 4 required
DuplicateRoleDto
object
3 properties 2 required
PermissionsDto
object
1 property
CreateServiceKeyResponseDto
object
7 properties 7 required
UpdateRoleDto
object
3 properties
UserKeysDto
object
1 property 1 required
ErrorResponse
object
2 properties 2 required
CreateServiceKeyRequestBodyDto
object
2 properties 2 required
ValidationErrorResponse
object
2 properties 2 required
RoleDto
object
8 properties 5 required
UserKeyDto
object
7 properties 7 required
UsersDto
object
1 property 1 required
UserDto
object
5 properties 4 required
ServiceKeyDto
object
6 properties 6 required
UpdateServiceKeyRequestBodyDto
object
2 properties
CreateRoleDto
object
3 properties 1 required
RolesAndPermissionsDto
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nasuni-iam-api-openapi.yml Raw ↑

Other APIs Nasuni publishes across the network.

Nasuni Data API
AE Profile APIs.io
Nasuni Portal MCP Server
AE Profile APIs.io
Nasuni Account API
AE Profile APIs.io
Nasuni Account Management API
AE Profile APIs.io
Nasuni Activity Logs API
AE Profile APIs.io
Nasuni AI Activate API
AE Profile APIs.io
Nasuni Auth API
AE Profile APIs.io
Nasuni Cloud Credentials API
AE Profile APIs.io
Nasuni Configuration API
AE Profile APIs.io
Nasuni Data API
AE Profile APIs.io
Nasuni Edge Appliances (Edge) API
AE Profile APIs.io
Nasuni File IQ Appliances (File IQ) API
AE Profile APIs.io
#IAM
← Back to N APIs
API Details
ID
nasuni:nasuni-iam-api
Base URL
https://hostname/api/v1.2
Docs
https://docs.api.nasuni.com/api/nmc/v120/introduction/
Provider
Nasuni
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=nasuni-iam-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/nasuni-iam-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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