Apache NiFi website screenshot

Apache NiFi

Apache NiFi is a dataflow management system designed to automate the flow of data between systems. It provides a web-based user interface for designing, controlling, and monitoring data flows with real-time operational control, data provenance tracking, and support for hundreds of processors. NiFi Version 2 is the current major version with enhanced security and performance.

Apache NiFi publishes 4 APIs on the APIs.io network, including Access API, Connections API, Controller Services API, and 1 more. Tagged areas include Data Integration, Dataflows, ETL, IoT, and Streaming.

Apache NiFi’s developer surface includes authentication, developer portal, engineering blog, and 18 more developer resources.

40.3/100 developing ▬ flat Agent 20/100 agent aware open core · Apache-2.0 Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessFreemiumSelf serve⚡ Free to try
1 APIs 10 Features 6 Use Cases
Data IntegrationDataflowsETLIoTStreamingData Pipeline

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 80 points between them, because the conditional facet above carries the other 20. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 80% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/apache-nifi: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Apache NiFi Registry

NiFi Registry provides a central location for storage and management of shared NiFi flow resources, enabling versioned flows across NiFi environments. It provides its own REST A...

Apache MiNiFi

MiNiFi is a lightweight agent for edge data collection that is a subproject of NiFi. MiNiFi C++ (nifi-minifi-cpp) provides a small-footprint agent for IoT edge data collection w...

Apache NiFi Access API

Authentication and access token management

Apache NiFi Connections API

Manage connections between processors

Apache NiFi Controller Services API

Manage shared controller services

Apache NiFi Flow API

Read overall flow status and process group hierarchy

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Apache NiFi REST API

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Apache Nifi Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Features 10

Notable capabilities this provider offers.

Visual Dataflow Designer

Browser-based drag-and-drop interface for designing, controlling, and monitoring data flows without coding.

Data Provenance Tracking

Complete lineage tracking of every piece of data that flows through the system from ingestion to destination.

Hundreds of Built-in Processors

Extensive library of processors for data ingestion, transformation, routing, and delivery to diverse systems and cloud platforms.

Guaranteed Delivery

Loss-tolerant and guaranteed delivery options with configurable prioritization and backpressure control.

REST API

Comprehensive JWT-authenticated REST API for programmatic management of all NiFi resources and operations.

Flow Versioning

Version control for data flows via NiFi Registry, enabling flow promotion across development, test, and production environments.

Multi-Tenant Security

Fine-grained multi-tenant authorization with HTTPS, TLS, and SSH support for secure deployments.

Clustering

Zero-master cluster architecture for high-availability and load-balanced dataflow execution.

Parameter Contexts

Externalize configuration using parameter contexts that can be applied across multiple processors and process groups.

MiNiFi Edge Agents

Lightweight MiNiFi agents for edge data collection at IoT endpoints, managed centrally from NiFi.

Scroll for all 10

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Apache Nifi Authentication

http · 1 scheme

SECURITY

Apache Nifi Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Apache Nifi Vulnerability Disclosure

security.txt · contact published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Apache Nifi Agentic Access

11 operations · 7 acting · 3 human-in-the-loop

11 operations · 7 acting

AGENTIC

Use Cases 6

What developers build with this provider.

Data Ingestion Pipelines

Build pipelines ingesting data from files, databases, message queues, cloud storage, and APIs into data lakes and warehouses.

Cybersecurity Data Collection

Collect and route security telemetry, logs, and threat intelligence feeds for SIEM and analytics platforms.

IoT Edge Data Collection

Deploy MiNiFi agents at IoT edge locations to collect, filter, and forward sensor data to central NiFi clusters.

Real-Time Event Streaming

Build event streaming pipelines consuming from Kafka, Kinesis, and other message brokers for real-time data processing.

Generative AI Data Pipelines

Build data preparation and vector database ingestion pipelines for generative AI and RAG applications.

Cloud Data Integration

Move and transform data between AWS, Azure, and GCP services with built-in cloud processor libraries.

Integrations 8

Pre-built integrations with other platforms and tools.

Apache Kafka

Native ConsumeKafka and PublishKafka processors for streaming data between NiFi and Kafka topics.

Amazon S3

PutS3Object and FetchS3Object processors for reading and writing data to AWS S3 buckets.

Azure Blob Storage

PutAzureBlobStorage and FetchAzureBlobStorage processors for Azure cloud storage integration.

Google Cloud Storage

Native GCS processors for reading and writing Google Cloud Storage objects.

MongoDB

PutMongo and GetMongo processors for reading and writing documents to MongoDB collections.

Elasticsearch

PutElasticsearchRecord and FetchElasticsearch processors for indexing and querying Elasticsearch.

Salesforce

