{"id":4218,"date":"2026-03-16T10:11:26","date_gmt":"2026-03-16T04:41:26","guid":{"rendered":"https:\/\/www.enablex.io\/insights\/?p=4218"},"modified":"2026-04-27T10:12:02","modified_gmt":"2026-04-27T04:42:02","slug":"migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex","status":"publish","type":"post","link":"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/","title":{"rendered":"Migrating from SMS, WhatsApp, or RCS APIs to the EnableX"},"content":{"rendered":"\n<p>Move from channel-based messaging to intelligent messaging orchestration\u2014start single-channel today, add fallback tomorrow, and scale without rewrites.<\/p>\n\n\n\n<p>Most teams begin with a single channel\u2014typically&nbsp;<strong>SMS<\/strong>,&nbsp;<strong>WhatsApp<\/strong>, or&nbsp;<strong><a href=\"\/insights\/RCS-messaging-all-you-need-to-know\/\">RCS<\/a><\/strong>\u2014and build workflows around it. As requirements evolve, you need faster OTPs, richer engagement, higher reliability, and smarter cost controls. That\u2019s when multi-channel integrations and DIY fallback logic start to add complexity. EnableX&nbsp;<strong>Unified Messaging API<\/strong>&nbsp;gives you a&nbsp;<em>single endpoint<\/em>&nbsp;across SMS, WhatsApp, and RCS\u2014while still letting you use just one channel until you\u2019re ready to expand.&nbsp;<a href=\"https:\/\/developer.enablex.io\/docs\/references\/apis\/unified-messaging-api\/index\/\">Explore the API<\/a>.<\/p>\n\n\n<p><strong>Key advantages:<\/strong>\u00a0One endpoint, unified message ID, single webhook, built-in fallback, and smart routing modes (order, budget, priority).<\/p>\n\n\n<h2 class=\"wp-block-heading\" style=\"text-transform:capitalize\">Why migrate to Unified Messaging?<\/h2>\n\n\n<ul>\n<li><strong>Eliminate integration sprawl:<\/strong>\u00a0move from multiple endpoints, payloads, and webhooks to one.<\/li>\n<li><strong>Keep it simple:<\/strong>\u00a0continue with a single channel exactly as you do today; no behavior change required.<\/li>\n<li><strong>Future-ready:<\/strong>\u00a0enable fallback or smart routing later with a small payload change\u2014no new infrastructure.<\/li>\n<\/ul>\n\n\n<p><a href=\"\/insights\/sms-to-rcs-omnichannel-messaging-strategy\/\">Why moving to RCS inside an omnichannel strategy matters<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1 \u2014 Replace your Send endpoint<\/h2>\n\n\n\n<p class=\"has-medium-font-size\">Example: Migrating from SMS Send API \u2192 Unified Messaging<\/p>\n\n\n\n<p><mark style=\"color:#0693e3;background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">Before \u2014 SMS API<\/mark><\/p>\n\n\n<pre id=\"sms-before\"><code class=\"language-json\">POST \/sms\/v1\/messages\n{\n  \"from\": \"ENXOTP\",\n  \"to\": \"+919999999999\",\n  \"data\": {\n    \"text\": \"Your OTP is 1234\"\n  }\n}<br \/><\/code><\/pre>\n\n\n<p><mark style=\"color:#0693e3;background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">After \u2014 Unified Messaging API (single-channel SMS)<\/mark><\/p>\n\n\n<pre id=\"sms-after\"><code class=\"language-json\">POST \/messaging\/v1\/messages\n{\n  \"to\": \"+919999999999\",\n  \"channels\": [\"sms\"],\n  \"preference\": \"order\",\n  \"sms\": {\n    \"from\": \"ENXOTP\",\n    \"data\": {\n      \"text\": \"Your OTP is 1234\"\n    }\n  }\n}<\/code><\/pre>\n\n\n<p>That\u2019s it\u2014you\u2019re on Unified Messaging with&nbsp;<em>no behavior changes and no routing changes<\/em>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2 \u2014 Migrate WhatsApp Messaging<\/h2>\n\n\n\n<p>Template message example<\/p>\n\n\n\n<p><mark style=\"color: #0693e3;background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">Before \u2014 WhatsApp Messages API<\/mark><\/p>\n\n\n<pre id=\"wa-before\"><code class=\"language-json\">{\n  \"to\": \"+919999999999\",\n  \"type\": \"template\",\n  \"template\": {\n    \"language\": { \"code\": \"en\" },\n    \"name\": \"order_update\"\n  }\n}<\/code><\/pre>\n\n\n<p><mark style=\"color: #0693e3;background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">After \u2014 Unified Messaging (single-channel WhatsApp)<\/mark><\/p>\n\n\n<pre id=\"wa-after\"><code class=\"language-json\">{\n  \"to\": \"+919999999999\",\n  \"channels\": [\"whatsapp\"],\n  \"whatsapp\": {\n    \"type\": \"template\",\n    \"template\": {\n      \"language\": { \"code\": \"en\" },\n      \"name\": \"order_update\"\n    }\n  }\n}<br \/><br \/><\/code><\/pre>\n\n\n<h2 class=\"wp-block-heading\">Step 3 \u2014 Migrate\u00a0RCS\u00a0Messaging<\/h2>\n\n\n\n<p><mark style=\"color: #0693e3;background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">Before \u2014 RCS API<\/mark><\/p>\n\n\n<pre id=\"rcs-before\"><code class=\"language-json\">POST \/rcs\/v1\/messages\n{\n  \"phone\": \"+919999999999\",\n  \"type\": \"text\",\n  \"agent\": \"brand_agent\",\n  \"fallback_text\": \"Order confirmed\"\n}<\/code><\/pre>\n\n\n<p><mark style=\"color: #0693e3;background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">After \u2014 Unified Messaging (single-channel RCS)<\/mark><\/p>\n\n\n<pre id=\"rcs-after\"><code class=\"language-json\">{\n  \"to\": \"+919999999999\",\n  \"channels\": [\"rcs\"],\n  \"rcs\": {\n    \"type\": \"text\",\n    \"agent\": \"brand_agent\",\n    \"fallback_text\": \"Order confirmed\"\n  }\n}<br \/><\/code><\/pre>\n\n\n<h2 class=\"wp-block-heading\">Prefer single channel? Keep it that way.<\/h2>\n\n\n\n<p>Unified Messaging lets you continue with &#8220;channels&#8221;: [&#8220;sms&#8221;] or &#8220;channels&#8221;: [&#8220;whatsapp&#8221;] and gain unified tracking plus a single webhook\u2014no change in behavior.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4 \u2014 Add automatic fallback later (one small change)<\/h2>\n\n\n\n<p>Turn on failover from WhatsApp \u2192 SMS<\/p>\n\n\n\n<p><mark style=\"color: #0693e3;background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">From<\/mark><\/p>\n\n\n<pre id=\"fallback-from\"><code class=\"language-json\">\"channels\": [\"whatsapp\"]<\/code><\/pre>\n\n\n<p><mark style=\"color: #0693e3;background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">To<\/mark><\/p>\n\n\n<pre id=\"fallback-to\"><code class=\"language-json\">\"channels\": [\"whatsapp\", \"sms\"]<\/code><\/pre>\n\n\n<p>Unified Messaging will try WhatsApp first and automatically fallback to SMS if needed\u2014no retry scripts or monitoring code required.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5 \u2014 Enable Smart Routing<\/h2>\n\n\n\n<p>Choose routing modes that fit your use case:&nbsp;order,&nbsp;budget, or&nbsp;priority. For OTPs and critical alerts, priority&nbsp;selects the most reliable, fast-performing channel.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Unsupported keys &amp; payload differences<\/h2>\n\n\n\n<p>Unified Messaging stays close to original channel payloads, but some channel\u2011specific keys are intentionally excluded to maintain a consistent model. Review the \u201cUnsupported objects\/keys\u201d section before migrating.<\/p>\n\n\n<p>Docs:\u00a0<a href=\"https:\/\/developer.enablex.io\/docs\/references\/apis\/unified-messaging-api\/content\/api-routes\/\" rel=\"noopener\">Unified Messaging API<\/a>\u00a0\u2022\u00a0<a href=\"https:\/\/developer.enablex.io\/docs\/references\/apis\/sms-api\/content\/api-routes\/\" rel=\"noopener\">SMS API<\/a>\u00a0\u2022\u00a0<a href=\"https:\/\/developer.enablex.io\/docs\/references\/apis\/whatsapp-business-api\/content\/api-routes\/messages-api\/index\/\" rel=\"noopener\">WhatsApp API<\/a>\u00a0\u2022\u00a0<a href=\"https:\/\/developer.enablex.io\/docs\/references\/apis\/rcs-api\/content\/api-routes\/index\/\" rel=\"noopener\">RCS API<\/a><\/p>\n\n\n<h2 class=\"wp-block-heading\">Migration Checklist<\/h2>\n\n\n\n<p>Planning a shift from SMS to RCS? Start with this readiness guide:&nbsp;<a href=\"\/insights\/8-questions-to-ask-before-you-shift-from-sms-to-rcs\/\">8 questions to ask before you shift<\/a>.<\/p>\n\n\n<ol>\n<li><strong>Change endpoint<\/strong>\u00a0to\u00a0\/messaging\/v1\/messages (from channel-specific endpoints).<\/li>\n<li><strong>Wrap payload<\/strong>: add\u00a0channels\u00a0and the channel object (sms\u00a0\/\u00a0whatsapp\u00a0\/\u00a0rcs).<\/li>\n<li><strong>Store unified<\/strong>\u00a0message_id\u00a0for tracking.<\/li>\n<li><strong>Update webhook<\/strong>\u00a0to a single Unified Messaging webhook (replace multiple channel webhooks).<\/li>\n<\/ol>\n\n\n<h2 class=\"wp-block-heading\">Start migrating today<\/h2>\n\n\n\n<p>Move from channel-based messaging to intelligent orchestration\u2014at your own pace.<\/p>\n\n\n\n<div style=\"height:17px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-group has-white-background-color has-background is-nowrap is-layout-flex wp-container-2 wp-block-group-is-layout-flex\">\n<div class=\"wp-block-buttons is-content-justification-left is-layout-flex wp-container-1 wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/developer.enablex.io\/docs\/references\/apis\/unified-messaging-api\/index\/\">Read the Unified Messaging Docs<\/a><\/div>\n\n\n\n<div class=\"wp-block-button has-custom-font-size has-medium-font-size\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/www.enablex.io\/contact-us\/\">Talk to an Expert<\/a><\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Move from channel-based messaging to intelligent messaging orchestration\u2014start single-channel today, add fallback tomorrow, and scale without rewrites. Most teams begin with a single channel\u2014typically&nbsp;SMS,&nbsp;WhatsApp, or&nbsp;RCS\u2014and build workflows around it. As requirements evolve, you need faster OTPs, richer engagement, higher reliability, and smarter cost controls. That\u2019s when multi-channel integrations and DIY fallback logic start to add &#8230;<\/p>\n","protected":false},"author":4,"featured_media":4245,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":true,"footnotes":""},"categories":[15],"tags":[299,163,214],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v21.4 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Migrating from SMS, WhatsApp, or RCS APIs to the EnableX - Insights about video API, SMS API; WhatsApp for Business API<\/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:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Migrating from SMS, WhatsApp, or RCS APIs to the EnableX - Insights about video API, SMS API; WhatsApp for Business API\" \/>\n<meta property=\"og:description\" content=\"Move from channel-based messaging to intelligent messaging orchestration\u2014start single-channel today, add fallback tomorrow, and scale without rewrites. Most teams begin with a single channel\u2014typically&nbsp;SMS,&nbsp;WhatsApp, or&nbsp;RCS\u2014and build workflows around it. As requirements evolve, you need faster OTPs, richer engagement, higher reliability, and smarter cost controls. That\u2019s when multi-channel integrations and DIY fallback logic start to add ...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/\" \/>\n<meta property=\"og:site_name\" content=\"Insights about video API, SMS API; WhatsApp for Business API\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-16T04:41:26+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-27T04:42:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.enablex.io\/insights\/wp-content\/uploads\/2026\/03\/Migrating-from-SMS-WhatsApp-or-RCS-APIs-to-the-EnableX-.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1148\" \/>\n\t<meta property=\"og:image:height\" content=\"397\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Team EnableX\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@EnablexIo\" \/>\n<meta name=\"twitter:site\" content=\"@enablexio\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Team EnableX\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Migrating from SMS, WhatsApp, or RCS APIs to the EnableX - Insights about video API, SMS API; WhatsApp for Business API","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:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/","og_locale":"en_US","og_type":"article","og_title":"Migrating from SMS, WhatsApp, or RCS APIs to the EnableX - Insights about video API, SMS API; WhatsApp for Business API","og_description":"Move from channel-based messaging to intelligent messaging orchestration\u2014start single-channel today, add fallback tomorrow, and scale without rewrites. Most teams begin with a single channel\u2014typically&nbsp;SMS,&nbsp;WhatsApp, or&nbsp;RCS\u2014and build workflows around it. As requirements evolve, you need faster OTPs, richer engagement, higher reliability, and smarter cost controls. That\u2019s when multi-channel integrations and DIY fallback logic start to add ...","og_url":"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/","og_site_name":"Insights about video API, SMS API; WhatsApp for Business API","article_published_time":"2026-03-16T04:41:26+00:00","article_modified_time":"2026-04-27T04:42:02+00:00","og_image":[{"width":1148,"height":397,"url":"https:\/\/www.enablex.io\/insights\/wp-content\/uploads\/2026\/03\/Migrating-from-SMS-WhatsApp-or-RCS-APIs-to-the-EnableX-.png","type":"image\/png"}],"author":"Team EnableX","twitter_card":"summary_large_image","twitter_creator":"@EnablexIo","twitter_site":"@enablexio","twitter_misc":{"Written by":"Team EnableX","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/#article","isPartOf":{"@id":"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/"},"author":{"name":"Team EnableX","@id":"https:\/\/www.enablex.io\/insights\/#\/schema\/person\/5218faaa806cca26a32cbd2c50b61de7"},"headline":"Migrating from SMS, WhatsApp, or RCS APIs to the EnableX","datePublished":"2026-03-16T04:41:26+00:00","dateModified":"2026-04-27T04:42:02+00:00","mainEntityOfPage":{"@id":"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/"},"wordCount":479,"publisher":{"@id":"https:\/\/www.enablex.io\/insights\/#organization"},"keywords":["rcs api","sms api","WhatsApp API"],"articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/","url":"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/","name":"Migrating from SMS, WhatsApp, or RCS APIs to the EnableX - Insights about video API, SMS API; WhatsApp for Business API","isPartOf":{"@id":"https:\/\/www.enablex.io\/insights\/#website"},"datePublished":"2026-03-16T04:41:26+00:00","dateModified":"2026-04-27T04:42:02+00:00","breadcrumb":{"@id":"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.enablex.io\/insights\/migrating-from-sms-whatsapp-or-rcs-apis-to-the-enablex\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.enablex.io\/insights\/"},{"@type":"ListItem","position":2,"name":"Migrating from SMS, WhatsApp, or RCS APIs to the EnableX"}]},{"@type":"WebSite","@id":"https:\/\/www.enablex.io\/insights\/#website","url":"https:\/\/www.enablex.io\/insights\/","name":"Enablex","description":"","publisher":{"@id":"https:\/\/www.enablex.io\/insights\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.enablex.io\/insights\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.enablex.io\/insights\/#organization","name":"Enablex","url":"https:\/\/www.enablex.io\/insights\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.enablex.io\/insights\/#\/schema\/logo\/image\/","url":"https:\/\/www.enablex.io\/insights\/wp-content\/uploads\/2023\/05\/EnableX-Logo-01.png","contentUrl":"https:\/\/www.enablex.io\/insights\/wp-content\/uploads\/2023\/05\/EnableX-Logo-01.png","width":17382,"height":3567,"caption":"Enablex"},"image":{"@id":"https:\/\/www.enablex.io\/insights\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/twitter.com\/enablexio","https:\/\/www.linkedin.com\/company\/vcloudx"]},{"@type":"Person","@id":"https:\/\/www.enablex.io\/insights\/#\/schema\/person\/5218faaa806cca26a32cbd2c50b61de7","name":"Team EnableX","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.enablex.io\/insights\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/57ce8b82fce67dbcffa404aa73926a28?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/57ce8b82fce67dbcffa404aa73926a28?s=96&d=mm&r=g","caption":"Team EnableX"},"description":"EnableX is a leading global provider of omnichannel Customer Engagement Cloud solutions, dedicated to empowering businesses to create engaging experiences at every stage of the customer journey. Our platform, built on a robust cloud infrastructure, seamlessly integrates AI, data, and real-time communications\u2014including text, voice, and video\u2014ensuring intelligent, personalised, and seamless interactions across all channels. Founded in 2017 and headquartered in Singapore, EnableX has quickly established itself as a pivotal force in transforming customer engagement. Guided by our motto, \"Perfecting Every Engagement,\" we serve large global telecoms and enterprises, continuously expanding our reach and refining our offerings to stay at the forefront of innovation in customer engagement.","sameAs":["https:\/\/twitter.com\/EnablexIo","https:\/\/www.youtube.com\/@enablex"],"url":"https:\/\/www.enablex.io\/insights\/author\/enablex\/"}]}},"_links":{"self":[{"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/posts\/4218"}],"collection":[{"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/comments?post=4218"}],"version-history":[{"count":0,"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/posts\/4218\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/media\/4245"}],"wp:attachment":[{"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/media?parent=4218"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/categories?post=4218"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.enablex.io\/insights\/wp-json\/wp\/v2\/tags?post=4218"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}