Apache Flume

Apache Flume is a distributed, reliable, and available service for efficiently collecting, aggregating, and moving large amounts of log and event data. It provides a simple and flexible architecture based on streaming data flows with pluggable sources, channels, and sinks, plus a REST monitoring API for agent metrics.

Apache Flume publishes 2 API contracts indexed on the APIs.io network, including Monitoring API, and 1 more. Tagged areas include Apache, Data Collection, ETL, Log Aggregation, and Open Source.

The Apache Flume catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

Apache Flume’s developer surface includes documentation, getting-started guide, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.6/100 thin ▬ flat Agent 24/100 agent aware self hosted · Apache-2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemium

1 published contract 9 Features 5 Use Cases

Apache Data Collection ETL Log Aggregation Open Source Streaming

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 32.6/100 · thin

Contract Quality 9.4 / 19

Developer Ergonomics 4.3 / 15

Access Clarity 1.2 / 15

Operational Transparency 2.1 / 10

Contract Governance 2.5 / 9

Discoverability 4.3 / 8

Regulatory Posture 2.5 / 15

Open Source Surface 4.0 / 10

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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 does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 75 points between them, because both conditional facets apply and carry 25 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/apache-flume/"><img src="https://apis.io/badge/apache-flume/card.svg" alt="Apache Flume on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 7.9 — up to +18.4 composite points
Developer Ergonomics scores 28.6 — up to +14.3 composite points
Contract Quality scores 50.1 — up to +12.5 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/apache-flume/apis.yml: open an issue on github.com/api-evangelist/apache-flume to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 2

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

Apache Flume Java API

Java API for building custom Flume sources, channels, sinks, and interceptors. Provides interfaces for developing pluggable data ingestion components.

Apache Flume Monitoring API

The Monitoring API from Apache Flume — 1 operation(s) for monitoring.

Open Collections 2

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

Apache Flume Monitoring API

OPEN COLLECTION

Apache Flume Monitoring API

OPEN COLLECTION

Apache Flume API pricing

Not yet checked against Apache Flume's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Apache Flume's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Apache Flume Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Apache Flume Rate Limits

5 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Apache Flume

SLA

FinOps 1

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

Apache Flume Finops

FINOPS

Features 9

Notable capabilities this provider offers.

Pluggable Sources

Extensible source architecture supporting Avro, Thrift, Exec, Taildir, Kafka, HTTP, Syslog, and custom sources.

Durable Channels

Multiple channel implementations including memory, file-backed, and Kafka-backed channels for different durability requirements.

Multi-Destination Sinks

Write events to HDFS, HBase, Solr, Elasticsearch, Kafka, and custom sink destinations.

Fan-In Consolidation

Aggregate events from multiple agent sources into a single destination for centralized log collection.

Fan-Out Distribution

Route events from a single source to multiple channel/sink combinations for parallel processing.

Interceptors

Event transformation interceptors for filtering, enrichment, and routing based on event content.

SSL/TLS Security

TLS encryption support across Avro, Thrift, Kafka, HTTP, and Syslog components.

Monitoring REST API

HTTP monitoring endpoint exposing source, channel, and sink metrics for agent health monitoring.

Multi-Hop Flows

Chain multiple Flume agents via Avro/Thrift RPC for tiered log aggregation architectures.

Scroll for all 9

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Apache Flume Monitoring Context

2 classes · 18 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Apache Flume — jsonschema rules

5 rules · 4 warnings 1 info

SPECTRAL

Apache Flume API Rules

9 rules · 4 errors 4 warnings 1 info

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

AgentMetrics

0 properties

JSON SCHEMA

ComponentMetrics

18 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Flume Monitoring Agent Metrics Structure

0 properties

JSON STRUCTURE

Flume Monitoring Component Metrics Structure

18 properties

JSON STRUCTURE

Examples 2

Example request and response payloads for these APIs.

Flume Monitoring Agent Metrics Example

0 fields

EXAMPLE

Flume Monitoring Component Metrics Example

18 fields

EXAMPLE

Security Posture 2

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

Apache Flume Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Apache Flume Vulnerability Disclosure

security.txt · contact published

