{"id":4516,"date":"2026-02-27T00:00:39","date_gmt":"2026-02-27T08:00:39","guid":{"rendered":"https:\/\/www.starstandard.org\/?p=4516"},"modified":"2026-02-27T21:02:59","modified_gmt":"2026-02-28T05:02:59","slug":"stars-february-2026-release-update","status":"publish","type":"post","link":"https:\/\/www.starstandard.org\/index.php\/2026\/02\/27\/stars-february-2026-release-update\/","title":{"rendered":"STAR\u2019s February 2026 Release Update"},"content":{"rendered":"<div class=\"wp-block-image\">\n<figure class=\"alignleft size-medium\"><img loading=\"lazy\" decoding=\"async\" width=\"300\" height=\"300\" src=\"https:\/\/www.starstandard.org\/wp-content\/uploads\/2022\/03\/STAR_blog_logo-300x300.jpg\" alt=\"\" class=\"wp-image-1560\" srcset=\"https:\/\/www.starstandard.org\/wp-content\/uploads\/2022\/03\/STAR_blog_logo-300x300.jpg 300w, https:\/\/www.starstandard.org\/wp-content\/uploads\/2022\/03\/STAR_blog_logo-150x150.jpg 150w, https:\/\/www.starstandard.org\/wp-content\/uploads\/2022\/03\/STAR_blog_logo-512x512.jpg 512w, https:\/\/www.starstandard.org\/wp-content\/uploads\/2022\/03\/STAR_blog_logo.jpg 750w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/figure>\n<\/div>\n\n\n<p>At STAR, we publish several major and minor releases throughout the year. To provide greater visibility into the innovation and collaboration taking place across our member community, we are beginning a monthly release update series.&nbsp;<\/p>\n\n\n\n<p>These updates are available to both members and non-members and highlight the progress STAR continues to make toward enabling standardized, interoperable automotive retail ecosystems.&nbsp;<\/p>\n\n\n\n<p><strong>February 2026 API Release Highlights<\/strong>&nbsp;<\/p>\n\n\n\n<p>This month\u2019s release includes several new APIs designed to support key operational and transactional capabilities across automotive retail systems.&nbsp;<\/p>\n\n\n\n<p><strong>Labor Operations<\/strong>&nbsp;<\/p>\n\n\n\n<p>Provides a standardized interface for managing labor operations, including service definitions,&nbsp;required&nbsp;skills, assigned staff, resource requirements, and pricing references.&nbsp;<\/p>\n\n\n\n<p><strong>Party and Identity<\/strong>&nbsp;<\/p>\n\n\n\n<p>Enables consistent management of individuals, organizations, and staff members through standardized dealer, organizational profile, and party APIs.&nbsp;<\/p>\n\n\n\n<p><strong>Credit Authorization<\/strong>&nbsp;<\/p>\n\n\n\n<p>Supports standardized management of credit authorization processes, including authorization status, pricing details, related parties, program participation, and event messaging.&nbsp;<\/p>\n\n\n\n<p><strong>Price Criteria<\/strong>&nbsp;<\/p>\n\n\n\n<p>Defines a consistent framework for pricing rules, effective periods, currencies, and localized pricing configurations.&nbsp;<\/p>\n\n\n\n<p><strong>Scheduling<\/strong>&nbsp;<\/p>\n\n\n\n<p>Supports service appointment scheduling, including advisor&nbsp;selection, vehicle context, transportation options, and selected labor operations.&nbsp;<\/p>\n\n\n\n<p><strong>Multi-Point Inspection (MPI)<\/strong>&nbsp;<\/p>\n\n\n\n<p>Provides a comprehensive interface for managing the full MPI lifecycle and enables standardized reporting of inspection results and related data between trading partners.&nbsp;<\/p>\n\n\n\n<p><strong>Service Invoice API<\/strong>&nbsp;<\/p>\n\n\n\n<p>Provides a standardized interface for managing service-related billing transactions, including rentals, subscriptions, and other non-repair services that may or may not include associated parts.&nbsp;<\/p>\n\n\n\n<p>The API supports structured representation of service charges, bundled offerings, recurring services, and related financial events, enabling consistent integration between operational and financial systems.&nbsp;<\/p>\n\n\n\n<p><strong>Parts Invoice API<\/strong>&nbsp;<\/p>\n\n\n\n<p>Provides a standardized interface for managing the invoicing of parts and accessories.&nbsp;<br>The API supports detailed transaction structures including itemization, pricing, taxation, and fulfillment context, enabling consistent communication of parts-related financial transactions across dealer, OEM, and partner systems.&nbsp;<\/p>\n\n\n\n<p><strong>Domain Model Advancement \u2013 Supporting API Version 1.1.0.20260228<\/strong>&nbsp;<\/p>\n\n\n\n<p>In conjunction with these API releases, STAR has enriched the Domain Model to support the evolving needs of modern API-driven integration.&nbsp;<\/p>\n\n\n\n<p>The updated Domain Model enhances alignment with the Version 1.1.0.20260228&nbsp;API framework by:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Expanding support for operational service workflows\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Improving interoperability across trading partners\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Supporting emerging data requirements, including richer inspection and service context\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Strengthening harmonization between legacy service integrations and modern JSON-based implementations\u00a0<\/li>\n<\/ul>\n\n\n\n<p>This continued evolution ensures the Domain Model&nbsp;remains&nbsp;a foundational enabler for:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>API consistency\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data interoperability\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Future-ready integrations\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AI-ready data structures\u00a0<\/li>\n<\/ul>\n\n\n\n<p><strong>Previously Released Domain Model 1.0.0 APIs<\/strong>&nbsp;<\/p>\n\n\n\n<p>The following Domain Model APIs continue to&nbsp;provide&nbsp;core enterprise capabilities:&nbsp;<\/p>\n\n\n\n<p><strong>Core and Common<\/strong>&nbsp;<\/p>\n\n\n\n<p>Including geographic boundary, budget, and control account APIs.&nbsp;<\/p>\n\n\n\n<p><strong>Financial and Payments<\/strong>&nbsp;<\/p>\n\n\n\n<p>Including accounting period, financial forecast, general ledger account, invoice, journal entry transaction, payment, receipt, and subsidiary ledger transaction APIs.&nbsp;<\/p>\n\n\n\n<p><strong>Human Resources<\/strong>&nbsp;<\/p>\n\n\n\n<p>Including payroll run, payroll stub, staff member, and payroll cycle APIs.&nbsp;<\/p>\n\n\n\n<p><strong>Inventory and Vehicle Management<\/strong>&nbsp;<\/p>\n\n\n\n<p>Including&nbsp;the Warehouse API.&nbsp;<\/p>\n\n\n\n<p><strong>Service, Repair, and Parts<\/strong>&nbsp;<\/p>\n\n\n\n<p>Including bill of material, part master, part inventory, part order, part search, price list, and related transactional APIs.&nbsp;<\/p>\n\n\n\n<p><strong>Moving Forward<\/strong>&nbsp;<\/p>\n\n\n\n<p>By enriching the Domain Model alongside new API development, STAR continues to ensure that our standards evolve in a way that supports real-world implementation needs while&nbsp;maintaining&nbsp;interoperability across the automotive ecosystem.&nbsp;<\/p>\n\n\n\n<p>For more information about these updates, the Retail Automotive Domain Model,&nbsp;or any&nbsp;of&nbsp;STAR\u2019s&nbsp;API releases, please contact:&nbsp;<\/p>\n\n\n\n<p><strong>Steve Zadoorian<\/strong>\u00a0<br>Executive Director\u00a0<br>steve@starstandard.org\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>At STAR, we publish several major and minor releases throughout the year. To provide greater visibility into the innovation and collaboration taking place across our member community, we are beginning a monthly release update series.\u00a0<\/p>\n","protected":false},"author":1,"featured_media":1560,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[39],"tags":[],"class_list":["post-4516","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-press"],"_links":{"self":[{"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/posts\/4516","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/comments?post=4516"}],"version-history":[{"count":2,"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/posts\/4516\/revisions"}],"predecessor-version":[{"id":4518,"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/posts\/4516\/revisions\/4518"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/media\/1560"}],"wp:attachment":[{"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/media?parent=4516"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/categories?post=4516"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.starstandard.org\/index.php\/wp-json\/wp\/v2\/tags?post=4516"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}