Native Salesforce processors for querying and publishing data to Salesforce CRM.

Apache MQTT

ConsumeMQTT and PublishMQTT processors for IoT messaging protocol support.

Scroll for all 8

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 6

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: apache-nifi
name: Apache NiFi
description: Apache NiFi is a dataflow management system designed to automate the flow of data between systems. It provides
  a web-based user interface for designing, controlling, and monitoring data flows with real-time operational control, data
  provenance tracking, and support for hundreds of processors. NiFi Version 2 is the current major version with enhanced security
  and performance.
type: Index
deliveryModel:
  model: open-core
  license: Apache-2.0
  open_source: true
  commercial: true
  callable_host: false
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/apache-nifi.png
tags:
- Data Integration
- Dataflows
- ETL
- IoT
- Streaming
- Data Pipeline
tags_raw:
- Data Integration
- Dataflow
- ETL
- IoT
- Streaming
- Data Pipeline
created: '2026-03-16'
modified: '2026-04-19'
url: https://raw.githubusercontent.com/api-evangelist/apache-nifi/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis:
- aid: apache-nifi:apache-nifi-registry
  name: Apache NiFi Registry
  description: NiFi Registry provides a central location for storage and management of shared NiFi flow resources, enabling
    versioned flows across NiFi environments. It provides its own REST API for managing buckets, flows, versions, and users.
  humanURL: https://nifi.apache.org/documentation/
  tags:
  - Flow Versioning
  - Registry
  - REST
  properties:
  - type: Documentation
    url: https://nifi.apache.org/documentation/
  - type: GitHubRepository
    url: https://github.com/apache/nifi
- aid: apache-nifi:apache-minifi
  name: Apache MiNiFi
  description: MiNiFi is a lightweight agent for edge data collection that is a subproject of NiFi. MiNiFi C++ (nifi-minifi-cpp)
    provides a small-footprint agent for IoT edge data collection with local processing and a remote NiFi parent instance
    for management.
  humanURL: https://nifi.apache.org/minifi/
  tags:
  - Edge Computing
  - IoT
  - Lightweight Agent
  properties:
  - type: Documentation
    url: https://nifi.apache.org/minifi/
  - type: GitHubRepository
    url: https://github.com/apache/nifi-minifi-cpp
- aid: apache-nifi:apache-nifi-access-api
  name: Apache NiFi Access API
  description: Authentication and access token management
  humanURL: https://nifi.apache.org/components/
  tags:
  - Access
  properties:
  - type: OpenAPI
    url: openapi/apache-nifi-access-api-openapi.yml
  - type: Documentation
    url: https://nifi.apache.org/components/
  - type: GettingStarted
    url: https://nifi.apache.org/documentation/guides/
  - type: GitHubRepository
    url: https://github.com/apache/nifi
- aid: apache-nifi:apache-nifi-connections-api
  name: Apache NiFi Connections API
  description: Manage connections between processors
  humanURL: https://nifi.apache.org/components/
  tags:
  - Connections
  properties:
  - type: OpenAPI
    url: openapi/apache-nifi-connections-api-openapi.yml
  - type: Documentation
    url: https://nifi.apache.org/components/
  - type: GettingStarted
    url: https://nifi.apache.org/documentation/guides/
  - type: GitHubRepository
    url: https://github.com/apache/nifi
- aid: apache-nifi:apache-nifi-controller-services-api
  name: Apache NiFi Controller Services API
  description: Manage shared controller services
  humanURL: https://nifi.apache.org/components/
  tags:
  - Controller Services
  properties:
  - type: OpenAPI
    url: openapi/apache-nifi-controller-services-api-openapi.yml
  - type: Documentation
    url: https://nifi.apache.org/components/
  - type: GettingStarted
    url: https://nifi.apache.org/documentation/guides/
  - type: GitHubRepository
    url: https://github.com/apache/nifi
- aid: apache-nifi:apache-nifi-flow-api
  name: Apache NiFi Flow API
  description: Read overall flow status and process group hierarchy
  humanURL: https://nifi.apache.org/components/
  tags:
  - Flow
  properties:
  - type: OpenAPI
    url: openapi/apache-nifi-flow-api-openapi.yml
  - type: Documentation
    url: https://nifi.apache.org/components/
  - type: GettingStarted
    url: https://nifi.apache.org/documentation/guides/
  - type: GitHubRepository
    url: https://github.com/apache/nifi
common:
- type: Website
  url: https://www.apache.org/
- type: Releases
  url: https://github.com/apache/nifi/releases
- type: SecurityPolicy
  url: https://github.com/apache/nifi/blob/main/SECURITY.md
