{"id":2663,"date":"2025-09-25T15:37:14","date_gmt":"2025-09-25T15:37:14","guid":{"rendered":"https:\/\/uptimerobot.com\/blog\/?p=2663"},"modified":"2026-01-19T15:05:50","modified_gmt":"2026-01-19T15:05:50","slug":"introducing-the-uptimerobot-v3-api","status":"publish","type":"post","link":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/","title":{"rendered":"Introducing the UptimeRobot v3 API"},"content":{"rendered":"\r\n<p>As you may have noticed, we released the latest version of the UptimeRobot API a few weeks ago. Don\u2019t worry, the v2 will remain available; however, it will no longer receive support or updates. New features will be added only to v3.<\/p>\r\n\r\n\r\n\r\n<p>Built on a RESTful architecture, v3 unlocks more flexibility, cleaner workflows, and expanded capabilities for developers who want tighter control over their monitoring.<\/p>\r\n\r\n\r\n\r\n<p>Below, we\u2019ll highlight what\u2019s new and how it compares to the legacy v2 API.<\/p>\r\n\r\n\r\n\r\n<div class=\"wp-block-buttons is-content-justification-center is-layout-flex wp-container-core-buttons-is-layout-a89b3969 wp-block-buttons-is-layout-flex\">\r\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/uptimerobot.com\/api\/v3\/\">Check API Docs<\/a><\/div>\r\n<\/div>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\">Modern, consistent REST design<\/h2>\r\n\r\n\r\n\r\n<p><strong>Here\u2019s a look at what\u2019s changed in this category:<\/strong><\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li><strong>HTTP methods &amp; URLs:<\/strong> v2 used POST calls for all actions, with verb-style endpoint names (getMonitors, newMonitor, etc.). v3 uses standard HTTP verbs and resource-oriented paths: \r\n<ul class=\"wp-block-list\">\r\n<li><code>GET \/monitors<\/code> \u2013 list monitors<\/li>\r\n\r\n\r\n\r\n<li><code>POST \/monitors<\/code> \u2013 create a monitor<\/li>\r\n\r\n\r\n\r\n<li><code>PATCH \/monitors\/{id}<\/code> \u2013 update a monitor<\/li>\r\n\r\n\r\n\r\n<li><code>DELETE \/monitors\/{id}<\/code> \u2013 delete a monitor<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<p>The same approach applies to Public Status Pages (<code>\/psps<\/code>), Maintenance Windows (<code>\/maintenance-windows<\/code>), and Integrations (<code>\/integrations<\/code>).<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li><strong>Response format:<\/strong> v3 returns JSON only, simplifying parsing and avoiding extra parameters for format selection.<\/li>\r\n\r\n\r\n\r\n<li><strong>Authentication:<\/strong> v3 supports <strong>bearer tokens (JWT)<\/strong> passed in the Authorization header, replacing the need to send API keys in request bodies.<\/li>\r\n\r\n\r\n\r\n<li><strong>Pagination:<\/strong> v2 uses offset and limit, while v3 uses <strong>cursor-based pagination<\/strong>, which scales better for large datasets.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\">Extended resource coverage<\/h2>\r\n\r\n\r\n\r\n<p>We\u2019ve made some enhancements to monitors, public status pages, and maintenance windows as well.<\/p>\r\n\r\n\r\n\r\n<h3 class=\"wp-block-heading\">Monitors<\/h3>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>Supports HTTP, Keyword, Ping, and Port monitors (as in v2) plus <strong>two new types<\/strong>: \r\n<ul class=\"wp-block-list\">\r\n<li><strong>Heartbeat<\/strong> monitors: confirm that scheduled jobs or services are alive by expecting periodic pings.<\/li>\r\n\r\n\r\n\r\n<li><strong>DNS<\/strong> <strong>monitors: <\/strong>track DNS records and expiry dates.<\/li>\r\n<\/ul>\r\n<\/li>\r\n\r\n\r\n\r\n<li>Uses descriptive string values for parameters instead of numeric codes (e.g., type: HTTP instead of type=1).<\/li>\r\n\r\n\r\n\r\n<li>More granular options for timeouts, success codes, custom HTTP headers, SSL, and domain expiry reminders, tagging, and attaching to maintenance windows.<\/li>\r\n\r\n\r\n\r\n<li>Alert contact assignment is now handled with a structured array instead of encoded strings, making automation easier.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h3 class=\"wp-block-heading\">Public Status Pages (PSPs)<\/h3>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>RESTful endpoints (\/psps, \/psps\/{id}) replace action verbs like newPSP or editPSP.<\/li>\r\n\r\n\r\n\r\n<li>New customization options: light\/dark themes, density settings, and incident history display.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h3 class=\"wp-block-heading\">Maintenance windows<\/h3>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>Fully resource-based, with explicit names, start\/end times, recurrence rules, and monitor assignments via arrays.<\/li>\r\n\r\n\r\n\r\n<li>More predictable scheduling compared to string-encoded parameters in v2.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\">New integration system<\/h2>\r\n\r\n\r\n\r\n<p>One of the biggest additions in v3 is <strong>integrations<\/strong>. Instead of manually creating alert contacts for each channel, you can programmatically set up integrations for:<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>Slack, Microsoft Teams, Google Chat, Discord<\/li>\r\n\r\n\r\n\r\n<li>Telegram, Pushover, Pushbullet<\/li>\r\n\r\n\r\n\r\n<li>PagerDuty, Splunk, Mattermost, Zapier, Webhooks<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\">User information endpoints<\/h2>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li><strong>GET \/user\/me<\/strong> \u2013 fetches the logged-in user\u2019s profile, limits, and subscription details.<\/li>\r\n\r\n\r\n\r\n<li><strong>GET \/user\/alert-contacts<\/strong> \u2013 lists alert contacts directly.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\">Other improvements<\/h2>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li><strong>CORS<\/strong> \u2013 v3 uses modern authentication headers, simplifying browser-side integrations.<\/li>\r\n\r\n\r\n\r\n<li><strong>Rate limits<\/strong> \u2013 same plan-based limits as v2 (10 req\/min on free plans; monitor_limit \u00d7 2 req\/min on Pro, up to 5,000\/min), but with standardized 429 responses and rate-limit headers.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\">Why upgrade to v3?<\/h2>\r\n\r\n\r\n\r\n<p>The v3 API delivers concrete improvements over v2:<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li><strong>Consistent RESTful endpoints<\/strong>: no more verb-based calls or POST-only methods; HTTP verbs map directly to CRUD operations.<\/li>\r\n\r\n\r\n\r\n<li><strong>Structured payloads<\/strong>: parameters are named and typed in a predictable way, avoiding numeric codes and string-encoded settings.<\/li>\r\n\r\n\r\n\r\n<li><strong>New capabilities<\/strong>: Heartbeat and DNS monitors, richer PSP customization, detailed maintenance window scheduling, and direct integration management.<\/li>\r\n\r\n\r\n\r\n<li><strong>Better automation support<\/strong>: Cursor-based pagination, machine-readable enums, and JSON-only responses make scripting simpler.<\/li>\r\n\r\n\r\n\r\n<li><strong>Modern authentication<\/strong>: Bearer tokens via the Authorization header enable safer, more flexible integration patterns.<\/li>\r\n\r\n\r\n\r\n<li><strong>Browser-friendly<\/strong>: CORS restrictions in v2 are gone, making client-side API calls easier to implement.<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\">Share your feedback<\/h2>\r\n\r\n\r\n\r\n<p>Explore the<a href=\"https:\/\/uptimerobot.com\/api\/v3\/\"> UptimeRobot v3 API documentation<\/a> and start upgrading your scripts and integrations to take advantage of the new capabilities.<\/p>\r\n\r\n\r\n\r\n<p>We\u2019d love to hear what you think \u2013 join the discussion and share your feedback on our <a href=\"https:\/\/discord.gg\/FjEDr7hbnB\">Discord community<\/a>. Your input helps us shape the next iterations of the API and other UptimeRobot features.<\/p>\r\n","protected":false},"excerpt":{"rendered":"<p>As you may have noticed, we released the latest version of the UptimeRobot API a few weeks ago. Don\u2019t worry, the v2 will remain available; however, it will no longer receive support or updates. New features will be added only to v3. Built on a RESTful architecture, v3 unlocks more flexibility, cleaner workflows, and expanded [&hellip;]<\/p>\n","protected":false},"author":16,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"_is_featured_guide":false,"_post_views":105,"_reading_completions":117,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-2663","post","type-post","status-publish","format-standard","hentry","category-announcements"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Introducing the UptimeRobot v3 API | UptimeRobot Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Introducing the UptimeRobot v3 API | UptimeRobot Blog\" \/>\n<meta property=\"og:description\" content=\"As you may have noticed, we released the latest version of the UptimeRobot API a few weeks ago. Don\u2019t worry, the v2 will remain available; however, it will no longer receive support or updates. New features will be added only to v3. Built on a RESTful architecture, v3 unlocks more flexibility, cleaner workflows, and expanded [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/\" \/>\n<meta property=\"og:site_name\" content=\"UptimeRobot Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-09-25T15:37:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-19T15:05:50+00:00\" \/>\n<meta name=\"author\" content=\"Tomas Koprusak\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Tomas Koprusak\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/\"},\"author\":{\"name\":\"Tomas Koprusak\",\"@id\":\"https:\/\/uptimerobot.com\/blog\/#\/schema\/person\/4e351b3eb3c7a5987a73b413d8354468\"},\"headline\":\"Introducing the UptimeRobot v3 API\",\"datePublished\":\"2025-09-25T15:37:14+00:00\",\"dateModified\":\"2026-01-19T15:05:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/\"},\"wordCount\":636,\"articleSection\":[\"Announcements\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/\",\"url\":\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/\",\"name\":\"Introducing the UptimeRobot v3 API | UptimeRobot Blog\",\"isPartOf\":{\"@id\":\"https:\/\/uptimerobot.com\/blog\/#website\"},\"datePublished\":\"2025-09-25T15:37:14+00:00\",\"dateModified\":\"2026-01-19T15:05:50+00:00\",\"author\":{\"@id\":\"https:\/\/uptimerobot.com\/blog\/#\/schema\/person\/4e351b3eb3c7a5987a73b413d8354468\"},\"breadcrumb\":{\"@id\":\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/uptimerobot.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Announcements\",\"item\":\"https:\/\/uptimerobot.com\/blog\/category\/announcements\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Introducing the UptimeRobot v3 API\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/uptimerobot.com\/blog\/#website\",\"url\":\"https:\/\/uptimerobot.com\/blog\/\",\"name\":\"UptimeRobot Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/uptimerobot.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/uptimerobot.com\/blog\/#\/schema\/person\/4e351b3eb3c7a5987a73b413d8354468\",\"name\":\"Tomas Koprusak\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/uptimerobot.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/42e6751dc39e91f1c7ab4926189550054308e366428ceb70e9621d680b843032?s=96&d=retro&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/42e6751dc39e91f1c7ab4926189550054308e366428ceb70e9621d680b843032?s=96&d=retro&r=g\",\"caption\":\"Tomas Koprusak\"},\"description\":\"He has worked for Sygic as a marketer and co-led the implementation and development of a product acquired from a competitor. He has also worked as a freelance developer, helping clients from various areas. Tomas brings a wealth of industry experience to our team. He spent a few years in the blockchain industry, leading projects and marketing teams at multiple blockchain-based companies. He has presented products and managed deals in more than 10 countries around the world, managed the ICO, and built a successful marketing team at Fuergy that continues to thrive. Tomas managed a product team for the biggest job site in Slovakia, covering development and transformation to a new B2B app. Not only is Tomas skilled at web development, but he also has a deep understanding of SaaS businesses, which makes him an invaluable asset in shaping and leading various projects at UptimeRobot. His focus is always on the continual improvement of our service and user experience. In addition to his professional achievements, Tomas is a devoted father. His personal interests include cycling (he traveled around the whole country of Slovakia), playing guitar (he even played in a band), servicing bikes, music, and enjoying good beer.\",\"sameAs\":[\"https:\/\/www.linkedin.com\/in\/tomas-koprusak\"],\"url\":\"https:\/\/uptimerobot.com\/blog\/author\/tomas\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Introducing the UptimeRobot v3 API | UptimeRobot Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/","og_locale":"en_US","og_type":"article","og_title":"Introducing the UptimeRobot v3 API | UptimeRobot Blog","og_description":"As you may have noticed, we released the latest version of the UptimeRobot API a few weeks ago. Don\u2019t worry, the v2 will remain available; however, it will no longer receive support or updates. New features will be added only to v3. Built on a RESTful architecture, v3 unlocks more flexibility, cleaner workflows, and expanded [&hellip;]","og_url":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/","og_site_name":"UptimeRobot Blog","article_published_time":"2025-09-25T15:37:14+00:00","article_modified_time":"2026-01-19T15:05:50+00:00","author":"Tomas Koprusak","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Tomas Koprusak","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/#article","isPartOf":{"@id":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/"},"author":{"name":"Tomas Koprusak","@id":"https:\/\/uptimerobot.com\/blog\/#\/schema\/person\/4e351b3eb3c7a5987a73b413d8354468"},"headline":"Introducing the UptimeRobot v3 API","datePublished":"2025-09-25T15:37:14+00:00","dateModified":"2026-01-19T15:05:50+00:00","mainEntityOfPage":{"@id":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/"},"wordCount":636,"articleSection":["Announcements"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/","url":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/","name":"Introducing the UptimeRobot v3 API | UptimeRobot Blog","isPartOf":{"@id":"https:\/\/uptimerobot.com\/blog\/#website"},"datePublished":"2025-09-25T15:37:14+00:00","dateModified":"2026-01-19T15:05:50+00:00","author":{"@id":"https:\/\/uptimerobot.com\/blog\/#\/schema\/person\/4e351b3eb3c7a5987a73b413d8354468"},"breadcrumb":{"@id":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/uptimerobot.com\/blog\/introducing-the-uptimerobot-v3-api\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/uptimerobot.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Announcements","item":"https:\/\/uptimerobot.com\/blog\/category\/announcements\/"},{"@type":"ListItem","position":3,"name":"Introducing the UptimeRobot v3 API"}]},{"@type":"WebSite","@id":"https:\/\/uptimerobot.com\/blog\/#website","url":"https:\/\/uptimerobot.com\/blog\/","name":"UptimeRobot Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/uptimerobot.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/uptimerobot.com\/blog\/#\/schema\/person\/4e351b3eb3c7a5987a73b413d8354468","name":"Tomas Koprusak","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/uptimerobot.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/42e6751dc39e91f1c7ab4926189550054308e366428ceb70e9621d680b843032?s=96&d=retro&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/42e6751dc39e91f1c7ab4926189550054308e366428ceb70e9621d680b843032?s=96&d=retro&r=g","caption":"Tomas Koprusak"},"description":"He has worked for Sygic as a marketer and co-led the implementation and development of a product acquired from a competitor. He has also worked as a freelance developer, helping clients from various areas. Tomas brings a wealth of industry experience to our team. He spent a few years in the blockchain industry, leading projects and marketing teams at multiple blockchain-based companies. He has presented products and managed deals in more than 10 countries around the world, managed the ICO, and built a successful marketing team at Fuergy that continues to thrive. Tomas managed a product team for the biggest job site in Slovakia, covering development and transformation to a new B2B app. Not only is Tomas skilled at web development, but he also has a deep understanding of SaaS businesses, which makes him an invaluable asset in shaping and leading various projects at UptimeRobot. His focus is always on the continual improvement of our service and user experience. In addition to his professional achievements, Tomas is a devoted father. His personal interests include cycling (he traveled around the whole country of Slovakia), playing guitar (he even played in a band), servicing bikes, music, and enjoying good beer.","sameAs":["https:\/\/www.linkedin.com\/in\/tomas-koprusak"],"url":"https:\/\/uptimerobot.com\/blog\/author\/tomas\/"}]}},"_links":{"self":[{"href":"https:\/\/uptimerobot.com\/blog\/wp-json\/wp\/v2\/posts\/2663","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/uptimerobot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/uptimerobot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/uptimerobot.com\/blog\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/uptimerobot.com\/blog\/wp-json\/wp\/v2\/comments?post=2663"}],"version-history":[{"count":0,"href":"https:\/\/uptimerobot.com\/blog\/wp-json\/wp\/v2\/posts\/2663\/revisions"}],"wp:attachment":[{"href":"https:\/\/uptimerobot.com\/blog\/wp-json\/wp\/v2\/media?parent=2663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/uptimerobot.com\/blog\/wp-json\/wp\/v2\/categories?post=2663"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/uptimerobot.com\/blog\/wp-json\/wp\/v2\/tags?post=2663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}