Verifiable Monitoring API

Endpoints to allow you to enable/disable monitoring or update monitoring settings for monitorable data. ## License Expiration Monitoring License Expiration Monitoring is a process that automatically performs verifications of licenses as they approach their expiration date. This process operates independently of a license's configured monitoring interval (e.g., Monthly, Yearly). Its purpose is to ensure timely updates and proactive management of expiring licenses. ### License Expiration Monitoring for Free Sources For licenses verified via free sources (those without pass-through fees), the Verifiable Platform follows a more frequent and proactive monitoring to ensure timely updates. This increased frequency applies regardless of the license's general monitoring interval. Verifications are performed at the following intervals, relative to the license expiration date: - Before license expiration: 90, 60, 28, 14, 7, 3, and 0 days - After license expiration: 3 days This means the Verifiable Platform will check the license 90 days before it expires, then 60 days before, and so on, until the day of expiration (0 days). A final check is performed 3 days after the expiration date. ### License Expiration Monitoring for Paid Sources For licenses verified via paid sources (those with pass-through fees), the Verifiable Platform follows a more streamlined monitoring for efficient management to minimize costs incurred to users. - After license expiration: 1 day As with free verification sources, these licenses will also continue to be monitored at their scheduled cadence regardless of this expiration check.

Business capability
Practitioner Credentialing BC-2890.10

Operations 6

POST /monitors Initiate monitoring for a provider or facility #
GET /monitors Lists all the monitored items #
POST /monitors/bulk/sanctions-and-exclusions Initiates monitoring for the specified Sanctions and Exclusions datasets for… #
GET /monitors/{id} Returns a specified monitored item #
PATCH /monitors/{id} Patch an existing monitored item #
DELETE /monitors/{id} Stop monitoring an item #

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/verifiable-monitoring-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.

OpenAPI Specification

verifiable-monitoring-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Verifiable API Documentation Monitoring API
  description: '# Introduction


    This document contains the official documentation for the latest version of the Verifiable API.'
  version: 26.12.1.962
servers:
- url: https://discovery.verifiable.com/api
  description: Production
- url: https://discovery-staging.verifiable.com/api
  description: Staging
tags:


# --- truncated at 32 KB (146 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/verifiable/refs/heads/main/openapi/verifiable-monitoring-api-openapi.yml