{"id":582,"date":"2026-01-28T21:02:21","date_gmt":"2026-01-28T15:32:21","guid":{"rendered":"https:\/\/kwala.network\/blogs\/?p=582"},"modified":"2026-04-08T15:07:57","modified_gmt":"2026-04-08T09:37:57","slug":"how-to-build-multi-chain-dapps-with-kwala-no-server-management-required","status":"publish","type":"post","link":"https:\/\/www.kwala.network\/blogs\/how-to-build-multi-chain-dapps-with-kwala-no-server-management-required\/","title":{"rendered":"How to Build Multi-Chain\u00a0dApps\u00a0with\u00a0Kwala: No Server Management Required\u00a0"},"content":{"rendered":"\n<p>Every Web3 developer knows this pattern: you launch a contract, test it, feel good about it\u2026 and then the backend work begins. Suddenly&nbsp;you\u2019re&nbsp;maintaining&nbsp;RPC listeners,&nbsp;cron&nbsp;jobs,&nbsp;relayers, indexers, retry queues; all before you even build your actual product logic.&nbsp;&nbsp;<\/p>\n\n\n\n<p>Multiply this across chains, and backend complexity becomes the reason simple ideas take weeks to ship.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">All the backend work you usually build?&nbsp;Kwala&nbsp;removes it.&nbsp;&nbsp;<\/h2>\n\n\n\n<p>Instead of writing and\u00a0maintaining\u00a0infrastructure, you express your backend as workflows that react to\u00a0<strong><a href=\"https:\/\/kwala.network\/docs\/workflow-builder\/monitor-workflow#monitor-workflow\">monitoring\u00a0on-chain events<\/a><\/strong>. You get to\u00a0build\u00a0backendless\u00a0dApps\u00a0that scale across chains using pure logic, not servers.\u00a0<\/p>\n\n\n\n<p>Below is a leaner explanation of why\u00a0this matters, and a more detailed breakdown of how to do it in\u00a0<strong><a href=\"https:\/\/kwala.network\/\">Kwala.<\/a><\/strong>\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why multi-chain development breaks teams (and how automation changes it)&nbsp;<\/h2>\n\n\n\n<p>Most teams&nbsp;don\u2019t&nbsp;struggle with smart contracts; they struggle with the invisible machinery around them. A multi-chain app&nbsp;requires:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Knowing when something happened on Chain A&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reacting on Chain B&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reconciling data across them&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keeping this machinery reliable&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>This is why<a href=\"https:\/\/kwala.network\/docs\/concepts\/workflow-execution#workflow-execution\">\u00a0<strong>multi-chain workflow automation<\/strong><\/a>\u00a0is critical.\u00a0Kwala\u00a0gives you a workflow engine that streams blocks, extracts events, and executes your logic; without you ever writing backend code.\u00a0<\/p>\n\n\n\n<p>Templates help too. With curated&nbsp;<strong><a href=\"https:\/\/kwala.network\/docs\">Web3 backend templates<\/a><\/strong>, you start closer to production instead of rebuilding orchestration patterns every time.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A Better Way to Handle Multi-Chain Backend Complexity&nbsp;<\/h2>\n\n\n\n<p><\/p>\n\n\n\n<p><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1012\" height=\"533\" src=\"https:\/\/kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/1-31.jpg\" alt=\"\" class=\"wp-image-586\" srcset=\"https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/1-31.jpg 1012w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/1-31-300x158.jpg 300w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/1-31-768x404.jpg 768w\" sizes=\"auto, (max-width: 1012px) 100vw, 1012px\" \/><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p><\/p>\n\n\n\n<p>When a&nbsp;dApp&nbsp;operates across multiple chains, its backend must track events on each network, coordinate actions between them, and keep everything aligned.&nbsp;That\u2019s&nbsp;where most of the complexity, and most delays come from. Traditional setups require separate listeners,&nbsp;relayers, and custom logic for every chain involved.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Kwala&nbsp;changes this model by turning those on-chain events into&nbsp;automated workflows.&nbsp;<\/h3>\n\n\n\n<p>Instead of wiring infrastructure to react to each chain separately, you define the logic once, and<a href=\"https:\/\/kwala.network\/\">&nbsp;Kwala&nbsp;<\/a>executes it wherever it needs to run. This makes cross-chain&nbsp;behavior&nbsp;consistent, reliable, and far easier to scale.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to build and deploy a multi-chain&nbsp;dApp&nbsp;using&nbsp;Kwala&nbsp;<\/h2>\n\n\n\n<p><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1012\" height=\"533\" src=\"https:\/\/kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/2-21.jpg\" alt=\"\" class=\"wp-image-587\" srcset=\"https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/2-21.jpg 1012w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/2-21-300x158.jpg 300w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/2-21-768x404.jpg 768w\" sizes=\"auto, (max-width: 1012px) 100vw, 1012px\" \/><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p><\/p>\n\n\n\n<p>The following steps outline the core workflow developers rely on when building<strong><a href=\"https:\/\/kwala.network\/docs\"> multi-chain applications with\u00a0Kwala.\u00a0<\/a><\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Define your event-to-action logic (your&nbsp;dApp\u2019s&nbsp;backbone)&nbsp;<\/h3>\n\n\n\n<p>Start with clarity:&nbsp;determine&nbsp;which on-chain events drive your logic and what actions they should&nbsp;initiate.&nbsp;<\/p>\n\n\n\n<p><strong>For example:&nbsp;<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cWhen a user stakes on Base \u2192 mint\/update an NFT on Polygon.\u201d&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cWhen a DAO proposal passes \u2192 post updates to an off-chain API.\u201d&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>This mapping is important because&nbsp;Kwala&nbsp;is built around&nbsp;<strong><a href=\"https:\/\/kwala.network\/docs\/workflow-builder\/monitor-workflow\">monitoring on-chain events<\/a><\/strong>. Your entire backend is essentially:&nbsp;<\/p>\n\n\n\n<p><strong>Event \u2192 Trigger \u2192 Action<\/strong>&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Set up your&nbsp;Kwala&nbsp;workspace&nbsp;<\/h3>\n\n\n\n<p>Once inside&nbsp;Kwala:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Connect your MetaMask wallet.&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Access your workspace where all workflows live.&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Top up credits if&nbsp;required&nbsp;(Kwala&nbsp;charges only when workflows execute).&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>This replaces servers, schedulers,&nbsp;relayers, and indexers: everything starts here.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Create your workflow and choose the trigger&nbsp;<\/h3>\n\n\n\n<p>This is where backend complexity collapses into a few clean decisions:&nbsp;<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>Click&nbsp;<strong>New Workflow<\/strong>.&nbsp;<\/li>\n<\/ol>\n\n\n\n<ol start=\"2\" class=\"wp-block-list\">\n<li>Give it a name (e.g.,&nbsp;RewardsIntentListener).&nbsp;<\/li>\n<\/ol>\n\n\n\n<ol start=\"3\" class=\"wp-block-list\">\n<li>Choose your trigger type:&nbsp;<\/li>\n<\/ol>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Immediate&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Time Stamp&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Event&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Oracle Price&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Block number&nbsp;<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"602\" height=\"340\" src=\"https:\/\/kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/image-28.png\" alt=\"\" class=\"wp-image-583\" srcset=\"https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/image-28.png 602w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/image-28-300x169.png 300w\" sizes=\"auto, (max-width: 602px) 100vw, 602px\" \/><\/figure>\n\n\n\n<p><strong>Note<\/strong>: For the first iteration of your workflow, use an&nbsp;<strong>on-chain event<\/strong>&nbsp;as the trigger.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4. Select your Trigger Source Contact and Chain ID&nbsp;<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Paste the contract address&nbsp;<\/li>\n\n\n\n<li>Kwala&nbsp;automatically retrieves ABIs from verified contracts, with&nbsp;an option&nbsp;for developers to supply the contract\u2019s source code themselves.&nbsp;<\/li>\n\n\n\n<li>Choose the specific event to listen for&nbsp;<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"602\" height=\"340\" src=\"https:\/\/kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/image-29.png\" alt=\"\" class=\"wp-image-584\" srcset=\"https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/image-29.png 602w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/image-29-300x169.png 300w\" sizes=\"auto, (max-width: 602px) 100vw, 602px\" \/><\/figure>\n\n\n\n<p>Behind the scenes, Kwala begins handling your block streaming, event extraction, validation, and indexing.&nbsp;<\/p>\n\n\n\n<p>You don\u2019t write any of this.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Configure dynamic inputs&nbsp;<\/h3>\n\n\n\n<p>Most multi-chain dApps rely on event parameters to execute actions.&nbsp;<\/p>\n\n\n\n<p>For example:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Wallet address&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Token ID&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Metadata&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Amount&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>Kwala supports this through parameter extraction using either:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ABI-driven parameter extraction,&nbsp;or&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Lightweight reg-ex that parses event logs&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>Once mapped, these dynamic values flow into your next chain\u2019s contract, your API, or your off-chain system. This step replaces the parsing\/indexing code developers normally spend days writing.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Add your actions (cross-chain or off-chain)&nbsp;<\/h3>\n\n\n\n<p>This is where you define what should happen next.&nbsp;<\/p>\n\n\n\n<p>A workflow can include actions such as:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Call a smart contract function&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Trigger a contract on another chain&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hit a REST API&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Send notifications&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Fan-out multiple actions in parallel&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>Often, a Chain 1 event routes straight into a Chain 2 action within the same workflow.&nbsp;<\/p>\n\n\n\n<p>However, for&nbsp;multi-chain apps,&nbsp;a&nbsp;commonly seen&nbsp;pattern is:&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Workflow A (Chain 1 event) \u2192 Workflow B (Chain 2 action)&nbsp;<\/h2>\n\n\n\n<p>Regardless of how&nbsp;it\u2019s&nbsp;triggered, the workflow runs in a familiar sequence:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You define the function you want to call&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Map the dynamic parameters&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Choose sequential or parallel execution&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ensure your contract permit logic allows Kwala to call it&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>This is where&nbsp;<strong><a href=\"https:\/\/kwala.network\/docs\/workflow-builder\/explore-the-playground\">Web3 backend templates<\/a><\/strong>&nbsp;help: you can start from a pattern instead of designing everything yourself.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Validate, deploy, and activate&nbsp;<\/h3>\n\n\n\n<p>This is a 3-phase process that makes your backend&nbsp;<em>real<\/em>:&nbsp;<\/p>\n\n\n\n<p>1.&nbsp;<strong>Save<\/strong>: Kwala validates your YAML logic and runs syntax checks.&nbsp;<\/p>\n\n\n\n<p>2.&nbsp;<strong>Deploy<\/strong>: Kwala registers the workflow in the network.&nbsp;<\/p>\n\n\n\n<p>3.&nbsp;<strong>Activate<\/strong>: Your workflow gets live.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"602\" height=\"286\" src=\"https:\/\/kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/image-30.png\" alt=\"\" class=\"wp-image-585\" srcset=\"https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/image-30.png 602w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/01\/image-30-300x143.png 300w\" sizes=\"auto, (max-width: 602px) 100vw, 602px\" \/><\/figure>\n\n\n\n<p>Kwala begins&nbsp;<strong>monitoring on-chain events<\/strong>&nbsp;and executing your actions the moment triggers occur.&nbsp;<\/p>\n\n\n\n<p>You have officially deployed a backend, without building a backend.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 7: Extend to more chains or use cases&nbsp;<\/h3>\n\n\n\n<p>This is the beauty of the approach:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>To add another chain \u2192 duplicate the workflow, change the chain ID&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>To add another use case \u2192 start from an existing template&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>To add off-chain logic \u2192 plug into any REST endpoint&nbsp;<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Why this model works long-term&nbsp;<\/h2>\n\n\n\n<p>By converting blockchain events into programmable workflows, you get:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Faster go-to-market&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Lower backend costs&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cleaner architecture&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Easier enterprise integration&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>No dependency on centralized RPC providers&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Peace of mind around reliability&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>More importantly: you spend time building features, not plumbing.&nbsp;<\/p>\n\n\n\n<p>That\u2019s the promise of\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/blockchain-events-explained-how-triggers-automate-on-chain-actions\/\">multi-chain workflow automation<\/a><\/strong>: simple, declarative backend logic that works across chains without servers.\u00a0\u00a0<\/p>\n\n\n\n<p>With\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/multi-chain-dapp-orchestration-how-kwala-stacks-against-other-web3-backends\/\">Web3 backend templates<\/a><\/strong>\u00a0and continuous\u00a0monitoring on-chain events,\u00a0<a href=\"https:\/\/kwala.network\/\" target=\"_blank\" rel=\"noreferrer noopener\">Kwala<\/a>\u00a0supports this approach end to end, enabling developers to ship multi-chain dApps with far less effort.\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQs on multi-chain workflow automation&nbsp;<\/h2>\n\n\n\n<h2 class=\"wp-block-heading\">1. Can enterprises migrate existing automation to Kwala?&nbsp;<\/h2>\n\n\n\n<p>Yes, existing backend tasks can be recreated as workflows, mapped to contract events, or connected through APIs, reducing infrastructure while maintaining operational consistency.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2.  What types of smart contracts work best with&nbsp;Kwala?&nbsp;<\/h2>\n\n\n\n<p>Any contract emitting events works seamlessly.&nbsp;As long as&nbsp;event structures are clear,&nbsp;Kwala&nbsp;can extract values and trigger workflows for DeFi, NFTs, gaming, or governance.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3. Do I need separate servers for each chain?&nbsp;<\/h2>\n\n\n\n<p>No, <strong><a href=\"https:\/\/kwala.network\/docs\/support\/glossary#orchestrator\">Kwala\u2019s orchestration<\/a><\/strong> layer handles cross-chain triggers and actions without requiring individual backend environments.\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every Web3 developer knows this pattern: you launch a contract, test it, feel good about it\u2026 and then the backend work begins. Suddenly&nbsp;you\u2019re&nbsp;maintaining&nbsp;RPC listeners,&nbsp;cron&nbsp;jobs,&nbsp;relayers, indexers, retry queues; all before you even build your actual product logic.&nbsp;&nbsp; Multiply this across chains, and backend complexity becomes the reason simple ideas take weeks to ship.&nbsp; All the backend [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":602,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"inline_featured_image":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[6],"tags":[],"class_list":["post-582","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blockchain"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/posts\/582","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/comments?post=582"}],"version-history":[{"count":5,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/posts\/582\/revisions"}],"predecessor-version":[{"id":913,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/posts\/582\/revisions\/913"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/media\/602"}],"wp:attachment":[{"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/media?parent=582"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/categories?post=582"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/tags?post=582"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}