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

The Filers API from Nasuni — 30 operation(s) for filers.

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

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

This API exposes 41 operations across 30 paths, and defines 53 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://hostname/api/v1, https://hostname/api/v1.1, https://hostname/api/v1.2.

41 operations 30 paths 53 schemas 4 DELETE30 GET2 PATCH3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://hostname/api/v1.2
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Nasuni Filers API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (AuthToken). By default, every request must be authenticated.

  • AuthToken — This header is required to make authenticated requests. The value format is: Token [yourauthtoken]

Paths & Operations 41

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

Filers 41
GET
/filers/
List all Filers
2 params → 200401429
GET
/filers/{filer_serial}/
Get a Filer
1 param → 200401404429
PATCH
/filers/{filer_serial}/
Update a Filer
1 param body → 202400401404405429
GET
/filers/cifsclients/
Retrieve a list of all Filers, each with a list of CIFS clients connected to it.
2 params → 200401404429
GET
/filers/{filer_serial}/cifsclients/
Retrieve a Filer with a list of CIFS clients connected to it.
1 param → 200401404429
GET
/filers/cifslocks/
Retrieve a list of all Filers, each with a list of CIFS file locks that clients have on its shares.
2 params → 200401404429
GET
/filers/{filer_serial}/cifslocks/
Retrieve a Filer with a list of CIFS file locks that clients have on its shares.
1 param → 200401404429
GET
/filers/ftpclients/
Retrieve a list of all Filers, each with a list of FTP clients connected to it.
2 params → 200401404429
GET
/filers/{filer_serial}/ftpclients/
Retrieve a Filer with a list of FTP clients connected to it.
1 param → 200401404429
GET
/filers/amqp-audit-destinations/
List AMQP Destinations
2 params → 200401429
GET
/filers/{filer_serial}/amqp-audit-destinations/
List AMQP Destinations for a Filer
3 params → 200401404429
POST
/filers/{filer_serial}/amqp-audit-destinations/
Create an AMQP Destination
1 param body → 202400401404409429
GET
/filers/{filer_serial}/amqp-audit-destinations/{amqp_destination_name}
Get a single AMQP destination
2 params → 200401404429
DELETE
/filers/{filer_serial}/amqp-audit-destinations/{amqp_destination_name}
Delete an AMQP destination
2 params → 202400401404409429
PATCH
/filers/{filer_serial}/amqp-audit-destinations/{amqp_destination_name}
Update an AMQP destination
2 params body → 202400401404409429
GET
/filers/{filer_serial}/cifsclients/{cifs_client_id}
Get CIFS client
2 params → 200401404429
GET
/filers/cifsclients/locks/
List CIFS file locks
2 params → 200401404429
GET
/filers/{filer_serial}/cifsclients/locks/
List CIFS file locks for a Filer
3 params → 200401404429
GET
/filers/{filer_serial}/cifsclients/{cifs_client_id}/locks/
List CIFS file locks for a client
4 params → 200401404429
GET
/filers/{filer_serial}/ftpclients/{ftp_client_id}
Get FTP client
2 params → 200401404429
GET
/filers/encryption-keys/
List encryption keys
2 params → 200401403429
GET
/filers/{filer_serial}/encryption-keys/
List encryption keys for a Filer
3 params → 200401403404429
POST
/filers/{filer_serial}/encryption-keys/
Upload encryption keys for a Filer
1 param body → 202400401404429
GET
/filers/{filer_serial}/encryption-keys/{encryption_key_id}/
Get a Filer encryption key
2 params → 200401403404429
GET
/filers/health/
List health status for all Filers
2 params → 200401404429
GET
/filers/{filer_serial}/health/
List health status for a Filer
3 params → 200401404429
GET
/filers/blocked-clients/
List blocked clients across all Filers
2 params → 200401404429
GET
/filers/{filer_serial}/blocked-clients/
List blocked clients on a Filer
1 param → 200401404409429
POST
/filers/{filer_serial}/blocked-clients/
Block a client IP address on a Filer
1 param body → 202401404409429
GET
/filers/{filer_serial}/blocked-clients/{blocked_ip}/
Get specific blocked client on specific Filer
2 params → 200401404429
DELETE
/filers/{filer_serial}/blocked-clients/{blocked_ip}/
Unblock a client IP address on a Filer
2 params → 202403404429
GET
/filers/blocked-sources/ip-addresses/
List blocked IP addresses across all Filers
2 params → 200401404429
GET
/filers/blocked-sources/usernames/
List blocked usernames across all Filers
2 params → 200401404429
GET
/filers/{filer_serial}/blocked-sources/ip-addresses/
List blocked IP addresses on a Filer
1 param → 200401404409429
GET
/filers/{filer_serial}/blocked-sources/usernames/
List blocked usernames on a Filer
1 param → 200401404409429
GET
/filers/{filer_serial}/blocked-sources/ip-addresses/{blocked_ip}/
Get specific blocked IP address on specific Filer
2 params → 200401404429
PUT
/filers/{filer_serial}/blocked-sources/ip-addresses/{blocked_ip}/
Block an IP address on a Filer
2 params → 202401429
DELETE
/filers/{filer_serial}/blocked-sources/ip-addresses/{blocked_ip}/
Unblock an IP address on a Filer
2 params → 202403404429
GET
/filers/{filer_serial}/blocked-sources/usernames/{blocked_username}/
Get specific blocked username on specific Filer
2 params → 200401404429
PUT
/filers/{filer_serial}/blocked-sources/usernames/{blocked_username}/
Block a username on a Filer
2 params → 202401429
DELETE
/filers/{filer_serial}/blocked-sources/usernames/{blocked_username}/
Unblock a username on a Filer
2 params → 202403404429