- type: CodeOfConduct
  url: https://github.com/apache/.github/blob/main/.github/CODE_OF_CONDUCT.md
- type: License
  name: Apache-2.0
  url: https://github.com/apache/nifi/blob/main/LICENSE
- type: AgenticAccess
  url: agentic-access/apache-nifi-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/apache-nifi-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/apache-nifi-domain-security.yml
- type: Authentication
  url: authentication/apache-nifi-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/apache-nifi
- type: Portal
  url: https://nifi.apache.org/
- type: GitHubOrganization
  url: https://github.com/apache
- type: GitHubRepository
  url: https://github.com/apache/nifi
- type: GitHubRepository
  url: https://github.com/apache/nifi-minifi-cpp
- type: GitHubRepository
  url: https://github.com/apache/nifi-api
- type: GitHubRepository
  url: https://github.com/apache/nifi-site
- type: Wiki
  url: https://cwiki.apache.org/confluence/display/NIFI
- type: IssueTracker
  url: https://issues.apache.org/jira/browse/NIFI
- type: Slack
  url: https://join.slack.com/t/apachenifi/shared_invite/zt-11njbtkdx-ZRU8FKYSWoEHRJetidy0zA
- type: Blog
  url: https://nifi.apache.org/blog/
- type: TermsOfService
  url: https://www.apache.org/licenses/LICENSE-2.0
- type: Features
  data:
  - name: Visual Dataflow Designer
    description: Browser-based drag-and-drop interface for designing, controlling, and monitoring data flows without coding.
  - name: Data Provenance Tracking
    description: Complete lineage tracking of every piece of data that flows through the system from ingestion to destination.
  - name: Hundreds of Built-in Processors
    description: Extensive library of processors for data ingestion, transformation, routing, and delivery to diverse systems
      and cloud platforms.
  - name: Guaranteed Delivery
    description: Loss-tolerant and guaranteed delivery options with configurable prioritization and backpressure control.
  - name: REST API
    description: Comprehensive JWT-authenticated REST API for programmatic management of all NiFi resources and operations.
  - name: Flow Versioning
    description: Version control for data flows via NiFi Registry, enabling flow promotion across development, test, and production
      environments.
  - name: Multi-Tenant Security
    description: Fine-grained multi-tenant authorization with HTTPS, TLS, and SSH support for secure deployments.
  - name: Clustering
    description: Zero-master cluster architecture for high-availability and load-balanced dataflow execution.
  - name: Parameter Contexts
    description: Externalize configuration using parameter contexts that can be applied across multiple processors and process
      groups.
  - name: MiNiFi Edge Agents
    description: Lightweight MiNiFi agents for edge data collection at IoT endpoints, managed centrally from NiFi.
- type: UseCases
  data:
  - name: Data Ingestion Pipelines
    description: Build pipelines ingesting data from files, databases, message queues, cloud storage, and APIs into data lakes
      and warehouses.
  - name: Cybersecurity Data Collection
    description: Collect and route security telemetry, logs, and threat intelligence feeds for SIEM and analytics platforms.
  - name: IoT Edge Data Collection
    description: Deploy MiNiFi agents at IoT edge locations to collect, filter, and forward sensor data to central NiFi clusters.
  - name: Real-Time Event Streaming
    description: Build event streaming pipelines consuming from Kafka, Kinesis, and other message brokers for real-time data
      processing.
  - name: Generative AI Data Pipelines
    description: Build data preparation and vector database ingestion pipelines for generative AI and RAG applications.
  - name: Cloud Data Integration
    description: Move and transform data between AWS, Azure, and GCP services with built-in cloud processor libraries.
- type: Integrations
  data:
  - name: Apache Kafka
    description: Native ConsumeKafka and PublishKafka processors for streaming data between NiFi and Kafka topics.
  - name: Amazon S3
    description: PutS3Object and FetchS3Object processors for reading and writing data to AWS S3 buckets.
  - name: Azure Blob Storage
    description: PutAzureBlobStorage and FetchAzureBlobStorage processors for Azure cloud storage integration.
  - name: Google Cloud Storage
    description: Native GCS processors for reading and writing Google Cloud Storage objects.
  - name: MongoDB
    description: PutMongo and GetMongo processors for reading and writing documents to MongoDB collections.
  - name: Elasticsearch
    description: PutElasticsearchRecord and FetchElasticsearch processors for indexing and querying Elasticsearch.
  - name: Salesforce
    description: Native Salesforce processors for querying and publishing data to Salesforce CRM.
  - name: Apache MQTT
    description: ConsumeMQTT and PublishMQTT processors for IoT messaging protocol support.
maintainers:
- FN: Kin Lane
  email: info@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/apache-nifi"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/apache-nifi/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/apache-nifi/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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