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
NeuVector

NeuVector File API

Operations about File

Documentation Provider Profile APIs.io OpenAPI GitHub

NeuVector File API is one of 31 APIs that NeuVector publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include File. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and an API reference.

This API exposes 18 operations across 15 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 5.6.0.

Requests are made against a single base URL, https://localhost:10443/.

18 operations 15 paths 12 schemas 3 GET15 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.6.0
Base URL
https://localhost:10443
Authentication
API Key, API Key
Contact
support@neuvector.com
License
Apache 2.0
Resource Areas
1

Authentication & Security 2

NeuVector File API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Auth-Apikey (ApiKeyAuth). An API key is passed in the header as X-Auth-Token (TokenAuth).

Paths & Operations 18

Across 15 paths, the API surfaces 18 operations — 3 GET, 15 POST. Each is listed below with its method, path, parameters, and response codes.

File 18

Operations about File

POST
/v1/file/compliance/profile
Export compliance profile as a yaml format. The exported yaml file can be imported by CRD or REST API to update the compliance profile.
1 param body → 200
POST
/v1/file/admission
Export admission control configuration as a yaml format. The exported yaml file can be imported by CRD (non-fed scope only) or REST API to update the admission control settings.
1 param body → 200
POST
/v1/file/admission/config
import admission config
2 params body → 200
POST
/v1/file/response/rule
Export non-group-dependent (federated) response rules as a yaml format. The exported yaml file can be imported by CRD (non-fed scope only) or REST API to update the response rules.
1 param body → 200
POST
/v1/file/response/rule/config
import non-group-dependent response rules
2 params body → 200
GET
/v1/file/config
Download a configure file
→ 200
POST
/v1/file/config
Upload configure file
2 params body → 200
POST
/v1/file/fed_config
Export federated webhooks configuration as a yaml format
1 param body → 200
POST
/v1/file/dlp
Export (federated) DLP configuration as a yaml format. The exported yaml file can be imported by CRD (non-fed scope only) or REST API to update the DLP configurations.
1 param body → 200
POST
/v1/file/dlp/config
import DLP config
2 params body → 200
POST
/v1/file/vulnerability/profile
Export vulnerability profile as a yaml format. The exported yaml file can be imported by CRD or REST API to update the compliance profile.
1 param body → 200
POST
/v1/file/waf
Export (federated) WAF configuration as a yaml format. The exported yaml file can be imported by CRD (non-fed scope only) or REST API to update the WAF configurations.
1 param body → 200
POST
/v1/file/waf/config
import waf config
2 params body → 200
GET
/v1/file/group
(Obsolete, please use POST method.) Export the yaml format configuration file ( used for CRD or group policy ).
body → 200
POST
/v1/file/group
Export (federated) group configuration as a yaml format. The exported yaml file can be imported by CRD (non-fed scope only) or REST API to update the group policy.
1 param body → 200
GET
/v1/file/group/config
Get import status
→ 200
POST
/v1/file/group/config
import group policy
2 params body → 200
POST
/v1/csp/file/support
Export support config tarball in gz format
→ 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are RESTImportTask (8 properties), RESTGroupExport (5 properties), RESTRemoteExportOptions (3 properties), RESTAdmCtrlRulesExport (3 properties). Each schema is shown below with its type and property counts.

RESTFedConfigExport
object
1 property
RESTAdmCtrlRulesExport
object
3 properties
RESTImportTask
object
8 properties 3 required
RESTImportTaskData
object
1 property 1 required
RESTVulnProfilesExport
object
2 properties
RESTResponseRulesExport
object
2 properties
RESTRemoteExportOptions
object
3 properties 2 required
RESTRemoteExportData
object
1 property
RESTWafSensorExport
object
2 properties 1 required
RESTCompProfilesExport
object
2 properties
RESTGroupExport
object
5 properties 1 required
RESTDlpSensorExport
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

neuvector-file-api-openapi.yml Raw ↑

Other APIs NeuVector publishes across the network.

NeuVector Admission API
AE Profile APIs.io
NeuVector Apikey API
AE Profile APIs.io
NeuVector Authentication API
AE Profile APIs.io
NeuVector Compliance API
AE Profile APIs.io
NeuVector compliance profile. The payload body is the content of the compliance profile yaml file. API
AE Profile APIs.io
NeuVector compliance profile. The payload body is the content of the vulnerability profile yaml file. API
AE Profile APIs.io
NeuVector Container API
AE Profile APIs.io
NeuVector Controller API
AE Profile APIs.io
NeuVector DLP API
AE Profile APIs.io
NeuVector Enforcer API
AE Profile APIs.io
NeuVector EULA API
AE Profile APIs.io
NeuVector Federation API
AE Profile APIs.io
#File
← Back to N APIs
API Details
ID
neuvector:neuvector-file-api
Base URL
https://localhost:10443
Docs
https://open-docs.neuvector.com/
Provider
NeuVector
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=neuvector-file-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/neuvector-file-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 NeuVector File 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.