{"id":21328,"date":"2026-07-06T12:46:03","date_gmt":"2026-07-06T12:46:03","guid":{"rendered":"https:\/\/www.sapcloudone.de\/?p=21328"},"modified":"2026-07-06T12:46:03","modified_gmt":"2026-07-06T12:46:03","slug":"sap-business-one-shopify-integration-architecture-explained","status":"publish","type":"post","link":"https:\/\/www.sapcloudone.de\/us\/sap-business-one-shopify-integration-architecture-explained\/","title":{"rendered":"SAP Business One Shopify Integration Architecture Explained"},"content":{"rendered":"

“We already have an integration” is one of the more dangerous sentences in an SAP Business One project. It usually means a nightly CSV export somebody built three years ago, held together with a scheduled task and one developer’s memory of why it works. It is not\u00a0an architecture. It is a workaround that has not failed yet.<\/span>\u00a0<\/span><\/p>\n

A genuine SAP Business One Shopify integration architecture is a designed system with layers that each do one job: a data access layer that exposes SAP objects safely, an event layer that reacts to change as it happens, an orchestration layer that transforms and routes that data, and an observability layer that tells you when something has gone wrong before a customer does. This article works through each of those layers \u2014 Service Layer, REST,\u00a0GraphQL, webhooks, middleware, direct integration, monitoring and security \u2014 and how they fit together into a data flow that actually holds up at order volume.<\/span>\u00a0<\/span><\/p>\n

What “Architecture” Actually Means in an SAP B1\u2013Shopify Integration<\/span><\/b>\u00a0<\/span><\/h2>\n

It is worth being precise about the word, because “integration” gets used to describe everything from a single scheduled script to a fully event-driven,\u00a0monitored\u00a0data pipeline. Architecture, in this context, means the deliberate choice of how data gets from SAP Business One to Shopify and back \u2014 which protocol carries it, what triggers the transfer, where transformation logic lives, and how failures are caught rather than discovered by an angry customer.<\/span>\u00a0<\/span><\/p>\n

Every SAP Business One Shopify integration, regardless of vendor or approach, is built from the same handful of components. SAP Business One exposes its data through the Service Layer (a modern, RESTful, OData-based API) or, in older or deeper-access scenarios, the DI API. Shopify exposes its data through the Admin API, available in both REST and\u00a0GraphQL\u00a0form, and pushes real-time events out through webhooks. Sitting between the two is either a thin, direct connection or a middleware layer that handles mapping,\u00a0transformation\u00a0and error handling. Around all of it sits monitoring and security, which are not optional add-ons but the difference between an integration that scales and one that quietly corrupts data during a flash sale.<\/span>\u00a0<\/span><\/p>\n

Understanding each layer on its own terms \u2014 rather than treating “the integration” as a single black box \u2014 is what makes it possible to diagnose problems, plan for scale, and choose the right architecture for a given business rather than the one a vendor happens to sell.<\/span>\u00a0<\/span><\/p>\n

The SAP Business One Service Layer: The Foundation Layer<\/span><\/b>\u00a0<\/span><\/h3>\n

The Service Layer is SAP Business One’s own application server for external access \u2014 an OData-based REST API that speaks HTTP and JSON, sitting on top of the same business\u00a0object layer the SAP client itself uses. It runs identically whether SAP Business One is deployed on SQL Server or HANA, which matters because it means an integration built against the Service Layer does not need to be rebuilt if the underlying database platform changes.<\/span>\u00a0<\/span><\/p>\n

Two details catch most teams building against it for the first time. The first is session handling: authentication is comparatively slow, while\u00a0subsequent\u00a0calls using the returned session cookie are fast, so an integration needs to cache and reuse that session rather than authenticating on every request. The second is that sessions expire after a period of inactivity, so any integration needs to catch the resulting authentication error and re-authenticate automatically rather than simply failing.<\/span>\u00a0<\/span><\/p>\n

For most SAP Business One Shopify integrations, the Service Layer is the correct starting point. It covers item master, business partner, inventory, sales order and AR document data without custom ABAP-style development, and it is the interface Ingold Solutions’ own SAP-certified Shopify Add-on is built against \u2014 which is part of why it can stay aligned with SAP’s own technical and security standards rather than depending on an unsupported workaround.<\/span>\u00a0<\/span><\/p>\n

REST APIs: How the Data Actually Moves<\/span><\/b>\u00a0<\/span><\/h3>\n

REST is the\u00a0protocol\u00a0doing\u00a0the heavy\u00a0lifting on both sides of this integration. On the SAP side, the Service Layer’s REST endpoints expose business objects such as Items,\u00a0BusinessPartners,\u00a0SalesOrders\u00a0and Deliveries as structured JSON resources that can be queried,\u00a0created\u00a0or updated over standard HTTP methods. On the Shopify side, the REST Admin API exposes products, customers,\u00a0orders\u00a0and inventory levels in the same pattern.<\/span>\u00a0<\/span><\/p>\n

In a typical SAP Business One Shopify integration, REST calls handle both directions of the core data flow: pushing product,\u00a0pricing\u00a0and stock data from SAP out to Shopify, and pulling customer and order data from Shopify back into SAP as sales documents. Because each call maps cleanly to a single business object, REST\u00a0remains\u00a0the most straightforward protocol to build, debug and document \u2014 which is exactly why it underpins most production integrations, including template-based and custom-built ones alike.<\/span>\u00a0<\/span><\/p>\n

The trade-off is\u00a0efficiency\u00a0at scale. A REST integration that needs several related pieces of data \u2014 a product, its variants, and its current stock across multiple warehouses \u2014 often has to make several separate calls to assemble a single, complete picture, which is where\u00a0GraphQL\u00a0starts to earn its place in\u00a0architecture.<\/span>\u00a0<\/span><\/p>\n

GraphQL: Where Shopify’s API Strategy Is Heading<\/span><\/b>\u00a0<\/span><\/h3>\n

Shopify has been steadily shifting its Admin API surface toward\u00a0GraphQL, and any SAP Business One Shopify integration architecture built today needs to account for that direction rather than assume REST will\u00a0remain\u00a0the primary interface indefinitely.\u00a0GraphQL\u00a0lets an integration request exactly the fields it needs, across related objects, in a single call \u2014 a\u00a0product with its variants, prices and inventory levels in one round trip, rather than the multiple REST calls the same request would otherwise require.<\/span>\u00a0<\/span><\/p>\n

For high-volume SAP B1 to Shopify product and inventory\u00a0synchronization, that difference is not cosmetic. Fewer round trips\u00a0means\u00a0lower latency, less exposure to rate limiting, and simpler error handling, since a single\u00a0GraphQL\u00a0response either\u00a0contains\u00a0everything needed or clearly reports what failed. Shopify Functions \u2014 which run custom logic directly at checkout, for scenarios like tiered pricing that mirrors SAP’s own pricing structures \u2014 are also\u00a0GraphQL-native, which matters for any integration planning to support more advanced, SAP-driven pricing logic on the storefront.<\/span>\u00a0<\/span><\/p>\n

In practice, most current SAP Business One Shopify integrations still lean on REST for its simplicity, particularly for order intake, while increasingly routing catalogue and inventory\u00a0synchronization\u00a0through\u00a0GraphQL. An architecture designed with both protocols available, rather than locked into one, ages\u00a0considerably better\u00a0as Shopify’s own API surface continues to evolve.<\/span>\u00a0<\/span><\/p>\n

Webhooks: The Event Layer<\/span><\/b>\u00a0<\/span><\/h3>\n

Polling an API on a schedule to check “has anything changed?” is the single biggest source of both wasted API calls and stale data in ERP-to-ecommerce integrations. Webhooks solve this by inverting the relationship: instead of the integration asking Shopify for updates, Shopify pushes a payload to a defined endpoint the moment an event happens \u2014 an order created, a customer registered, a fulfilment updated.<\/span>\u00a0<\/span><\/p>\n

In a well-designed SAP Business One Shopify integration architecture, webhooks are what\u00a0make\u00a0near-real-time order sync possible. A new Shopify order fires a webhook, which triggers the integration to\u00a0immediately\u00a0create the corresponding SAP Business One sales order, complete with customer, item, pricing,\u00a0tax\u00a0and discount data, rather than waiting for a scheduled batch job to notice it.<\/span>\u00a0<\/span><\/p>\n

The architectural discipline webhooks demand is idempotency: because webhook delivery is not always guaranteed to happen exactly once, the receiving system needs to\u00a0recognise\u00a0and safely ignore a duplicate delivery of the same event, rather than creating the same sales order twice. This is\u00a0detail generic connectors\u00a0sometimes get wrong, and one worth specifically asking about when evaluating an integration partner.<\/span>\u00a0<\/span><\/p>\n

Middleware: The Orchestration Layer<\/span><\/b>\u00a0<\/span><\/h3>\n

Middleware sits between SAP Business One and Shopify and does the work neither system does natively: transforming SAP’s data model into Shopify’s, applying business rules, handling retries, and giving a human somewhere to look when something goes wrong. SAP’s own Integration Framework (B1if) is one\u00a0option, built specifically for SAP-centered\u00a0integration\u00a0scenarios; third-party iPaaS platforms are another, offering pre-built connectors and visual data-flow configuration in exchange for less SAP-specific depth.<\/span>\u00a0<\/span><\/p>\n

Middleware earns its complexity in multi-system environments \u2014 SAP Business One, Shopify and a CRM, a warehouse management system, or multiple sales channels all needing to stay\u00a0in sync\u00a0\u2014 where transformation and orchestration logic would otherwise be duplicated across several point-to-point connections. For a single, well-defined SAP B1-to-Shopify relationship, a purpose-built add-on that wraps this orchestration logic natively, such as the Ingold Solutions SAP Business One Shopify Add-on, typically delivers the same reliability with\u00a0considerably less\u00a0infrastructure to\u00a0maintain.<\/span>\u00a0<\/span><\/p>\n

The architectural question worth asking early is not “do we need middleware” but “where does our transformation logic live, and who maintains it when SAP or Shopify changes their API.” That question\u00a0determines\u00a0far more about long-term cost of ownership than the\u00a0initial\u00a0build price.<\/span>\u00a0<\/span><\/p>\n

Direct Integration vs Middleware: Making the Trade-off Deliberately<\/span><\/b>\u00a0<\/span><\/h3>\n

A direct integration connects SAP Business One’s Service Layer straight to Shopify’s Admin API, with custom code handling authentication, mapping, error handling and retry logic in between. It offers full control and no additional infrastructure layer, which makes it well suited to businesses with unique pricing rules, multi-warehouse logic or custom fields that a template-based product does not cover \u2014 provided there is development capacity to build and, critically, maintain it.<\/span>\u00a0<\/span><\/p>\n

The maintenance point deserves more weight than it usually gets in vendor comparisons. A direct integration is not a one-off build; it is a piece of software that needs to keep working every time SAP releases a patch, Shopify updates its API version, or a new edge case appears in production. Middleware and pre-built add-ons absorb much of that ongoing maintenance burden into a supported product rather than leaving it with an internal team.<\/span>\u00a0<\/span><\/p>\n

As a rough guide: a native, template-based add-on typically suits businesses with standard B2C order-to-fulfilment flows and no unusual pricing logic. Middleware suits businesses already juggling several connected systems. A custom direct build suits businesses with genuinely unique requirements and the in-house or contracted development capacity to support it for the long term \u2014 not just to launch it.<\/span>\u00a0<\/span><\/p>\n

Monitoring: Keeping the Integration Observable<\/span><\/b>\u00a0<\/span><\/h3>\n

An integration without monitoring does not fail loudly \u2014 it fails quietly, usually as a slow accumulation of\u00a0unsynced\u00a0orders, mismatched stock counts, or duplicate customer records that nobody notices until a customer\u00a0complaints\u00a0or month-end reconciliation does not balance.<\/span>\u00a0<\/span><\/p>\n

A properly architected SAP Business One Shopify integration needs, at minimum, logging of every transaction attempt with enough detail to diagnose a failure without reproducing it live,\u00a0alerting when a sync fails rather than a dashboard someone has to remember to check, and a reprocessing mechanism that lets a failed transaction be corrected and resubmitted without manual data re-entry on either side.<\/span>\u00a0<\/span><\/p>\n

This is the layer most likely to be underbuilt in a rushed or purely custom integration, and it is precisely the layer that\u00a0determines\u00a0whether an issue during a peak sales period is a five-minute fix or a week of manual reconciliation.<\/span>\u00a0<\/span><\/p>\n

Security: Authentication, Encryption and Access Control<\/span><\/b>\u00a0<\/span><\/h3>\n

Every layer discussed so far moves commercially sensitive data \u2014 customer records, pricing, order values \u2014 between two systems over the internet, which makes security an architectural concern, not a checkbox added at the end.<\/span>\u00a0<\/span><\/p>\n

At minimum, a sound architecture uses HTTPS for every connection, OAuth 2.0 for API authentication rather than long-lived static credentials wherever both systems support it, and scoped API access so the integration can only read and write the specific data objects it\u00a0actually needs. SAP Business One’s Service Layer supports OAuth 2.0 and OpenID Connect on current versions, which is worth confirming against the specific SAP Business One patch level in use before assuming it is available.<\/span>\u00a0<\/span><\/p>\n

Beyond transport security, access control matters just as much: credentials for the integration should be distinct from any individual user’s login, rotated on a defined schedule, and scoped narrowly enough that a compromised integration credential cannot be used to access unrelated parts of either system.<\/span>\u00a0<\/span><\/p>\n

Data Flow Diagram: How the Layers Work Together<\/span><\/b>\u00a0<\/span><\/h3>\n

Put together, a typical SAP Business One Shopify integration architecture moves data through the following path for the two most common flows:<\/span>\u00a0<\/span><\/p>\n

Catalogue and inventory (SAP Business One \u2192 Shopify)<\/span><\/b>\u00a0<\/span><\/h3>\n\n\n\n
SAP Item Master & Stock<\/span><\/b>\u00a0<\/span><\/td>\n\u2192<\/span><\/b>\u00a0<\/span><\/td>\nService Layer \/\u00a0GraphQL<\/span><\/b>\u00a0<\/span><\/td>\n\u2192<\/span><\/b>\u00a0<\/span><\/td>\nMiddleware or Add-on<\/span><\/b>\u00a0<\/span><\/td>\n\u2192<\/span><\/b>\u00a0<\/span><\/td>\nShopify Admin API<\/span><\/b>\u00a0<\/span><\/td>\n\u2192<\/span><\/b>\u00a0<\/span><\/td>\nStorefront<\/span><\/b>\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Orders and customers (Shopify \u2192 SAP Business One)<\/span><\/b>\u00a0<\/span><\/p>\n\n\n\n
Shopify Checkout<\/span><\/b>\u00a0<\/span><\/td>\n\u2192<\/span><\/b>\u00a0<\/span><\/td>\nWebhook Event<\/span><\/b>\u00a0<\/span><\/td>\n\u2192<\/span><\/b>\u00a0<\/span><\/td>\nMiddleware or Add-on<\/span><\/b>\u00a0<\/span><\/td>\n\u2192<\/span><\/b>\u00a0<\/span><\/td>\nService Layer<\/span><\/b>\u00a0<\/span><\/td>\n\u2192<\/span><\/b>\u00a0<\/span><\/td>\nSAP Sales Order & A\/R Documents<\/span><\/b>\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

T<\/span>he two flows run in opposite directions and on different triggers \u2014 one largely scheduled or event-driven from the SAP side, the other webhook-driven from the Shopify side \u2014 which is precisely why treating the integration as a single undifferentiated pipe, rather than two distinct flows with their own failure modes, is where a lot of home-built integrations run into trouble.<\/span>\u00a0<\/span><\/p>\n

Frequently Asked Questions<\/span><\/b>\u00a0<\/span><\/h3>\n

What is the SAP Business One Service Layer?<\/span><\/b>\u00a0<\/span><\/h4>\n

The Service Layer is SAP Business One’s RESTful, OData-based API for external access. It exposes business objects such as items, business partners, sales orders and inventory over HTTP and JSON, and works identically on both SQL Server and HANA deployments.<\/span>\u00a0<\/span><\/p>\n

Should\u00a0a\u00a0SAP Business One Shopify integration use REST or\u00a0GraphQL?<\/span><\/b>\u00a0<\/span><\/h4>\n

Most current integrations use REST for its simplicity, particularly for order intake, while increasingly routing catalogue and inventory\u00a0synchronization\u00a0through\u00a0GraphQL\u00a0for efficiency. An architecture that supports both tends to age better as Shopify’s API surface evolves.<\/span>\u00a0<\/span><\/p>\n

Why are webhooks important in this architecture?<\/span><\/b>\u00a0<\/span><\/h4>\n

Webhooks let Shopify push order,\u00a0customer\u00a0and fulfilment events to the integration the moment they happen, rather than requiring the integration to repeatedly poll for changes. This is what makes near-real-time order sync into SAP Business One possible.<\/span>\u00a0<\/span><\/p>\n

Do I need middleware, or can I integrate directly?<\/span><\/b>\u00a0<\/span><\/h4>\n

Middleware is worth the added complexity in multi-system environments needing shared transformation and orchestration logic. For a single, well-defined SAP B1-to-Shopify connection, a purpose-built add-on often delivers the same reliability with less infrastructure to\u00a0maintain\u00a0than either a direct custom build or general-purpose middleware.<\/span>\u00a0<\/span><\/p>\n

How is data kept secure in\u00a0a\u00a0SAP Business One Shopify integration?<\/span><\/b>\u00a0<\/span><\/h4>\n

A sound architecture uses HTTPS for every connection, OAuth 2.0 authentication where supported, and scoped API credentials limited to the specific data the integration needs \u2014 separate from individual user logins and rotated on a defined schedule.<\/span>\u00a0<\/span><\/p>\n

What happens when a sync fails?<\/span><\/b>\u00a0<\/span><\/h4>\n

In a properly\u00a0monitored\u00a0integration, a failed transaction is logged, triggers an alert, and can be reprocessed once the underlying issue is fixed \u2014 without manual re-entry of the order,\u00a0customer\u00a0or inventory data on either system.<\/span>\u00a0<\/span><\/p>\n

Can this architecture support multiple warehouses and sales channels?<\/span><\/b>\u00a0<\/span><\/h4>\n

Yes. Shopify store locations can be mapped to SAP Business One warehouses for\u00a0accurate\u00a0stock allocation, and the same architectural pattern extends to\u00a0additional\u00a0sales channels by adding further endpoints into the same middleware or add-on layer.<\/span>\u00a0<\/span><\/p>\n

Conclusion<\/span><\/b>\u00a0<\/span><\/p>\n

None of these layers \u2014 Service Layer, REST,\u00a0GraphQL, webhooks, middleware, monitoring, security \u2014 is optional in\u00a0a\u00a0SAP Business One Shopify integration architecture built to last. What varies by business is how much of that architecture is built custom, absorbed into a purpose-built add-on, or handled by general-purpose middleware. What should not vary is whether each layer is deliberately designed rather than assumed.<\/span>\u00a0<\/span><\/p>\n

Ingold Solutions builds and supports\u00a0a\u00a0SAP-certified SAP Business One Shopify integration for exactly this reason \u2014 so that catalogue, inventory, customer and order\u00a0synchronization\u00a0runs on an architecture that was designed for it, with the monitoring and security layers already built in, rather than assembled under deadline pressure. Contact our SAP integration experts for a free consultation.<\/span>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

“We already have an integration” is one of the more dangerous sentences in an SAP Business One project. It usually means a nightly CSV export somebody built three years ago, held together with a scheduled task and one developer’s memory of why it works. It is not\u00a0an architecture. It is a workaround that has not […]<\/p>\n","protected":false},"author":2,"featured_media":21329,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-21328","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-unkategorisiert"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"SAP Business One Shopify Integration Architecture Explained","description":"Learn how SAP Business One Shopify integration works, including data flow, real-time sync, architecture, and best practices for scalable eCommerce.","canonical_url":"https:\/\/www.sapcloudone.de\/us\/sap-business-one-shopify-integration-architecture-explained\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"SAP Cloud -","og:type":"article","og:title":"SAP Business One Shopify Integration Architecture Explained","og:description":"Learn how SAP Business One Shopify integration works, including data flow, real-time sync, architecture, and best practices for scalable eCommerce.","og:url":"https:\/\/www.sapcloudone.de\/us\/sap-business-one-shopify-integration-architecture-explained\/","article:published_time":"2026-07-06T12:46:03+00:00","article:modified_time":"2026-07-06T12:46:03+00:00","twitter:card":"summary_large_image","twitter:title":"SAP Business One Shopify Integration Architecture Explained","twitter:description":"Learn how SAP Business One Shopify integration works, including data flow, real-time sync, architecture, and best practices for scalable eCommerce."},"aioseo_meta_data":{"post_id":"21328","title":"SAP Business One Shopify Integration Architecture Explained","description":"Learn how SAP Business One Shopify integration works, including data flow, real-time sync, architecture, and best practices for scalable eCommerce.","keywords":null,"keyphrases":{"focus":{"keyphrase":"","score":0,"analysis":{"keyphraseInTitle":{"score":0,"maxScore":9,"error":1}}},"additional":[]},"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":"","og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"BlogPosting","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":"-1","robots_max_videopreview":"-1","robots_max_imagepreview":"large","priority":null,"frequency":"default","local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":{"faqs":[],"keyPoints":[],"schemas":[],"titles":[],"descriptions":[],"socialPosts":{"email":{"subject":"","preview":"","content":""},"linkedin":[],"twitter":[],"facebook":[],"instagram":[]}},"created":"2026-07-06 12:46:03","updated":"2026-07-06 13:21:09","seo_analyzer_scan_date":null},"aioseo_breadcrumb":"

\n\t\t\tHome<\/a>\n\t\t<\/span>»<\/span>\n\t\t\tUnkategorisiert<\/a>\n\t\t<\/span>»<\/span>\n\t\t\tSAP Business One Shopify Integration Architecture Explained\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/www.sapcloudone.de\/us\/"},{"label":"Unkategorisiert","link":"https:\/\/www.sapcloudone.de\/jp\/category\/unkategorisiert\/"},{"label":"SAP Business One Shopify Integration Architecture Explained","link":"https:\/\/www.sapcloudone.de\/us\/sap-business-one-shopify-integration-architecture-explained\/"}],"_links":{"self":[{"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/posts\/21328","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/comments?post=21328"}],"version-history":[{"count":1,"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/posts\/21328\/revisions"}],"predecessor-version":[{"id":21343,"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/posts\/21328\/revisions\/21343"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/media\/21329"}],"wp:attachment":[{"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/media?parent=21328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/categories?post=21328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sapcloudone.de\/us\/wp-json\/wp\/v2\/tags?post=21328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}