{"id":56972,"date":"2026-10-12T14:29:27","date_gmt":"2026-10-12T04:29:27","guid":{"rendered":"https:\/\/www.cloudproinc.com.au\/?p=56972"},"modified":"2026-10-12T14:29:27","modified_gmt":"2026-10-12T04:29:27","slug":"github-copilot-sdk-architecture-explained","status":"publish","type":"post","link":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/12\/github-copilot-sdk-architecture-explained\/","title":{"rendered":"GitHub Copilot SDK Architecture Explained"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">In this blog post <strong>GitHub Copilot SDK Architecture Explained for Teams and Builders<\/strong> we will walk through the moving parts that make Copilot integrations work, and how to design them so they stay secure, maintainable, and useful for real teams.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p class=\"wp-block-paragraph\">At a high level, GitHub Copilot is not \u201cone model in your editor.\u201d It\u2019s a <strong>workflow<\/strong>: your IDE or GitHub UI collects context, the Copilot service selects an interaction mode (chat, inline, or agentic execution), and then it may call <strong>tools<\/strong> (like GitHub or Playwright) to fetch data or take actions before producing an answer. Newer Copilot capabilities increasingly rely on a tools layer built around <strong>Model Context Protocol (MCP)<\/strong>, which standardises how an assistant discovers and uses external tools. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019ve heard \u201cCopilot SDK\u201d mentioned, it typically refers to this <strong>integration surface<\/strong>: the ways you extend Copilot with your organisation\u2019s systems (tickets, runbooks, deployments, internal docs) using a tool protocol (MCP) or IDE-specific extension points. GitHub has also been explicit that <strong>GitHub App-based Copilot Extensions are being sunset<\/strong>, while MCP and VS Code extensions remain supported\u2014so it\u2019s worth designing with that direction in mind. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-what-problem-the-copilot-architecture-is-solving\">What problem the Copilot architecture is solving<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Most AI assistants fail in the same two places:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Context is missing<\/strong>: the model can\u2019t see your repo, coding standards, or the conversation history that explains why this change matters.<\/li>\n\n\n\n<li><strong>Actions are unsafe<\/strong>: the assistant can\u2019t safely query internal systems or run repeatable operations with least-privilege access.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Copilot\u2019s architecture tackles both by separating concerns:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Clients<\/strong> (VS Code, JetBrains, GitHub web\/mobile, CLI) gather context and present UX.<\/li>\n\n\n\n<li><strong>Copilot service<\/strong> handles model orchestration and prompt construction.<\/li>\n\n\n\n<li><strong>Tools layer<\/strong> (increasingly MCP-based) provides well-defined capabilities the assistant can call.<\/li>\n\n\n\n<li><strong>Policy and admin controls<\/strong> determine what\u2019s allowed for users and organisations.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-the-main-technology-behind-modern-copilot-integrations-mcp\">The main technology behind modern Copilot integrations: MCP<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Model Context Protocol (MCP)<\/strong> is an open standard that defines how applications share context with LLMs and how assistants can call external tools. In Copilot, MCP servers expose <strong>tools<\/strong> that the assistant can invoke. For Copilot Chat, MCP can also expose <strong>resources<\/strong> that users add to chat context (depending on client support). <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One practical takeaway: instead of baking \u201cJira integration\u201d or \u201cServiceNow integration\u201d into a one-off extension, you can expose a stable set of tools via an MCP server and reuse them across multiple assistants and hosts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-mcp-in-copilot-coding-agent-vs-copilot-chat\">MCP in Copilot coding agent vs Copilot Chat<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">GitHub\u2019s documentation draws an important line:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Copilot coding agent<\/strong> currently supports <strong>tools<\/strong> from MCP servers (and notably does <em>not<\/em> support MCP resources\/prompts in the same way). <\/li>\n\n\n\n<li>There are also current constraints around <strong>remote MCP servers using OAuth<\/strong> for coding agent scenarios. <\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For architects, this means you should design MCP tools to be self-contained and automation-friendly, especially if you want agentic execution.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-copilot-architecture-the-layers-you-should-design-for\">Copilot architecture: the layers you should design for<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-1-the-host-client-layer\">1) The host client layer<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is where the developer interacts with Copilot:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>VS Code \/ JetBrains IDE chat panels and inline chat<\/li>\n\n\n\n<li>GitHub web and mobile experiences<\/li>\n\n\n\n<li>Terminal workflows (Copilot in CLI is evolving quickly, including a move away from older CLI extension approaches) (github.blog)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Clients differ in what context they can collect and what actions they can present cleanly (buttons, diffs, approvals). You should assume variability and keep your integration logic in the tool layer, not the UI.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-2-context-assembly-and-grounding\">2) Context assembly and grounding<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Copilot performs best when it has:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Repository context<\/strong> (files, symbols, errors)<\/li>\n\n\n\n<li><strong>Conversation context<\/strong> (what you tried, what failed, what matters)<\/li>\n\n\n\n<li><strong>Organisational context<\/strong> (coding standards, security constraints, platform conventions)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Where possible, encode team standards into:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Clear repo documentation (CONTRIBUTING, architecture notes)<\/li>\n\n\n\n<li>Repeatable tool calls (e.g., \u201cfetch runbook\u201d, \u201ccheck deployment status\u201d)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-3-model-orchestration\">3) Model orchestration<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Copilot can use multiple underlying models, and the available set changes over time. GitHub has been actively evolving model access and agent experiences, including adding additional agent options in public previews and adjusting which models are available. (theverge.com)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Architecturally, this is exactly why a tools-first approach matters: if the model changes, your <strong>tool contracts<\/strong> should remain stable.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-4-the-tools-layer-your-copilot-sdk-sweet-spot\">4) The tools layer (your \u201cCopilot SDK\u201d sweet spot)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Tools are where your organisation adds real leverage. In Copilot\u2019s world, MCP servers are becoming the standard way to provide tools such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Search internal docs<\/li>\n\n\n\n<li>Create or query tickets<\/li>\n\n\n\n<li>Check feature flags<\/li>\n\n\n\n<li>Trigger safe deployment operations<\/li>\n\n\n\n<li>Query CI results and logs<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">GitHub also ships <strong>default MCP servers<\/strong> for some agent experiences, including a GitHub MCP server (repo-scoped, read-only by default) and Playwright for web interactions. <\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-5-policy-permissions-and-auditability\">5) Policy, permissions, and auditability<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For tech leaders, this is the layer that determines whether Copilot is a productivity tool or a risk. Examples of controls include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Organisation policies for whether MCP servers are allowed (and that the policy can be disabled by default depending on plan).<\/li>\n\n\n\n<li>Token scoping: default tokens may be read-only and repo-scoped, with options to broaden access carefully. <\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Design goal: <strong>least privilege by default<\/strong>, and make privileged operations explicit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-a-practical-reference-architecture-for-an-mcp-based-copilot-integration\">A practical reference architecture for an MCP-based Copilot integration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s a simple, scalable pattern that works for most teams:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Copilot Host<\/strong> (VS Code \/ GitHub) uses Copilot Chat or an agent.<\/li>\n\n\n\n<li><strong>MCP Server<\/strong> (your service) exposes a handful of tools with tight schemas.<\/li>\n\n\n\n<li><strong>Integration Adapter<\/strong> inside the MCP server talks to Jira\/ServiceNow\/Confluence\/Datadog\/etc.<\/li>\n\n\n\n<li><strong>Auth and Policy<\/strong> enforce who can do what (read vs write tools; environment restrictions).<\/li>\n\n\n\n<li><strong>Observability<\/strong> logs tool calls, inputs\/outputs (redacted), latency, and error rates.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-tool-design-tips-that-make-copilot-actually-useful\">Tool design tips that make Copilot actually useful<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Prefer 5\u201315 sharp tools<\/strong> over 100 vague ones.<\/li>\n\n\n\n<li><strong>Make tools deterministic<\/strong>: same input should yield same output.<\/li>\n\n\n\n<li><strong>Return structured data<\/strong> (JSON-like objects) so the assistant can reason reliably.<\/li>\n\n\n\n<li><strong>Separate read tools from write tools<\/strong> (and gate writes more aggressively).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-example-mcp-server-tool-set-conceptual\">Example MCP server tool set (conceptual)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The exact SDK code varies by language and MCP framework, but the shape is consistent: define tools with names, input schemas, and handler functions.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/\/ Pseudocode: MCP tool definitions (conceptual)\n\ntool \"runbook.search\" (query: string, service?: string) -&amp;gt; { results: Runbook&#91;] }\ntool \"incidents.latest\" (service: string) -&amp;gt; { incidents: Incident&#91;] }\ntool \"deploy.status\" (environment: \"dev\"|\"staging\"|\"prod\", service: string) -&amp;gt; { state: string, version: string }\n\n\/\/ Write tools should be separate and tightly controlled\ntool \"ticket.create\" (project: string, title: string, body: string, severity: string) -&amp;gt; { id: string, url: string }\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When Copilot can call tools like these, your prompts become simpler: \u201cCheck the latest incident for payments-api and summarise impact,\u201d and the assistant can actually fetch the answer instead of guessing.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-migration-note-for-teams-who-built-copilot-extensions\">Migration note for teams who built Copilot Extensions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you previously invested in GitHub Copilot Extensions via GitHub Apps, plan a transition. GitHub has published a sunset timeline where GitHub App-based Copilot Extensions are disabled in November 2025, while VS Code Copilot extensions are not affected. For many teams, MCP servers are the cleanest replacement path. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-implementation-checklist-for-it-leaders\">Implementation checklist for IT leaders<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n <li><strong>Pick your first 2 use cases<\/strong>: e.g., \u201cincident triage\u201d and \u201crelease readiness.\u201d<\/li>\n <li><strong>Design your tool contracts<\/strong>: inputs\/outputs, error handling, and timeouts.<\/li>\n <li><strong>Decide where the MCP server runs<\/strong>: local vs hosted, network access rules, secrets management.<\/li>\n <li><strong>Apply least privilege<\/strong>: read-only first; introduce write tools later with approvals.<\/li>\n <li><strong>Turn on logging<\/strong>: tool call metrics, redaction, and audit trails.<\/li>\n <li><strong>Roll out with guardrails<\/strong>: pilot group, documented do\/don\u2019t prompts, feedback loop.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-wrap-up\">Wrap-up<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The simplest way to think about \u201cGitHub Copilot SDK architecture\u201d is this: <strong>Copilot is the conversational brain, MCP is the tool contract, and your integration is the muscle<\/strong>. If you invest in a clean tools layer (schemas, permissions, observability), Copilot becomes dramatically more reliable\u2014regardless of which model is in fashion this quarter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019d like, tell us what systems you want Copilot to connect to (Azure DevOps, Jira, ServiceNow, Confluence, GitHub Issues, Datadog, Splunk), and we can map a minimal MCP tool set that delivers value in the first sprint.<\/p>\n\n\n\n<ul class=\"wp-block-yoast-seo-related-links yoast-seo-related-links\">\n<li><a href=\"https:\/\/www.cloudproinc.com.au\/index.php\/2025\/04\/18\/setting-up-azure-mcp-server-with-vs-code\/\">Setting Up Azure MCP Server with VS Code<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/cloudproinc.com.au\/index.php\/2025\/11\/26\/accelerate-vs-code-development-with-mcp-servers\/\">Accelerate VS Code Development with MCP Servers<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.cloudproinc.com.au\/index.php\/2024\/09\/10\/simplifying-azure-management-with-github-copilot-for-azure\/\">Simplifying Azure Management with GitHub Copilot for Azure<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/cloudproinc.azurewebsites.net\/index.php\/2026\/02\/03\/use-cases-for-the-github-copilot-sdk\/\">Use Cases for the GitHub Copilot SDK<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.cloudproinc.com.au\/index.php\/2025\/04\/28\/creating-an-mcp-server-in-c-to-call-openai-and-list-files\/\">Creating an MCP Server in C# to Call OpenAI and List Files<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Understand how GitHub Copilot SDK-style integrations work, from context to tools to policies. Learn a practical architecture that helps teams build reliable Copilot experiences with agents and MCP.<\/p>\n","protected":false},"author":1,"featured_media":56974,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[13,99],"tags":[],"class_list":["post-56972","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-github-copilot-sdk"],"jetpack-related-posts":[{"id":56973,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/12\/github-copilot-cli-vs-github-copilot-sdk\/","url_meta":{"origin":56972,"position":0},"title":"GitHub Copilot CLI vs GitHub Copilot SDK","author":"CPI Staff","date":"October 12, 2026","format":false,"excerpt":"Copilot CLI helps individuals move faster in the terminal. Copilot SDK helps teams embed Copilot into products and workflows. Here\u2019s how to choose, govern, and roll out both.","rel":"","context":"In &quot;Blog&quot;","block_context":{"text":"Blog","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/blog\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/02\/post-12.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/02\/post-12.png 1x, \/wp-content\/uploads\/2026\/02\/post-12.png 1.5x, \/wp-content\/uploads\/2026\/02\/post-12.png 2x, \/wp-content\/uploads\/2026\/02\/post-12.png 3x, \/wp-content\/uploads\/2026\/02\/post-12.png 4x"},"classes":[]},{"id":56943,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/12\/use-cases-for-the-github-copilot-sdk\/","url_meta":{"origin":56972,"position":1},"title":"Use Cases for the GitHub Copilot SDK","author":"CPI Staff","date":"October 12, 2026","format":false,"excerpt":"Explore real-world ways to use the GitHub Copilot SDK to automate developer workflows, build team assistants, and safely connect internal tools to AI\u2014without losing control of security and governance.","rel":"","context":"In &quot;Blog&quot;","block_context":{"text":"Blog","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/blog\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/02\/post-5.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/02\/post-5.png 1x, \/wp-content\/uploads\/2026\/02\/post-5.png 1.5x, \/wp-content\/uploads\/2026\/02\/post-5.png 2x, \/wp-content\/uploads\/2026\/02\/post-5.png 3x, \/wp-content\/uploads\/2026\/02\/post-5.png 4x"},"classes":[]},{"id":56961,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/12\/benefits-of-using-github-copilot-coding-agents\/","url_meta":{"origin":56972,"position":2},"title":"Benefits of Using GitHub Copilot Coding Agents","author":"CPI Staff","date":"October 12, 2026","format":false,"excerpt":"GitHub Copilot coding agents can take on routine engineering tasks in the background and deliver draft pull requests for review. Learn how they work, where they fit, and how to use them safely.","rel":"","context":"In &quot;AI&quot;","block_context":{"text":"AI","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/ai\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/02\/post-8.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/02\/post-8.png 1x, \/wp-content\/uploads\/2026\/02\/post-8.png 1.5x, \/wp-content\/uploads\/2026\/02\/post-8.png 2x, \/wp-content\/uploads\/2026\/02\/post-8.png 3x, \/wp-content\/uploads\/2026\/02\/post-8.png 4x"},"classes":[]},{"id":56919,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/12\/parallel-code-review-with-github-copilot-cli\/","url_meta":{"origin":56972,"position":3},"title":"Parallel Code Review with GitHub Copilot CLI","author":"CPI Staff","date":"October 12, 2026","format":false,"excerpt":"Run multiple AI review passes in parallel from your terminal using GitHub Copilot CLI. Catch bugs, security issues, and style drift earlier\u2014without slowing down your human reviewers.","rel":"","context":"In &quot;Blog&quot;","block_context":{"text":"Blog","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/blog\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":57198,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/12\/github-copilot-adds-claude-and-codex-how-to-standardise-dev-ai-safely\/","url_meta":{"origin":56972,"position":4},"title":"GitHub Copilot adds Claude and Codex\u2014how to standardise dev AI safely","author":"CPI Staff","date":"October 12, 2026","format":false,"excerpt":"Copilot is no longer \u201cone assistant.\u201d With Claude and Codex in the mix, tooling decisions now affect cost, security, and code quality. Here\u2019s how to standardise without slowing teams down.","rel":"","context":"In &quot;Blog&quot;","block_context":{"text":"Blog","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/blog\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/03\/post-9.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/03\/post-9.png 1x, \/wp-content\/uploads\/2026\/03\/post-9.png 1.5x, \/wp-content\/uploads\/2026\/03\/post-9.png 2x, \/wp-content\/uploads\/2026\/03\/post-9.png 3x, \/wp-content\/uploads\/2026\/03\/post-9.png 4x"},"classes":[]},{"id":57610,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/12\/githubs-new-agent-desktop-changes-what-senior-developers-can-delegate\/","url_meta":{"origin":56972,"position":5},"title":"GitHub&#8217;s New Agent Desktop Changes What Senior Developers Can Delegate","author":"CPI Staff","date":"October 12, 2026","format":false,"excerpt":"Most organisations are still treating AI coding tools like faster autocomplete. That is already out of date. At Microsoft Build 2026, GitHub introduced the new GitHub Copilot app as an agent-native desktop experience. For senior developers and engineering leaders, the real significance is not the interface. It is the operating\u2026","rel":"","context":"In &quot;AI for Business &amp; AI Strategy&quot;","block_context":{"text":"AI for Business &amp; AI Strategy","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/ai-for-business-ai-strategy\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/06\/github-agent-desktop-changes-developer-delegation.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/06\/github-agent-desktop-changes-developer-delegation.png 1x, \/wp-content\/uploads\/2026\/06\/github-agent-desktop-changes-developer-delegation.png 1.5x, \/wp-content\/uploads\/2026\/06\/github-agent-desktop-changes-developer-delegation.png 2x, \/wp-content\/uploads\/2026\/06\/github-agent-desktop-changes-developer-delegation.png 3x, \/wp-content\/uploads\/2026\/06\/github-agent-desktop-changes-developer-delegation.png 4x"},"classes":[]}],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"\/wp-content\/uploads\/2026\/02\/post-11.png","_links":{"self":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts\/56972","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/comments?post=56972"}],"version-history":[{"count":2,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts\/56972\/revisions"}],"predecessor-version":[{"id":56980,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts\/56972\/revisions\/56980"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/media\/56974"}],"wp:attachment":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/media?parent=56972"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/categories?post=56972"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/tags?post=56972"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}