SignalFx REST API

The SignalFx REST API manages metadata and configuration objects in Splunk Observability Cloud / SignalFx: metrics and dimension metadata, detectors and alert muting rules, charts, dashboards and dashboard groups, teams, data links, SLOs, organization and access tokens, metric rulesets, and cloud/notification integrations (AWS, Azure, GCP, PagerDuty, Slack, Opsgenie, Jira, ServiceNow). It is realm-based (api.{realm}.signalfx.com) and authenticated with the X-SF-Token header.

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/signalfx-rest-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

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.

API entry from apis.yml

apis.yml Raw ↑
name: SignalFx REST API
description: 'The SignalFx REST API manages metadata and configuration objects in Splunk Observability
  Cloud / SignalFx: metrics and dimension metadata, detectors and alert muting rules, charts, dashboards
  and dashboard groups, teams, data links, SLOs, organization and access tokens, metric rulesets, and
  cloud/notification integrations (AWS, Azure, GCP, PagerDuty, Slack, Opsgenie, Jira, ServiceNow). It
  is realm-based (api.{realm}.signalfx.com) and authenticated with the X-SF-Token header.'
humanURL: https://dev.splunk.com/observability/reference
baseURL: https://api.us1.signalfx.com
properties:
- type: Documentation
  url: https://dev.splunk.com/observability/docs
- type: APIReference
  url: https://dev.splunk.com/observability/reference
- type: Authentication
  url: authentication/signalfx-authentication.yml
- type: Conventions
  url: conventions/signalfx-conventions.yml
- type: X-MCPServerCandidate
  url: mcp/signalfx-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate
    — a tool list derived from the published API contracts, not an existing server. The scorer already
    read the manifest and reported mcp_server correctly; the MCPServer type was crediting the artifact-type
    surfaces with a server that does not exist.'