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

Topograph Monitors API

The Monitors API from Topograph — 3 operation(s) for monitors.

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

Tagged areas include Monitors. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 0.1.

Requests are made against a single base URL, https://api.topograph.co.

5 operations 3 paths 7 schemas 1 DELETE3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1
Base URL
https://api.topograph.co
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Topograph Monitors API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (x-api-key). By default, every request must be authenticated.

Paths & Operations 5

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

Monitors 5
POST
/v2/monitors
Add monitoring for a company
MonitoringController_createMonitor_v2 body → 201400401
GET
/v2/monitors
List monitored companies
MonitoringController_listMonitors_v2 4 params → 200401
GET
/v2/monitors/{id}
Get monitor details
MonitoringController_getMonitor_v2 1 param → 200401404
DELETE
/v2/monitors/{id}
Stop monitoring a company
MonitoringController_stopMonitoring_v2 1 param → 204401404
GET
/v2/monitors/{id}/logs
Get monitor change logs
MonitoringController_getMonitorLogs_v2 3 params → 200401404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are MonitorDetailsResponseDto (7 properties), MonitorLogDto (6 properties), MonitorDto (5 properties), ListMonitorsResponseDto (4 properties). Each schema is shown below with its type and property counts.

MonitorDto
object
5 properties 3 required
CreateMonitorResponseDto
object
4 properties 3 required
MonitorLogsResponseDto
object
3 properties 2 required
MonitorDetailsResponseDto
object
7 properties 4 required
CreateMonitorDto
object
3 properties 2 required
MonitorLogDto
object
6 properties 5 required
ListMonitorsResponseDto
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

topograph-monitors-api-openapi.yml Raw ↑

Other APIs Topograph publishes across the network.

Topograph Billing API
Topograph Billing Notifications API
Topograph Data API
Topograph Pricing API
Topograph Search API
Topograph Workspaces API
Where this information came from

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