SECURITY

Agentic Access 1

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

Apache Flume Agentic Access

1 operation

1 operations · 0 acting

AGENTIC

Use Cases 5

What developers build with this provider.

Centralized Log Aggregation

Collect application logs from hundreds of servers and aggregate them into HDFS, Kafka, or Elasticsearch.

Real-Time Log Tailing

Tail application log files in real time using Taildir source for immediate event processing.

Syslog Ingestion

Ingest RFC-3164 and RFC-5424 syslog events from network devices into centralized storage.

Kafka Event Ingestion

Bridge Kafka topics to HDFS or other storage for batch analytics on streaming event data.

Multi-Tier Architectures

Build tiered data collection with edge collectors forwarding to aggregation agents and final destinations.

Integrations 5

Pre-built integrations with other platforms and tools.

Apache Kafka

Kafka source and channel for consuming events, and Kafka sink for writing events to topics.

Apache HDFS

Primary sink for writing log data to Hadoop Distributed File System for batch analytics.

Apache HBase

HBase sink for writing events directly to HBase tables for random-access analytics.

Apache Solr

Solr sink for indexing log events for full-text search capabilities.

Elasticsearch

Elasticsearch sink for indexing and searching aggregated log data.

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

SpectralRules

SpectralRules

Vocabulary

Vocabulary

Build 3

SDKs, sample code, and the tooling you integrate with

CodeOfConduct

CodeOfConduct

GitHubOrganization

GitHubOrganization

GitHubRepository

GitHubRepository

Access & Security 2

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

IssueTracker

IssueTracker

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

License

License

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: apache-flume
name: Apache Flume
description: Apache Flume is a distributed, reliable, and available service for efficiently collecting, aggregating, and moving
  large amounts of log and event data. It provides a simple and flexible architecture based on streaming data flows with pluggable
  sources, channels, and sinks, plus a REST monitoring API for agent metrics.
type: Index
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: low
  try_now_blocked_by: loopback
  source:
  - plans
  - security
  generated: '2026-11-06'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/apache-flume.png
x-docs-platform: sphinx
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-19
tags:
- Apache
- Data Collection
- ETL
- Log Aggregation
- Open Source
- Streaming
tags_raw:
- Apache
- Data Collection
- ETL
- Log Aggregation
- Open Source
- Streaming
- Open-Source
created: '2026-03-16'
modified: '2026-05-19'
url: https://raw.githubusercontent.com/api-evangelist/apache-flume/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis:
- aid: apache-flume:apache-flume-java-api
  name: Apache Flume Java API
  description: Java API for building custom Flume sources, channels, sinks, and interceptors. Provides interfaces for developing
    pluggable data ingestion components.
  humanURL: https://flume.apache.org/FlumeDeveloperGuide.html
  tags:
  - Java
  - SDK
  - Extension
  properties:
  - type: Documentation
    url: https://flume.apache.org/FlumeDeveloperGuide.html
  - type: SDKs
    url: https://search.maven.org/artifact/org.apache.flume/flume-ng-core
    title: Java SDK (Maven Central)
- aid: apache-flume:apache-flume-monitoring-api
  name: Apache Flume Monitoring API
  description: The Monitoring API from Apache Flume — 1 operation(s) for monitoring.
  humanURL: https://flume.apache.org/FlumeUserGuide.html
  baseURL: http://localhost:41414
  tags:
  - Monitoring
  properties:
  - type: OpenAPI
    url: openapi/apache-flume-monitoring-api-openapi.yml
  - type: Documentation
    url: https://flume.apache.org/FlumeUserGuide.html
  - type: JSONSchema
    url: json-schema/flume-monitoring-agent-metrics-schema.json
  - type: JSONLD
    url: json-ld/apache-flume-monitoring-context.jsonld
common:
- type: Plans
  url: plans/apache-flume-plans-pricing.yml
- type: RateLimits
  url: rate-limits/apache-flume-rate-limits.yml
- type: FinOps
  url: finops/apache-flume-finops.yml
- type: Website
  url: https://www.apache.org/
- type: IssueTracker
  url: https://github.com/apache/flume/issues
