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

Metaplane Tags API

The Tags API from Metaplane — 7 operations for bulk-labelling tables and monitors, removing tags, fetching tag definitions and reading tagged objects and monitors back. Tags are the routing dimension for incident alerts.

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

Tagged areas include Tags. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 7 paths, and defines 20 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.

7 operations 7 paths 20 schemas 2 GET5 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
Resource Areas
1

Authentication & Security 1

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

Across 7 paths, the API surfaces 7 operations — 2 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

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

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are PublicMonitor (16 properties), MonitorConfig (7 properties), PublicAnomalyAlertRule (6 properties), TaggedObjectResponse (3 properties). Each schema is shown below with its type and property counts.

LabelNameValue
object
2 properties
MonitorConfig
object
7 properties
MonitorGrouping
object
List of all groups that have seen at least one datapoint for this monitor
1 property
PublicAlertRule
object
Optional alert rule configuration. Defaults to ANOMALY
2 properties
PublicAnomalyAlertRule
object
6 properties
PublicEntity
object
2 properties
PublicIncrementalClause
object
2 properties
PublicManualThreshold
object
2 properties
PublicManualThresholdRule
object
1 property
PublicMonitor
object
16 properties
PublicTagDefinition
object
3 properties
RemoveMonitorTagsRequest
object
2 properties
RemoveTableTagsRequest
object
3 properties
TagDefinitionRequest
object
1 property
TagMonitorsRequest
object
2 properties
TagMonitorsResult
object
2 properties
TagTablesRequest
object
3 properties
TagTablesResult
object
2 properties
TaggedObjectResponse
object
3 properties
TimeDuration
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

metaplane-tags-api-openapi.yml Raw ↑

Other APIs Metaplane publishes across the network.

Metaplane API
Metaplane Connections API
Metaplane Monitors API
Where this information came from

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