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
Metaplane

Metaplane API

The Metaplane REST API — 23 operations over connections, monitors, monitor evaluations, datapoint ingestion and tags. Bearer-token authenticated, versioned by path prefix (/v1 with /v2 for two monitor operations), served from https://dev.api.metaplane.dev.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include AIOps and Data Observability. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

This API exposes 23 operations across 22 paths, organized into 3 resource areas, and defines 37 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against a single base URL, https://dev.api.metaplane.dev.

23 operations 22 paths 37 schemas 9 GET14 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://dev.api.metaplane.dev
Authentication
API Key
Contact
Metaplane
Resource Areas
3

Authentication & Security 1

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

  • Authorization — Copy in your API key generated from metaplane

Paths & Operations 23

Across 22 paths, the API surfaces 23 operations — 9 GET, 14 POST. They span 3 resource areas: Monitors, Tags, Connections. Each is listed below with its method, path, parameters, and response codes.

Monitors 12
POST
/v2/monitors/bulk-fetch/tables/{connectionId}
Bulk get monitors on tables
bulkGetTableMonitors 3 params body → 200
POST
/v1/monitors
Create Monitor
createMonitor body → 200
GET
/v1/monitors/connection/{connectionId}
List for connection
getAllMonitorsForSource 3 params → 200
POST
/v1/monitors/evaluation-history/{monitorId}
Evaluation History
getEvaluationHistory 1 param body → 200
GET
/v1/monitors/{monitorId}
Get monitor
getMonitor 2 params → 200
POST
/v1/monitors/{monitorId}
Update monitor
updateMonitor 1 param body → 200
GET
/v1/monitors/path/{connectionId}/{absolutePath}
Get for database entity
getMonitors 5 params → 200
GET
/v1/monitors/status/{monitorId}
Status (deprecated)
getMonitorStatus 1 param → 200
GET
/v2/monitors/status/{monitorId}
Status
getMonitorStatus2 1 param → 200
POST
/v1/monitors/import-historic/{monitorId}
Import Historic Data
importHistoricDataForMonitor 1 param body → 200
POST
/v1/monitors/ingest-datapoint/{monitorId}
Ingest Datapoint
ingestDataPoint 1 param body → 200
POST
/v1/monitors/run
Run
runMonitors body → 200
Tags 7
POST
/v1/tags/batch/fetch-tags
Batch fetch tag definitions
fetchTagDefinitions body → 200
GET
/v1/tags/tagged-monitors/{tag}
Fetch monitors for a tag
fetchTaggedMonitors 3 params → 200
GET
/v1/tags/tagged-objects/{tag}
Fetch all objects for tag
fetchTaggedObjects 2 params → 200
POST
/v1/tags/remove-monitor-tags
Remove monitor tags
removeMonitorTags body → 200
POST
/v1/tags/remove-table-tags
Remove table tags
removeTableTags body → 200
POST
/v1/tags/batch/tag-monitors
Batch tag monitors
tagMonitors body → 200
POST
/v1/tags/batch/tag-tables
Batch tag tables
tagTables body → 200
Connections 4
GET
/v1/connections
List all
getAllConnections 1 param → 200
GET
/v1/connections/{connectionId}/sync/status
Sync status
getConnectionStatus 1 param → 200
POST
/v1/connections/{connectionId}/sync
Sync
syncConnection 1 param → 200
POST
/v1/connections/{connectionId}/update-private-key
Update private key
updatePrivateKey 1 param body → 200

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are PublicMonitor (16 properties), MonitorStatus (10 properties), MonitorEgg (8 properties), Connection (7 properties). Each schema is shown below with its type and property counts.

PublicAnomalyAlertRule
object
6 properties
PublicMonitor
object
16 properties
MonitorGrouping
object
List of all groups that have seen at least one datapoint for this monitor
1 property
LabelNameValue
object
2 properties
TimeDuration
object
3 properties
MonitorListResult
object
1 property
PublicIncrementalClause
object
2 properties
PublicManualThreshold
object
2 properties
PublicAlertRule
object
Optional alert rule configuration. Defaults to ANOMALY
2 properties
BulkFetchMonitorTablesRequest
object
1 property
PublicManualThresholdRule
object
1 property
MonitorConfig
object
7 properties
MonitorEgg
object
8 properties
PublicTagDefinition
object
3 properties
TagDefinitionRequest
object
1 property
PublicEntity
object
2 properties
TaggedObjectResponse
object
3 properties
Connection
object
7 properties
ConnectionSyncStatusResult
object
4 properties
AnnotatedPoint
object
Optional annotation that was applied to this specific datapoint
3 properties
EvaluationHistoryRequest
object
4 properties
MonitorStatus
object
10 properties
MonitorStatusResultV2
object
4 properties
SeriesStatus
object
6 properties
ImportHistoricDataRequest
object
2 properties
PublicImportResult
object
4 properties
PublicSeriesPointWithTimestamp
object
3 properties
PublicSeriesPoint
object
2 properties
RemoveMonitorTagsRequest
object
2 properties
RemoveTableTagsRequest
object
3 properties
RunMonitorsRequest
object
1 property
TagMonitorsResult
object
2 properties
TagMonitorsRequest
object
2 properties
TagTablesRequest
object
3 properties
TagTablesResult
object
2 properties
MonitorUpdate
object
5 properties
UpdatePrivateKeyRequest
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

metaplane-api-openapi.yml Raw ↑

Other APIs Metaplane publishes across the network.

Metaplane Connections API
AE Profile APIs.io
Metaplane Monitors API
AE Profile APIs.io
Metaplane Tags API
AE Profile APIs.io
#AIOps#Data Observability
← Back to M APIs
API Details
ID
metaplane:metaplane
Base URL
https://dev.api.metaplane.dev
Docs
https://docs.metaplane.dev/reference/getting-started
Provider
Metaplane
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=metaplane&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/metaplane"

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 Metaplane 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.