- type: CodeOfConduct
  url: https://github.com/apache/.github/blob/main/.github/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/apache/logging-flume/blob/trunk/CONTRIBUTING.md
- type: License
  name: Apache-2.0
  url: https://github.com/apache/flume/blob/trunk/LICENSE
- type: AgenticAccess
  url: agentic-access/apache-flume-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/apache-flume-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/apache-flume-domain-security.yml
- type: Documentation
  url: https://flume.apache.org/documentation.html
- type: GettingStarted
  url: https://flume.apache.org/FlumeUserGuide.html
- type: GitHubOrganization
  url: https://github.com/apache
- type: GitHubRepository
  url: https://github.com/apache/flume
- type: SpectralRules
  url: rules/apache-flume-spectral-rules.yml
- type: Vocabulary
  url: vocabulary/apache-flume-vocabulary.yaml
- type: Features
  data:
  - name: Pluggable Sources
    description: Extensible source architecture supporting Avro, Thrift, Exec, Taildir, Kafka, HTTP, Syslog, and custom sources.
  - name: Durable Channels
    description: Multiple channel implementations including memory, file-backed, and Kafka-backed channels for different durability
      requirements.
  - name: Multi-Destination Sinks
    description: Write events to HDFS, HBase, Solr, Elasticsearch, Kafka, and custom sink destinations.
  - name: Fan-In Consolidation
    description: Aggregate events from multiple agent sources into a single destination for centralized log collection.
  - name: Fan-Out Distribution
    description: Route events from a single source to multiple channel/sink combinations for parallel processing.
  - name: Interceptors
    description: Event transformation interceptors for filtering, enrichment, and routing based on event content.
  - name: SSL/TLS Security
    description: TLS encryption support across Avro, Thrift, Kafka, HTTP, and Syslog components.
  - name: Monitoring REST API
    description: HTTP monitoring endpoint exposing source, channel, and sink metrics for agent health monitoring.
  - name: Multi-Hop Flows
    description: Chain multiple Flume agents via Avro/Thrift RPC for tiered log aggregation architectures.
- type: UseCases
  data:
  - name: Centralized Log Aggregation
    description: Collect application logs from hundreds of servers and aggregate them into HDFS, Kafka, or Elasticsearch.
  - name: Real-Time Log Tailing
    description: Tail application log files in real time using Taildir source for immediate event processing.
  - name: Syslog Ingestion
    description: Ingest RFC-3164 and RFC-5424 syslog events from network devices into centralized storage.
  - name: Kafka Event Ingestion
    description: Bridge Kafka topics to HDFS or other storage for batch analytics on streaming event data.
  - name: Multi-Tier Architectures
    description: Build tiered data collection with edge collectors forwarding to aggregation agents and final destinations.
- type: Integrations
  data:
  - name: Apache Kafka
    description: Kafka source and channel for consuming events, and Kafka sink for writing events to topics.
  - name: Apache HDFS
    description: Primary sink for writing log data to Hadoop Distributed File System for batch analytics.
  - name: Apache HBase
    description: HBase sink for writing events directly to HBase tables for random-access analytics.
  - name: Apache Solr
    description: Solr sink for indexing log events for full-text search capabilities.
  - name: Elasticsearch
    description: Elasticsearch sink for indexing and searching aggregated log data.
maintainers:
- FN: Kin Lane
  email: info@apievangelist.com

Apache Flume API — frequently asked questions

Does Apache Flume have an API?

Yes. APIs.io lists 2 APIs from Apache Flume, including Apache Flume Java API and Apache Flume Monitoring API.

Is there an OpenAPI specification for the Apache Flume API?

Yes. APIs.io indexes 1 OpenAPI specification for Apache Flume, each linked for download from this page.

How much does the Apache Flume API cost?

APIs.io lists 3 pricing plans for Apache Flume, with each plan's price, limits and inclusions under Pricing on this page.

Is the Apache Flume API ready for AI agents?

Apache Flume has a Kin Score of 32.6 out of 100 (thin) and an Agent Readiness score of 23.6 (agent-aware), scored by API Evangelist on 2026-11-06.

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-flume"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/apache-flume/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/apache-flume/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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