# Monitoring API & Integrations for Agencies | Uptimeify > Automate onboarding & incident workflows via REST API and webhooks. Native Slack, Teams & Discord integrations, for agencies & MSPs. Start free today. Source: https://uptimeify.io/features/smart-operations/api-integrations Wire Uptimeify into the stack your agency already runs. Provision clients through the REST API, route incidents through webhooks into your own tools, and turn monitoring into an operational layer instead of a data-entry screen. Start Free Trial Explore Success Kit ## A monitoring API built for agencies. No more manual work. For the technical stakeholder ### Authentication, customer scope & rate limit This is how it is wired. View API Reference https://docs.uptimeify.io/api Manage Create and configure monitors programmatically. Data Pull real-time stats and incident histories. Auth scoped keys granular access control. API Layer ## limits. Build without Anything you can do in the dashboard, you can do through the API. The RESTful architecture lets you create monitors programmatically, manage sub-accounts and pull uptime data straight into your own tools or client portals, without ever touching a form by hand. - **Programmatic management**, so you roll out monitors and config automatically instead of clicking through them client by client. - **Real-time data access**, so you pull uptime numbers and incident history into your own dashboards and reports. - **Scoped API keys**, so every integration sees only what it should, and no client ever reaches the account next door. For the technical stakeholder ### Customer/website creation & bulk provisioning This is how it is wired. Learn more about Client Accounts Integration Connect to WHMCS, CRM or deployment scripts. Bulk Apply settings across subaccounts in one run. Live Monitoring active before the new site goes live. Provisioning Layer ## zero manual cleanup. Onboarding with For agencies running hundreds of clients, setup by hand isn't an option. Hook Uptimeify into your provisioning script: spin up a new client site, and monitoring, alert rules and white-label reports are live before the site itself goes live. - **Provisioning hooks**, so you fire Uptimeify from WHMCS, a CRM or your own deployment script. - **Bulk configuration**, so you push settings across multiple sub-accounts in a single run instead of patching each one. - **Isolated client spaces**, so every new tenant starts cleanly separated, straight from your single source of truth. For the technical stakeholder ### Webhook payloads, headers & status logic This is how it is wired. View API Docs https://docs.uptimeify.io/api Payloads JSON detailed per incident and recovery. Headers Custom auth headers for private endpoints. Logic Different actions for Up, Down or Degraded. Webhook Layer ## not just emails. Trigger actions, Monitoring only earns its keep when an incident moves cleanly through your delivery process. Native integrations push alerts where your team already works. Webhooks turn every status change into an automated step. - **Native ChatOps**, so Slack, Microsoft Teams and Discord get the alert without anyone polling an inbox. - **Workflow automation via Zapier or Make**, so a single incident fires multi-step chains, from ticket to escalation. - **Real-time webhooks with JSON payloads**, so you trigger auto-restarts, open Jira tickets or update your billing. For the technical stakeholder ### Monitoring node IPs & firewall whitelist This is how it is wired. View API Docs https://docs.uptimeify.io/api Nodes eu-central active node IPs as JSON. Region Polling from European locations, no US nodes. Whitelist Always-current list, no US sub-processors with data access. Infrastructure Layer ## for professionals. Documentation and infrastructure Strong integrations start with clear communication. You don't just get endpoints. You get the context your team needs for a stable implementation, plus the infrastructure facts every firewall sign-off asks for. - **Developer-friendly docs**, so your team works with clean payloads and in-browser try-it-out instead of guessing. - **IP whitelist service**, so you configure your firewall against an always-current list of our monitoring nodes, precisely and without guesswork. - **Public roadmap**, so you know which API features and integrations land next. For the technical stakeholder ### Transport, auth and token scope: how the MCP server is wired This is how it is wired. Learn more about our MCP server Read the MCP docs https://docs.uptimeify.io/api/mcp Transport Streamable HTTP stateless, no local process. No npm package, no wrapper for you to maintain. POST https://uptimeify.io/mcp Auth The token scope is the boundary, not a setting in the client. Authorization: Bearer wsm_your_token Account-bound list_monitors, monitor_status, check_history, uptime_summary, list_incidents, list_alert_channels, alert_history, list_status_pages, list_maintenance_windows, get_organization, list_users, list_customers and billing_summary return only what the token is allowed to see. The last four also emit a fixed list of fields, so contact details, addresses, VAT ids, tariff names and payment methods never leave with them. Diagnostics check_dns, dns_propagation, check_ssl, hsts_check, http_headers, redirect_check, website_status, response_time, ping_test, port_check, reverse_dns, ip_geolocation, asn_lookup, whois, domain_expiry, mx_lookup, spf_check, dkim_check, dmarc_check and dnsbl_check run against arbitrary targets and therefore need no rights on your account. So a check_ssl on deinkunde.com works before a monitor for it even exists. Write access 33 read 43 write, opt-in every write tool sits behind its own consent scope, granted apart from read. Forty-three tools can change state, pause or resume a monitor, create or delete one, acknowledge or resolve an incident, plan a maintenance window, run a status page, manage alert channels and keep the organization's tags, custom fields, reports and customers, one consent scope per area (monitors, incidents, maintenance windows, status pages, alerts, organization), plus a confirmation on the call itself naming that exact change. Grant nothing, and none of it runs. Prefer to automate without that per-call ceremony? The REST API stays the direct, traceable route. Location Executed on the European stack in Frankfurt, without US sub-processors. Agent Layer Uptimeify dashboard showing uptime status, open incidents and the customer overview across an agency portfolio ## instead of clicking through it. MCP server: ask your monitoring Your client's question always arrives in the same shape: is the site still up? Until now that meant opening the dashboard, finding the monitor, reading the history, replying. With the MCP server you ask that same question inside the tool you already work in, and the answer comes back in a form you can pass on as it stands. A click path becomes a single line. At thirty clients in your portfolio that is not convenience, it is time you stop writing off. - **Portfolio status in plain language.** Monitors, open incidents and uptime figures come back as an answer, not as a view, so you prove it on the client call instead of looking it up. - **20 diagnostic tools behind one connection.** DNS, TLS certificates, SPF, DKIM, DMARC, blacklists, redirects, ports and latency, so you name the cause before your client sends the second email. - **Token scope per client.** A client token sees nothing beyond its own sub-account, so tenant isolation holds even when an AI is asking the questions. - **Twenty prompts already written.** The [Prompt Library](/resources/success-kit/prompt-library) covers mail records, certificate deadlines, DNS moves, outage triage and client reports, ten of them without an account, so you start with a working prompt instead of a blank chat. ### SLA & Contract Templates Service Level Agreement templates to define professional boundaries with your clients. ### Pricing Calculator Find the sweet spot for your care plans. Calculate margins based on check frequency and support hours. ### White-Label Pitch Decks Powerpoint Templates that explain 24/7 monitoring to non-technical clients. Close more retainers. ### Churn-Proof Reporting Guide Use automated reports to proactively communicate value, so clients never ask what they're paying for. Claim your Success Kit and start scaling today. Claim your Success Kit & Start Monitoring Ready to turn monitoring into a profit center? Every Uptimeify subscription includes access to our Success Kit, a collection of battle-tested resources to turn your monitoring into a profit center. ## We don't just monitor. We help you sell. → For the technical stakeholder ### Token scopes & rate limit: how it's wired API tokens carry the `wsm_` prefix and come in two scopes: organization-wide for full portfolio reach, customer-scoped for external integrations that touch a single tenant only. Anything outside the scope returns 403. Auth is via bearer token in the header, responses are JSON throughout. The rate limit sits at 600 requests per minute per IP; you read your remaining quota from `X-RateLimit-Remaining`, and going over returns a 429. Can you create client accounts and monitors fully automatically through the API? Yes. You create clients, websites and every monitor type programmatically, without ever opening the dashboard as an input form. You hook the API into your provisioning script so a new tenant's monitoring and alert rules are standing before the site goes live. That lets you scale your portfolio instead of piling up click-work per client. Which tools connect natively, with no code? Slack, Microsoft Teams and Discord connect directly in seconds, no code required. For multi-step flows you drop Zapier or Make in between and let an incident fire entire workflow chains. So every alert lands where your team already works instead of going stale in an inbox. How flexible are the webhooks for your own automations? Every status change sends a JSON payload: incident, recovery, timestamp, affected monitor, to any URL you point it at. You set custom auth headers for private endpoints and attach a different action to each up, down or degraded. That lets you build auto-restarts, ticket creation or billing updates straight into your own process. Where do you find the monitoring node IPs for your firewall? You pull the current list of node IPs anytime as JSON via the API or the public IP page, each entry with its region and active status, always up to date. That lets you configure your firewall rules precisely instead of chasing a stale list. Polling locations sit across Europe, no US sub-processors with access to your customer or monitoring data. Do you need developer skills to use the MCP server? No. You store the endpoint URL and your API token in your AI client once, then you ask in plain language. The 33 tools sit behind that, and you never need to know one of them by name. That means your support team answers a status question in seconds without dashboard access. If you want to automate rather than ask, stay on the REST API: the [MCP server](/mcp-server) can write too now, but only in the scopes you grant it, area by area, never as a blanket default. Can you export uptime data into your own client portals? Yes. Through the API you pull real-time stats, uptime numbers and incident history into your own dashboards or white-label portals. You decide what your client sees and in which layout. So monitoring stays visibly your work under your brand, not some third-party tool's. Tool scope and write access: how it is boundaried 33 tools only read. Account-bound ones respect the scope of the bearer token, diagnostic ones work against arbitrary domains or IPs and touch your account for nothing. Forty-three more can write, pause or resume a monitor, create or delete one, acknowledge or resolve an incident, plan maintenance, run a status page, manage alert channels and keep the organization's tags, custom fields, reports and customers, but only behind their own consent scope, one per area and granted apart from read access, plus a confirmation on the call itself naming that exact change. Grant nothing, and nothing writes. If you want to automate without that per-call ceremony, the REST API stays the direct, traceable route. FAQ ## Frequently Asked Questions Open the API docs, connect your workflows and turn monitoring into a cleaner operational system for every client environment. One plan, your brand, your stack. ## Ready to wire monitoring into your agency stack?