Schemas 53

The contract defines 53 schemas that model the data the API accepts and returns. The most detailed are FilerHealthStatus (14 properties), AMQPAuditDestination_2 (12 properties), AMQPAuditDestination (12 properties), Message (11 properties). Each schema is shown below with its type and property counts.

FilerFTPClients
object
A description of a Filer's connected FTP clients.
4 properties
Paging
object
The paging object provides a container for a listing of objects, defining the start, end, and total size of the listing. Any endpoint that returns a list of it…
6 properties
FilerConfigurationQuotaReportSchedule
object
1 property
Error
object
2 properties
FilerConfigurationAutoupdate
object
8 properties
FilerConfigurationFTP
object
5 properties
FilerConfigurationCIFS
object
10 properties
FilerCIFSClients
object
A description of a Filer's connected CIFS clients.
4 properties
FilerServicesSupport
object
Enable or disable Remote Support, set the timeout before it is automatically disabled, and report if there is an active connection from Nasuni Support.
4 properties
FilerServicesMobile
object
4 properties
FilerCIFSLocks
object
A description of the CIFS File Locks that CIFS clients have on this Filer's shares.
4 properties
FilerPlatform
object
Information about a Filer's platform, including hardware type and information about CPU, Memory, and cache.
4 properties
Link
object
2 properties
Filer
object
Complete Filer object with all associated settings and statuses.
8 properties
FilerConfigurationAutoupdate_2
object
8 properties
HealthItem
string
FilerConfigurationQuotaReportSchedule_2
object
1 property
FilerConfigurationFTP_2
object
5 properties
ErrorResponse
object
1 property
AMQPAuditDestination
object
AMQP Destination for auditing logs object
12 properties 9 required
Message
object
The message object is used to track an action that we want the Filer to perform.
11 properties
FilerCIFSLock
object
A description of a CIFS file lock held by a connected CIFS client.
9 properties
FilerConfigurationCIFS_2
object
10 properties
MessageResponse
object
1 property
FilerServicesSupport_2
object
Enable or disable Remote Support, set the timeout before it is automatically disabled, and report if there is an active connection from Nasuni Support.
4 properties
FilerCIFSClient
object
A description of a connected CIFS client.
7 properties
FilerPlatform_2
object
Information about a Filer's platform, including hardware type and information about CPU, Memory, and cache.
4 properties
Link_2
object
2 properties
Filer_2
object
Complete Filer object with all associated settings and statuses.
8 properties
EncryptionKey
object
OpenPGP key
11 properties
Error_2
object
2 properties
FilerHealthStatus
object
Status of a given filer. Fields listed as "Warn" have one or more checks failing moderately. Fields listed as "Fail" have one or more checks failing severely.
14 properties
FilerFTPClient
object
A description of a connected (S)FTP client.
5 properties
FilerConfigurationAutoupdate_3
object
8 properties
Paging_2
object
The paging object provides a container for a listing of objects, defining the start, end, and total size of the listing. Any endpoint that returns a list of it…
6 properties
FilerConfigurationQuotaReportSchedule_3
object
1 property
FilerConfigurationFTP_3
object
5 properties
ErrorResponse_2
object
1 property
AMQPAuditDestination_2
object
AMQP Destination for auditing logs object
12 properties 9 required
BlockedSourceIpAddress
object
A blocked source IP address object
5 properties 4 required
Message_2
object
The message object is used to track an action that we want the Filer to perform.
11 properties
FilerCIFSLock_2
object
A description of a CIFS file lock held by a connected CIFS client.
8 properties
FilerConfigurationCIFS_3
object
10 properties
BlockedSourceUsername
object
A blocked source username object
5 properties 4 required
FilerServicesSupport_3
object
Enable or disable Remote Support, set the timeout before it is automatically disabled, and report if there is an active connection from Nasuni Support.
4 properties
FilerCIFSClient_2
object
A description of a connected CIFS client.
6 properties
FilerPlatform_3
object
Information about a Filer's platform, including hardware type and information about CPU, Memory, and cache.
4 properties
BlockedClient
object
A blocked client object
5 properties 4 required
Link_3
object
2 properties
Filer_3
object
Complete Filer object with all associated settings and statuses.
8 properties
EncryptionKey_2
object
OpenPGP key
11 properties
Error_3
object
2 properties
FilerFTPClient_2
object
A description of a connected (S)FTP client.
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nasuni-filers-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 Edge Appliances (Edge) API
Nasuni File IQ Appliances (File IQ) API
Where this information came from

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