{"id":27090,"date":"2026-10-29T08:26:18","date_gmt":"2026-10-29T07:26:18","guid":{"rendered":"https:\/\/scheer-pas.com\/en\/?post_type=post_type_article&p=27090"},"modified":"2026-10-29T09:46:48","modified_gmt":"2026-10-29T08:46:48","slug":"kba-interface-integration-automotive","status":"publish","type":"post_type_article","link":"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/","title":{"rendered":"KBA Interface Integration for Automotive Manufacturers: Keeping a Legacy SOAP Connection Stable\u00a0"},"content":{"rendered":"
<\/div>
\n
\n \"Illustration <\/div>\n\n<\/div><\/div>
\n\t

BLOG<\/p>\n<\/div><\/div><\/div><\/div>

\n\n\t
\n\t\t

KBA Interface Integration for Automotive Manufacturers: Keeping a Legacy SOAP Connection Stable <\/h1>\t<\/div>\n\n<\/div><\/div>
\n\t

October 28 | Lukas Peter<\/p>\n<\/div><\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\t

The <\/span>Kraftfahrt-Bundesamt<\/span> (KBA), Germany’s Federal Motor Transport Authority, exchanges vehicle and approval data with manufacturers through a SOAP interface whose schema only the authority controls. For one automotive manufacturer, a central integration layer in Scheer PAS kept internal systems stable while the specification was incomplete, support from the authority was limited, passwords had to be renewed regularly, and the authority changed the interface on short notice.<\/span><\/span>\u00a0<\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\t
\n\t\t
<\/div>\n\t\t\t\t
<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>
<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

TL;DR <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

The KBA dictates schema, documentation, credentials, and deadlines. Because all of that sat in one integration layer, a KBA interface revision with a two-month deadline only had to be implemented there, not in the manufacturer’s own systems.<\/span><\/span>\u00a0<\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\t
\n\t\t
<\/div>\n\t\t\t\t
<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>
<\/div><\/div>
<\/div>
\n\t

Government interfaces rarely get much attention in integration projects. They are one connection among many, until they stop working. Then vehicle registration stops with them, and a deadline set by regulation does not <\/span>move for<\/span> anyone’s release plan. That <\/span>makes<\/span> them a good test of how an integration layer is built, and of what an AI agent would later need from it.<\/span><\/span>\u00a0<\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n
\n \"The <\/div>\n\n<\/div><\/div><\/div>
<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

Why is the KBA interface hard to integrate? <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

The KBA interface is hard to integrate because the manufacturer controls none of its parameters. The KBA sets the schema, writes the documentation, defines the credential cycle, and decides when the interface changes. Anyone of these can stop the process if the integration does not absorb it.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

The schema is fixed. It has no extension points and no room for a field the manufacturer would find useful. Internal data must fit the authority’s structure, never the other way round.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

The official specification was incomplete, and technical support from the authority was limited. Parts of the endpoint’s behavior only became clear by sending messages and reading the responses.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Access depends on passwords that must be renewed regularly. Miss a renewal, and the user is locked and communication with the KBA stops.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

And when the authority revises the interface, regulation sets the deadline, not the manufacturer’s release calendar. In this project, the KBA announced extensive changes and left two months to implement them.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

If the connection breaks, production, vehicle registration, and compliance reporting stall with it.<\/span>\u00a0<\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

How does an integration layer protect internal systems from KBA interface changes? <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

An integration layer protects internal systems by owning everything that is KBA-specific. The manufacturer keeps delivering data in its own format. Configurable mappings and rule sets in Scheer PAS transform it into the structure the KBA <\/span>requires<\/span>, and the connection itself sits there too. When the KBA changes its interface, the change happens there, and ERP and internal master data systems stay as they are.<\/span><\/p>\n<\/div><\/div><\/div>

\n
\n \"KBA<\/picture> <\/div>\n\n<\/div><\/div>
\n\t

That concentration is what made a short delivery window manageable. Instead of coordinating changes across several backend systems and their release cycles, the team adjusted mappings and service models in Scheer PAS. All changes were implemented within the deadline, and the manufacturer did not have to adapt any of its own systems.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Complex response messages from the KBA are mapped back as well, into a format the manufacturer’s processes understand. Internal systems never handle the authority’s XML directly.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

The trade-off is that the integration layer becomes software, to be owned, versioned, and tested. For an interface that changes on someone else’s schedule, that is still the cheaper option.<\/span>\u00a0<\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

How do you stop expiring credentials from blocking vehicle registration? <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

Expiring KBA passwords stop being a risk once the integration layer tracks and renews them, instead of a calendar entry. In this project, an automated process in Scheer PAS continuously checks whether the credentials are still valid and renews passwords before they expire. User accounts are not locked, and business processes do not stop.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

It sounds like a detail. In practice, an expired credential is one of the few failures that can stop a correctly mapped, fully tested interface overnight.<\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n
\n \"Iterative <\/div>\n\n<\/div><\/div><\/div>
<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

How do you integrate an interface with incomplete documentation? <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

An interface with incomplete documentation has to be integrated against its observed behaviors, not just the spec. With key information missing, the project team analysed how the KBA endpoint actually behaved, adjusted the mappings to what it accepted and returned, and developed the integration iteratively through tests and validation until it ran reliably in production.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

This approach is slower at the start and faster overall. Every behavior found this way ends up in the mapping, where the next interface revision can be checked against it.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

KBA constraints at a glance<\/span><\/b>\u00a0<\/span><\/h3>\n<\/div><\/div><\/div>
\n
\n\t
\n\t\t
\n\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t
\n\n\t
\n\t\t

Constraint at the KBA <\/h4>\t<\/div>\n\n<\/div><\/div><\/div><\/th>

\n\n\t
\n\t\t

Risk without an integration layer <\/h4>\t<\/div>\n\n<\/div><\/div><\/div><\/td>

\n\n\t
\n\t\t

How the integration layer handles it <\/h4>\t<\/div>\n\n<\/div><\/div><\/div><\/td>\t\t\t\t\t<\/tr>\n\t\t\t\t\t\t\t\t\t

\n\n
\n

Fixed SOAP schema<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/th>

\n\n
\n

Internal data does not fit<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/td>

\n\n
\n

Mapping to the KBA XML schema<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/td>\t\t\t\t\t<\/tr>\n\t\t\t\t\t\t\t\t\t

\n\n
\n

Incomplete specification, limited support<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/th>

\n\n
\n

Messages rejected or misread in production<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/td>

\n\n
\n

Iterative tests against the real endpoint; whatever turned up went into the mapping<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/td>\t\t\t\t\t<\/tr>\n\t\t\t\t\t\t\t\t\t

\n\n
\n

Passwords that must be renewed regularly<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/th>

\n\n
\n

Locked user, communication with the KBA stops<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/td>

\n\n
\n

Automated monitoring and renewal<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/td>\t\t\t\t\t<\/tr>\n\t\t\t\t\t\t\t\t\t

\n\n
\n

Interface revisions on a regulatory deadline<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/th>

\n\n
\n

Changes spread across several backend systems and their release cycles<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/td>

\n\n
\n

Mappings and service models only, ERP untouched<\/p><\/div>\n <\/div>\n\n<\/div><\/div><\/div><\/td>\t\t\t\t\t<\/tr>\n\t\t\t\t\t\t\t<\/tbody>\n\t\t<\/table>\n\t\t<\/div>\n\t<\/div>\n<\/div>\n<\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

Why can’t an AI agent submit data to the KBA directly? <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

An AI agent should not submit data to the KBA directly, because the KBA records every submission, and correcting a wrong one is an administrative process, not a rollback. A language model can produce XML that looks valid and still uses a code the authority does not accept or leaves out a field the endpoint expects.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

The layer that made this integration reliable is the same one an agent would need underneath. The agent can decide that a record has to be filed, gather the data, and prepare the request. Scheer PAS then maps it, checks it against the schema, uses credentials the agent never sees, and sends it.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

The agent never touches the SOAP envelope, the endpoint address, or the credentials. It calls an operation with a defined input and output. How Scheer PAS defines which operations an agent may execute is described in this article<\/a>.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

No AI agents were used in this project. The integration layer described here is the precondition for using them later.<\/span><\/span>\u00a0<\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n
\n \"Schema <\/div>\n\n<\/div><\/div><\/div>
<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

What guardrails do agent-prepared KBA submissions need? <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

Agent-prepared KBA submissions need checks that run before the message leaves the company. Once a submission reaches the KBA, it is on record. Three of them are specific to this interface.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Schema enforcement<\/span><\/b> against the current KBA schema version, plus plausibility checks against internal master data. A submission that fails here never reaches the authority.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Credential isolation.<\/span><\/b> The agent requests an operation; the integration layer holds and renews the credentials. The agent never sees or stores them.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Approval before submission<\/span><\/b> for anything that changes an official record. Queries can run automatically. Submissions wait for a person.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

The general requirements for agent governance, from validation and permissions to logging and human approval, are covered in this article<\/a>.<\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

Lessons learned<\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

Treat the KBA interface as something that will change without asking you. Everything specific to it belongs in one place, and that place is not the ERP system.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Automate credential renewal before you need it. It is the cheapest fix in the whole project and the one most likely to be forgotten.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Expect gaps in the documentation, do not count on support from the authority, and plan time for testing against the real endpoint.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

And if AI agents are on the roadmap, they will need exactly this layer underneath. Build it for the interface first.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Government interfaces are usually treated as a box to tick. Projects like this one show that they are where an integration layer earns its keep, and where an AI agent would fail first if it had nothing in between.<\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

Frequently asked questions <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

What do manufacturers use the KBA interface for?<\/h3>\n

 <\/p>\n

To exchange vehicle and approval data with the Kraftfahrt-Bundesamt, which keeps Germany’s central vehicle register and acts as the national type-approval authority. When the connection fails, registration-related processes and compliance reporting stall.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Do KBA interface changes require changes to the ERP system?<\/h3>\n

 <\/p>\n

Not when the mapping between internal data and the KBA schema sits in an integration layer. Interface revisions are then handled in that layer, and ERP and internal master data systems can stay unchanged.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Who should be responsible for renewing KBA credentials?<\/h3>\n

 <\/p>\n

The integration platform that uses them. It can track validity, renew in time, and raise an alert when a renewal fails, which a calendar reminder cannot do reliably.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

About the author<\/h2>\n

 <\/p>\n

Lukas Peter<\/span><\/b> is a developer and technical consultant at Scheer PAS. He builds integration services in Scheer PAS Designer and PAS Code, including xUML and BPMN service models, REST and file-based adapters, and connections to SAP data sources. Link to author’s LinkedIn Profile – https:\/\/www.linkedin.com\/in\/lukas-peter-9998b1250\/<\/a><\/span><\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div><\/div>\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"","protected":false},"featured_media":27092,"template":"","class_list":["post-27090","post_type_article","type-post_type_article","status-publish","has-post-thumbnail","hentry"],"acf":[],"yoast_head":"\nKBA Interface Integration for Automotive Manufacturers<\/title>\n<meta name=\"description\" content=\"How an integration layer in Scheer PAS kept a legacy KBA SOAP interface stable through schema changes, expiring passwords and incomplete documentation.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"KBA Interface Integration for Automotive Manufacturers\" \/>\n<meta property=\"og:description\" content=\"How an integration layer in Scheer PAS kept a legacy KBA SOAP interface stable through schema changes, expiring passwords and incomplete documentation.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/\" \/>\n<meta property=\"og:site_name\" content=\"Scheer PAS\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-29T08:46:48+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/scheer-pas.com\/en\/wp-content\/uploads\/2026\/10\/kba-interface-01-hero@2x.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1350\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/blog\\\/article\\\/kba-interface-integration-automotive\\\/\",\"url\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/blog\\\/article\\\/kba-interface-integration-automotive\\\/\",\"name\":\"KBA Interface Integration for Automotive Manufacturers\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/blog\\\/article\\\/kba-interface-integration-automotive\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/blog\\\/article\\\/kba-interface-integration-automotive\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/kba-interface-01-hero@2x.webp\",\"datePublished\":\"2026-10-29T07:26:18+00:00\",\"dateModified\":\"2026-10-29T08:46:48+00:00\",\"description\":\"How an integration layer in Scheer PAS kept a legacy KBA SOAP interface stable through schema changes, expiring passwords and incomplete documentation.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/blog\\\/article\\\/kba-interface-integration-automotive\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/scheer-pas.com\\\/en\\\/blog\\\/article\\\/kba-interface-integration-automotive\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/blog\\\/article\\\/kba-interface-integration-automotive\\\/#primaryimage\",\"url\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/kba-interface-01-hero@2x.webp\",\"contentUrl\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/kba-interface-01-hero@2x.webp\",\"width\":2400,\"height\":1350,\"caption\":\"Integration layer between a manufacturer's internal systems and the KBA SOAP interface, absorbing interface changes\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/blog\\\/article\\\/kba-interface-integration-automotive\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Articles\",\"item\":\"https:\\\/\\\/scheer-pas.com\\\/blog\\\/article\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"KBA Interface Integration for Automotive Manufacturers: Keeping a Legacy SOAP Connection Stable\u00a0\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/\",\"name\":\"Scheer PAS\",\"description\":\"Agentic Process Orchestration\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/scheer-pas.com\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"KBA Interface Integration for Automotive Manufacturers","description":"How an integration layer in Scheer PAS kept a legacy KBA SOAP interface stable through schema changes, expiring passwords and incomplete documentation.","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:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/","og_locale":"en_GB","og_type":"article","og_title":"KBA Interface Integration for Automotive Manufacturers","og_description":"How an integration layer in Scheer PAS kept a legacy KBA SOAP interface stable through schema changes, expiring passwords and incomplete documentation.","og_url":"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/","og_site_name":"Scheer PAS","article_modified_time":"2026-10-29T08:46:48+00:00","og_image":[{"width":2400,"height":1350,"url":"https:\/\/scheer-pas.com\/en\/wp-content\/uploads\/2026\/10\/kba-interface-01-hero@2x.webp","type":"image\/webp"}],"twitter_card":"summary_large_image","twitter_misc":{"Estimated reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/","url":"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/","name":"KBA Interface Integration for Automotive Manufacturers","isPartOf":{"@id":"https:\/\/scheer-pas.com\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/#primaryimage"},"image":{"@id":"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/#primaryimage"},"thumbnailUrl":"https:\/\/scheer-pas.com\/en\/wp-content\/uploads\/2026\/10\/kba-interface-01-hero@2x.webp","datePublished":"2026-10-29T07:26:18+00:00","dateModified":"2026-10-29T08:46:48+00:00","description":"How an integration layer in Scheer PAS kept a legacy KBA SOAP interface stable through schema changes, expiring passwords and incomplete documentation.","breadcrumb":{"@id":"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/#primaryimage","url":"https:\/\/scheer-pas.com\/en\/wp-content\/uploads\/2026\/10\/kba-interface-01-hero@2x.webp","contentUrl":"https:\/\/scheer-pas.com\/en\/wp-content\/uploads\/2026\/10\/kba-interface-01-hero@2x.webp","width":2400,"height":1350,"caption":"Integration layer between a manufacturer's internal systems and the KBA SOAP interface, absorbing interface changes"},{"@type":"BreadcrumbList","@id":"https:\/\/scheer-pas.com\/en\/blog\/article\/kba-interface-integration-automotive\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/scheer-pas.com\/en\/"},{"@type":"ListItem","position":2,"name":"Articles","item":"https:\/\/scheer-pas.com\/blog\/article\/"},{"@type":"ListItem","position":3,"name":"KBA Interface Integration for Automotive Manufacturers: Keeping a Legacy SOAP Connection Stable\u00a0"}]},{"@type":"WebSite","@id":"https:\/\/scheer-pas.com\/en\/#website","url":"https:\/\/scheer-pas.com\/en\/","name":"Scheer PAS","description":"Agentic Process Orchestration","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/scheer-pas.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"}]}},"_links":{"self":[{"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/post_type_article\/27090","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/post_type_article"}],"about":[{"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/types\/post_type_article"}],"version-history":[{"count":11,"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/post_type_article\/27090\/revisions"}],"predecessor-version":[{"id":27113,"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/post_type_article\/27090\/revisions\/27113"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/media\/27092"}],"wp:attachment":[{"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/media?parent=27090"}],"wp:term":[{"taxonomy":"taxonomy_of_sector_articles","embeddable":true,"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/1?post=27090"},{"taxonomy":"taxonomy_of_product_articles","embeddable":true,"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/1?post=27090"},{"taxonomy":"taxonomy_of_topic_articles","embeddable":true,"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/1?post=27090"},{"taxonomy":"taxonomy_of_theme_articles","embeddable":true,"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/1?post=27090"},{"taxonomy":"taxonomy_of_main_articles","embeddable":true,"href":"https:\/\/scheer-pas.com\/en\/wp-json\/wp\/v2\/1?post=27090"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}