{"id":644,"date":"2026-02-04T11:06:55","date_gmt":"2026-02-04T05:36:55","guid":{"rendered":"https:\/\/kwala.network\/blogs\/?p=644"},"modified":"2026-02-09T18:42:39","modified_gmt":"2026-02-09T13:12:39","slug":"from-zero-to-production-blockchain-workflow-engines-with-kwala","status":"publish","type":"post","link":"https:\/\/www.kwala.network\/blogs\/from-zero-to-production-blockchain-workflow-engines-with-kwala\/","title":{"rendered":"From Zero to Production: Blockchain Workflow Engines with\u00a0kwala\u00a0"},"content":{"rendered":"\n<p>Shipping a blockchain product feels exciting at first. A few smart contracts go\u00a0live,\u00a0some scripts listen for events, and everything seems fine. Then usage grows. Events get missed, retries fail silently, and cross-chain logic starts behaving unpredictably.\u00a0<\/p>\n\n\n\n<p><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"960\" height=\"540\" src=\"https:\/\/kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/publication20231006071009.jpg\" alt=\"\" class=\"wp-image-648\" srcset=\"https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/publication20231006071009.jpg 960w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/publication20231006071009-300x169.jpg 300w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/publication20231006071009-768x432.jpg 768w\" sizes=\"auto, (max-width: 960px) 100vw, 960px\" \/><\/figure>\n\n\n\n<p><a href=\"https:\/\/www.thinkers360.com\/tl\/blog\/members\/about-blockchain\" target=\"_blank\" rel=\"noreferrer noopener\">Source<\/a>&nbsp;<\/p>\n\n\n\n<p>This is exactly where a\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/kwalas-guide-to-serverless-blockchain-infrastructure-best-practices-and-smart-start\/\">blockchain workflow engine<\/a><\/strong>\u00a0becomes necessary. Many teams move forward without a proper\u00a0<strong>workflow engine for blockchain dev<\/strong>, relying on scattered automation that works only until real volume and edge cases show up.\u00a0<\/p>\n\n\n\n<p>Kwala\u00a0acts as a\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/from-manual-to-automated-web3-workflows-how-kwala-simplifies-blockchain-operations-for-you\/\">backend as a service for Web3<\/a><\/strong>, taking care of orchestration, execution, and recovery behind the scenes.\u00a0\u00a0<\/p>\n\n\n\n<p>In this blog,&nbsp;we\u2019ll&nbsp;show you how&nbsp;Kwala&nbsp;helps teams move from fragile setups to production-ready&nbsp;workflows, and&nbsp;why having the right workflow engine matters before things start breaking at scale.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What a blockchain workflow engine&nbsp;actually is&nbsp;<\/h2>\n\n\n\n<p>A\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/kwalas-guide-to-serverless-blockchain-infrastructure-best-practices-and-smart-start\/\">blockchain workflow engine<\/a><\/strong>\u00a0is the system that keeps everything moving in the right order once your product goes live. It coordinates actions across smart contracts, different chains, APIs, and off-chain\u00a0logic\u00a0so nothing runs in isolation.\u00a0<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1699\" height=\"992\" src=\"https:\/\/kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/Blockchain-Process.jpg\" alt=\"\" class=\"wp-image-649\" srcset=\"https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/Blockchain-Process.jpg 1699w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/Blockchain-Process-300x175.jpg 300w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/Blockchain-Process-1024x598.jpg 1024w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/Blockchain-Process-768x448.jpg 768w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/Blockchain-Process-1536x897.jpg 1536w\" sizes=\"auto, (max-width: 1699px) 100vw, 1699px\" \/><\/figure>\n\n\n\n<p><a href=\"https:\/\/ilwllc.com\/blockchain-2\/\" target=\"_blank\" rel=\"noreferrer noopener\">Source<\/a>&nbsp;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Here\u2019s\u00a0what a\u00a0workflow engine for blockchain dev\u00a0actually does:\u00a0<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Listens to triggers such as on-chain events, off-chain signals, or time-based conditions across networks.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Decides what should happen next using defined logic, rules, retries, and execution order.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Executes actions like smart contract calls, data writes, API requests, or notifications without manual intervention.\u00a0<\/li>\n<\/ul>\n\n\n\n<p>A simple way\u00a0to picture this is through an analogy. Smart contracts are\u00a0instruments. A\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/kwalas-guide-to-serverless-blockchain-infrastructure-best-practices-and-smart-start\/\">blockchain workflow engine<\/a><\/strong>\u00a0is the conductor, ensuring every part plays\u00a0in sync\u00a0at the right time without breaking the flow.\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why most teams fail with manual blockchain workflows&nbsp;<\/h2>\n\n\n\n<p>Now, consider implementing a&nbsp;<strong>blockchain workflow engine<\/strong>&nbsp;in practice. On paper, everything sounds straightforward.&nbsp;In reality, building&nbsp;workflows manually feels fine until you realize that every single step&nbsp;has to&nbsp;be handled by&nbsp;you.&nbsp;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Here\u2019s why manual approaches break down for most teams building a\u00a0workflow engine for blockchain dev:<\/strong>\u00a0<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Event handling is fragile because custom listeners miss events, duplicate triggers, or fail silently during network congestion.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Retry logic is usually an afterthought, leading to stuck workflows when transactions fail or gas spikes unexpectedly.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>State management becomes messy since scripts rarely track what ran, what failed, and what needs to resume.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cross-chain workflows\u00a0are hard to coordinate when each network needs its own logic, RPC setup, and error handling.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Debugging turns painful because logs are\u00a0scattered\u00a0and failures are difficult to trace end-to-end.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Scaling exposes cracks fast, especially when volume increases, and manual scripts cannot keep up.\u00a0<\/li>\n<\/ul>\n\n\n\n<p>This is where a proper\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/how-to-automate-web3-workflows-without-writing-backend-code-using-kwala\/\">backend as a service for Web3<\/a><\/strong>\u00a0starts to matter. Without it, teams spend more time fixing automation than building real product features.\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Enter\u00a0Kwala\u2019s\u00a0BaaS model\u00a0<\/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\/02\/1-41.jpg\" alt=\"\" class=\"wp-image-650\" srcset=\"https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/1-41.jpg 1012w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/1-41-300x158.jpg 300w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/1-41-768x404.jpg 768w\" sizes=\"auto, (max-width: 1012px) 100vw, 1012px\" \/><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p><a href=\"https:\/\/kwala.network\/\"><strong>kwala<\/strong>\u00a0<\/a>is a stateless, declarative, event-driven automation layer designed to make blockchains usable in real-world applications. It sits above chains and turns raw blockchain activity into structured, reliable workflows without requiring teams to run backend infrastructure.\u00a0<\/p>\n\n\n\n<p>Kwala\u2019s\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/how-to-automate-web3-workflows-without-writing-backend-code-using-kwala\/\">backend as a service for\u00a0Web3\u00a0(BaaS)<\/a><\/strong>\u00a0model is built to remove the heavy lifting that usually comes with a\u00a0<strong>blockchain workflow engine<\/strong>. Instead of setting up event listeners, worker queues, retry logic, and cross-chain coordination, teams define workflows while\u00a0Kwala\u00a0handles execution.\u00a0<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Here\u2019s\u00a0what the BaaS model delivers for a\u00a0workflow engine for blockchain dev:\u00a0<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Event-driven automation\u00a0that reacts to on-chain and off-chain triggers in real time.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Managed workflow execution without servers, polling systems, or custom runners.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.youtube.com\/watch?v=RgXNcyE-BKY&amp;t=2s\" target=\"_blank\" rel=\"noreferrer noopener\">Cross-chain orchestration<\/a>\u00a0through a single, unified workflow definition.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Built-in retries and recovery to handle failures and network issues safely.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Web2 and Web3 integrations using APIs, webhooks, and external services.\u00a0<\/li>\n<\/ul>\n\n\n\n<p>The result is a production-ready workflow engine where developers focus on logic, not backend complexity.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Beginner setup \u2013 your first workflow on&nbsp;Kwala&nbsp;<\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1874\" height=\"839\" src=\"https:\/\/kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/website.png\" alt=\"\" class=\"wp-image-651\" srcset=\"https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/website.png 1874w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/website-300x134.png 300w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/website-1024x458.png 1024w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/website-768x344.png 768w, https:\/\/www.kwala.network\/blogs\/wp-content\/uploads\/2026\/02\/website-1536x688.png 1536w\" sizes=\"auto, (max-width: 1874px) 100vw, 1874px\" \/><\/figure>\n\n\n\n<p>Getting started with\u00a0<strong><a href=\"https:\/\/kwala.network\/\">Kwala<\/a><\/strong>\u00a0is about defining intent without managing infrastructure. You focus on what should happen when an event occurs, while\u00a0Kwala\u00a0handles execution across chains and external\u00a0systems.\u00a0<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Here&#8217;s&nbsp;how a first workflow usually comes together:&nbsp;<\/h4>\n\n\n\n<h4 class=\"wp-block-heading\">1. Define the trigger&nbsp;<\/h4>\n\n\n\n<p>Choose what the workflow&nbsp;listens&nbsp;to. Options include a smart contract event, wallet activity,&nbsp;or a time-based trigger. Clear trigger definitions keep workflows&nbsp;accurate&nbsp;and help control execution costs.&nbsp;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">2. Select the action&nbsp;<\/h4>\n\n\n\n<p>Decide what runs when the trigger fires. Actions can include smart contract calls, token transfers, cross-chain operations, or API requests to external services.&nbsp;<br>&nbsp;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">3. Set the execution policy&nbsp;<\/h4>\n\n\n\n<p>Configure how actions run under real conditions. Retry behavior, execution limits, and safety rules help workflows handle network delays and temporary failures smoothly.&nbsp;<br>&nbsp;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">4. Deploy and monitor&nbsp;<\/h4>\n\n\n\n<p>Save and deploy the&nbsp;workflow, and&nbsp;let&nbsp;Kwala&nbsp;listen for incoming triggers. Execution logs and history provide visibility into what runs and confirm expected outcomes.&nbsp;<\/p>\n\n\n\n<p>The setup stays simple and accessible, making it easy for mid-level developers to ship reliable blockchain automation without backend overhead.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Intermediate setup &#8211; multi-step and event-driven workflows&nbsp;<\/h2>\n\n\n\n<p>Once a basic workflow is live, most teams move toward multi-step automation. At this stage, a&nbsp;<strong>blockchain workflow engine<\/strong>&nbsp;helps coordinate several actions in a defined order, driven entirely by events rather than manual scripts.&nbsp;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Here\u2019s how intermediate workflows are typically structured using a\u00a0workflow engine for blockchain dev:\u00a0<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Chain multiple actions together:<\/strong>\u00a0One trigger can run several actions in sequence, such as a contract call followed by a cross-chain step and an API update. Clear sequencing keeps execution predictable and easy to follow.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Rely on\u00a0event-driven execution:<\/strong>\u00a0Each step runs only when\u00a0its\u00a0trigger\u00a0fires. Event-driven workflows reduce unnecessary processing and ensure actions respond directly to real blockchain activity.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Handle failures with execution policies:<\/strong>\u00a0Retries, limits, and safe execution rules help workflows recover from temporary network issues. These controls prevent partial execution from breaking the overall flow.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Track workflow state across steps:<\/strong>\u00a0Execution history shows which steps ran successfully and where failures occurred. State visibility makes debugging faster as workflows grow in complexity.\u00a0<\/li>\n<\/ul>\n\n\n\n<p>At this level,&nbsp;Kwala&nbsp;acts as a&nbsp;<strong>backend as a service for Web3<\/strong>, coordinating multi-step logic without requiring custom backend systems or manual orchestration.&nbsp;<\/p>\n\n\n\n<p>Advanced logic \u2013 conditional paths and dynamic workflows&nbsp;<\/p>\n\n\n\n<p>As workflows mature, logic needs to adapt to real-world variability. A production-grade&nbsp;<strong>blockchain workflow engine<\/strong>&nbsp;supports dynamic behavior without hardcoding every scenario or redeploying systems.&nbsp;<\/p>\n\n\n\n<p>Here\u2019s how advanced logic works with a&nbsp;<strong>workflow engine for blockchain dev<\/strong>&nbsp;like&nbsp;Kwala:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dynamic execution paths:<\/strong>\u00a0Workflow behavior can change based on trigger data, execution outcomes, or external inputs. Actions follow different paths depending on what the workflow receives at runtime.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Parameter-driven workflows:<\/strong>\u00a0Inputs from events or APIs shape how actions execute. One workflow definition can support multiple use cases by adjusting parameters instead of duplicating logic.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Outcome-aware execution:<\/strong>\u00a0Workflows respond to success or failure signals during execution.\u00a0Follow-up actions depend on what\u00a0actually happens, not fixed assumptions.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Resilient design at scale:<\/strong>\u00a0Dynamic workflows reduce brittle logic and limit manual intervention. Automation stays reliable even as volume, chains, or integrations increase.\u00a0<\/li>\n<\/ul>\n\n\n\n<p>Kwala&nbsp;provides a&nbsp;<strong>workflow engine for blockchain dev<\/strong>&nbsp;that supports complex logic while keeping execution predictable, observable, and&nbsp;production-ready.&nbsp;<\/p>\n\n\n\n<p>Building reliable blockchain workflows with&nbsp;Kwala&nbsp;<\/p>\n\n\n\n<p>A reliable\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/kwalas-guide-to-serverless-blockchain-infrastructure-best-practices-and-smart-start\/\">blockchain workflow engine<\/a><\/strong>\u00a0is no longer optional once products move into production. Manual scripts and custom automation struggle to handle real usage, multiple chains, and failure scenarios.\u00a0\u00a0<\/p>\n\n\n\n<p>A purpose-built\u00a0<strong>workflow engine for blockchain dev<\/strong>\u00a0brings structure, visibility, and predictable execution to complex workflows.\u00a0Kwala\u00a0delivers this as a\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/how-to-automate-web3-workflows-without-writing-backend-code-using-kwala\/\">backend as a service for Web3<\/a><\/strong>, removing the need to manage backend infrastructure while keeping workflows flexible and scalable.\u00a0<\/p>\n\n\n\n<p><a href=\"https:\/\/kwala.network\/\" target=\"_blank\" rel=\"noreferrer noopener\">Explore how Kwala helps teams build production-ready blockchain workflows with confidence<\/a>&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQs on blockchain workflow engine&nbsp;<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What is a workflow engine used for?&nbsp;<\/h3>\n\n\n\n<p>A workflow engine is used to coordinate tasks, events, and actions in a defined order. In blockchain systems, a&nbsp;<strong>blockchain workflow engine<\/strong>&nbsp;helps automate contract calls, cross-chain actions, and integrations while keeping execution reliable and traceable.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does ChatGPT use blockchain?&nbsp;<\/h3>\n\n\n\n<p>ChatGPT does not run on blockchain and does not rely on blockchain networks for operation. It works on centralized infrastructure, unlike a\u00a0<strong><a href=\"https:\/\/kwala.network\/blogs\/kwalas-guide-to-serverless-blockchain-infrastructure-best-practices-and-smart-start\/\">workflow engine for blockchain dev<\/a><\/strong>, which directly interacts with on-chain events and execution.\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What are the 5 steps of&nbsp;workflow?&nbsp;<\/h2>\n\n\n\n<p>A typical workflow follows these steps:&nbsp;<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>Trigger initiation\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"2\" class=\"wp-block-list\">\n<li>Action execution\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"3\" class=\"wp-block-list\">\n<li>State tracking\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"4\" class=\"wp-block-list\">\n<li>Error handling\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"5\" class=\"wp-block-list\">\n<li>Completion or follow-up\u00a0<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Shipping a blockchain product feels exciting at first. A few smart contracts go\u00a0live,\u00a0some scripts listen for events, and everything seems fine. Then usage grows. Events get missed, retries fail silently, and cross-chain logic starts behaving unpredictably.\u00a0 Source&nbsp; This is exactly where a\u00a0blockchain workflow engine\u00a0becomes necessary. Many teams move forward without a proper\u00a0workflow engine for blockchain [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":652,"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":[4],"tags":[],"class_list":["post-644","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-product-deep-dives"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/posts\/644","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=644"}],"version-history":[{"count":1,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/posts\/644\/revisions"}],"predecessor-version":[{"id":653,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/posts\/644\/revisions\/653"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/media\/652"}],"wp:attachment":[{"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/media?parent=644"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/categories?post=644"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kwala.network\/blogs\/wp-json\/wp\/v2\/tags?post=644"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}