Tuner Brands

Introduction

Authentication 

/{version}/auth/token

Brands

/{version}/brands

/{version}/brands/{brandId}

Inventory

/{version}/inventory/search-changes

/{version}/inventory

/{version}/inventory/{inventoryId}

/{version}/inventory/brand/{brandId}

/{version}/inventory/item/{itemId}

/{version}/inventory/search-by-sku

Items

/{version}/items

/{version}/items/{itemId}

/{version}/items/brand/{brandId}

/{version}/items/search-by-sku

Orders

/{version}/orders/{orderId}

/{version}/orders/by-po/{poNumber}

/{version}/orders/by-date-range

/{version}/orders/submit

/{version}/orders/quote

/{version}/orders/country-codes

Prices

/{version}/pricing/item/{itemId}

/{version}/pricing/search-by-sku

/{version}/pricing/brand/{brandId}

/{version}/pricing/all

TunerBrands.DealerApi

Tuner Brands Dealer API

V1 2025-01

Production

Sandbox

<p class="slate-p " ><p class="slate-p " ><p class="slate-p " ><p class="slate-p " ><p class="slate-p slate-indent-1" style="24px">Thank you for choosing to integrate the TunerBrands Dealer API into your workflow! I genuinely appreciate your support and want you to know I’m here to ensure your experience is smooth and successful.</p><p class="slate-p slate-indent-1" style="24px">Here are a few key things to know about our API:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">RESTful Design with JSON</strong>: Our API follows REST principles and uses JSON for data exchange.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">POST &amp; GET Requests</strong>: Use POST for actions like logging in or placing orders, and GET for retrieving information.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Rate Limiting</strong>: To keep things running smoothly, we use a leaky bucket approach to manage request rates.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Secure Authentication</strong>: All requests require a Bearer token in the header to keep your data secure.</div></li></ul><p class="slate-p slate-indent-1" style="24px">To help you hit the ground running, we’ve included a <a href="https://www.postman.com/" target="_blank">Postman</a> configuration file that showcases every endpoint and workflow. This will make it easy for you to test and integrate the API.</p><p class="slate-p slate-indent-1" style="24px">If you have any questions or need a hand at any stage, don’t hesitate to reach out, I’m here to help every step of the way.</p><p class="slate-p " >~Matthew Magnuson</p><p class="slate-p " ></p><div style="text-align:center"><iframe
                        title="embed"
                        frameBorder="0"
                        allowFullScreen=""
                        src="https://www.youtube.com/embed/G1937vpBnJY"
                        id="G1937vpBnJY"
                        provider="youtube"
                        class="slate-MediaEmbedElement-iframe"
                        width="100%"
                    ></iframe></div><p class="slate-p " ></p></p></p></p><h3 class="slate-h3 " ><strong class="slate-bold">OpenAPI Specification</strong></h3><p class="slate-p slate-indent-1" style="24px">The OpenAPI Specification is a JSON file that defines our API and is specifically designed to make your integration process seamless and efficient. Whether you’re using tools like Postman, Mulesoft, or other API connectors, this file serves as a comprehensive guide to all available endpoints, the data they accept, and the responses they return. Tools like Postman can directly read this file, enabling you to quickly set up and test API calls without writing any setup code. Additionally, you can visualize the API using platforms like Swagger UI, providing an interactive way to explore endpoints and test functionality directly in your browser. By offering this specification, we aim to streamline your development process, reduce complexity, and help you build reliable integrations more efficiently.</p><p class="slate-p slate-indent-1" style="24px">File: <a href="https://api.tunerbrands.com/docs/v1/openapi.json" target="_blank">https://api.tunerbrands.com/docs/v1/openapi.json</a></p><p class="slate-p slate-indent-1" style="24px"></p><h3 class="slate-h3 " >Rate Limiting</h3><p class="slate-p " ><p class="slate-p slate-indent-1" style="24px">TunerBrands Dealer API uses a “<a href="https://en.wikipedia.org/wiki/Leaky_bucket" target="_blank">leaky bucket</a>” approach to keep things running smoothly. Think of each request as a drop of water and the bucket has a set capacity, if you exceed it, you’ll see a <code class="slate-code">429 (Too Many Requests)</code> error until a few drops have leaked out. We don&apos;t caclulate query dificulty rating but rather track number of requests per period of time. Our default limits are currently 50 requests per 5 seconds. But we rase this limit dealers taking part in our pro level dealer programs.  This setup helps maintain a fair flow for everyone, and if you need a higher limit or run into any issues, just let me or our support team know.</p><p class="slate-p slate-indent-1" style="24px"> </p><h3 class="slate-h3 " >Date Format </h3><p class="slate-p slate-indent-1" style="24px">In our API, dates and times are encoded in UTC (Coordinated Universal Time) using the ISO 8601 standard format. A typical example looks like this: <code class="slate-code">2024-12-19T04:02:43.5673039</code>. This format is designed to be universally readable and provides precise timestamps for seamless integration into your applications.</p><p class="slate-p slate-indent-1" style="24px">Breaking it down, <code class="slate-code">2024-12-19</code> represents the date in the format <code class="slate-code">YYYY-MM-DD</code> (year, month, day). The <code class="slate-code">T</code> acts as a separator between the date and time. Following this, <code class="slate-code">04:02:43</code> provides the time in <code class="slate-code">HH:mm:ss</code> (hours, minutes, seconds). Lastly, <code class="slate-code">.5673039</code> is the fractional second component.</p><p class="slate-p slate-indent-1" style="24px">This standardized format is widely supported across programming languages. For example, in Python, libraries like <code class="slate-code">datetime</code> or <code class="slate-code">pytz</code> make it easy to parse, manipulate, and convert these timestamps. In JavaScript, the built-in <code class="slate-code">Date</code> object supports this format for parsing and formatting. For developers working in C#, classes like <code class="slate-code">DateTime</code> or <code class="slate-code">DateTimeOffset</code> are perfect for handling these ISO 8601 strings with precision. Similarly, languages like Java, Ruby, PHP, and others also provide robust tools for working with this standard althought i have less experience with them.</p><p class="slate-p slate-indent-1" style="24px">Since all timestamps are in UTC, they represent a &quot;universal&quot; time without any time zone offset. This approach ensures that timestamps remain consistent regardless of the location of the client or server. If you need to display the time in a specific time zone, most modern frameworks offer built-in utilities to convert UTC times into the desired local time zone.</p><p class="slate-p " ></p><h2 class="slate-h2 " ><strong class="slate-bold">Returned Status Codes &amp; Error Handling</strong></h2><p class="slate-p slate-indent-1" style="24px">When you interact with our API, you’ll receive HTTP status codes that reflect the outcome of each request. These status codes are generated by the server, and in most cases, especially for error scenarios, our API returns a structured JSON error response. However, sometimes a request may not even reach our API (for example, if the HTTP method is incorrect). In these situations, the web server might issue a standard HTTP error code on its own.</p><p class="slate-p " >Below are a few important status codes and how our API handles them:</p></p></p><h4 class="slate-h4 " ><strong class="slate-bold">200 OK</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Definition</strong>: The request succeeded, and the server returned the expected data.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Example</strong>: Successfully retrieving the requsted data.</div></li></ul><p class="slate-p " ></p><h4 class="slate-h4 " ><strong class="slate-bold">400 Bad Request</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Definition</strong>: The request was malformed or invalid.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">API Example</strong>: If pagination parameters (<code class="slate-code">page</code> or <code class="slate-code">pageSize</code>) are out of bounds or negative, you might see an error like:</div></li></ul><div class="code-block-wrapper"  style="width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">{
  "code": "invalid_pagination_parameters",
  "description": "Page and pageSize must be greater than 0."
} </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div><h4 class="slate-h4 " ><strong class="slate-bold">401 Unauthorized</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Definition</strong>: The request lacks valid authentication credentials.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">API Example</strong>: If you forget to include your Bearer token or provide an expired token, the API responds with:</div></li></ul><div class="code-block-wrapper"  style="width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">{
  "code": "unauthorized",
  "description": "Invalid or expired token."
} </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div><h4 class="slate-h4 " ><strong class="slate-bold">429 Too Many Requests</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Definition</strong>: You’ve hit the API’s rate limit.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">API Example</strong>: If you exceed the allowable request threshold, you’ll get a 429 with a JSON body like:</div></li></ul><div class="code-block-wrapper"  style="width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">{
  "code": "rate_limit_exceeded",
  "description": "You have exceeded the maximum number of requests. Please wait before retrying."
}
 </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div><h4 class="slate-h4 " ><strong class="slate-bold">500 Internal Server Error</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Definition</strong>: Something went wrong on the server side.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">API Example</strong>: In the rare event our API encounters a runtime issue, you might see:</div></li></ul><div class="code-block-wrapper"  style="width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">{
  "code": "internal_server_error",
  "description": "An unexpected error occurred. Please try again later."
} </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div><h4 class="slate-h4 " ><strong class="slate-bold">Web Server vs. API Errors</strong></h4><p class="slate-p " >Sometimes, your request won’t make it to our API at all. For instance, if you use an incorrect method (e.g., sending a <code class="slate-code">POST</code> where a <code class="slate-code">GET</code> is expected), the web server itself could return a standard HTTP error like <strong class="slate-bold">405 Method Not Allowed</strong> or <strong class="slate-bold">404 Not Found</strong>, without providing our usual JSON error structure. In these cases, you’ll typically see a generic HTML or text-based response rather than a JSON body.</p><p class="slate-p " ></p><h4 class="slate-h4 " ><strong class="slate-bold">Error JSON Structure</strong></h4><p class="slate-p " >When the API generates an error, you’ll typically see a JSON response containing at code property and a human readable description.</p><div class="code-block-wrapper"  style="width:100%" ><div class="code-block-header">Plain text</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden">{
  "code": "some_error_code",
  "description": "A human-readable explanation of the error."
} </textarea><code class="language-plainText keep-markup drop-tokens"></code></pre></div><p class="slate-p " >By paying attention to the status code and error response body, you can quickly diagnose issues and keep your integration running smoothly. Again, if you have any questions or need assistance, don’t hesitate to reach out to our support team.  </p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Page and pageSize must be greater than 0.

You have exceeded the maximum number of requests. Please wait before retrying.

An unexpected error occurred. Please try again later.

Sometimes, your request won’t make it to our API at all. For instance, if you use an incorrect method (e.g., sending a 

 is expected), the web server itself could return a standard HTTP error like 

, without providing our usual JSON error structure. In these cases, you’ll typically see a generic HTML or text-based response rather than a JSON body.

When the API generates an error, you’ll typically see a JSON response containing at code property and a human readable description.

By paying attention to the status code and error response body, you can quickly diagnose issues and keep your integration running smoothly. Again, if you have any questions or need assistance, don’t hesitate to reach out to our support team.  

NotFound

Unauthorized

InvalidData

InternalServerError

Access is not granted on object requested.

Forbidden

RateLimitExceeded

InvalidPaginationParameters

PageNumberExceedsTotal

The request succeeded, and the server returned the expected data.

The request lacks valid authentication credentials.

429 

Check to make sure you are using the correct request type: Get, Post, Etc.

<p class="slate-p " >We rely on a Bearer Token approach for authentication and authorization because it’s both straightforward and secure. When you log in, our server generates a time-limited token specifically for your account, which you then include with each request in the Authorization header. This token eliminates the need to repeatedly enter sensitive credentials or maintain server-side sessions, ensuring the experience remains lightweight and stateless. Plus, with short-lived tokens, we minimize exposure if one is ever compromised.</p><p class="slate-p " ></p>

We rely on a Bearer Token approach for authentication and authorization because it’s both straightforward and secure. When you log in, our server generates a time-limited token specifically for your account, which you then include with each request in the Authorization header. This token eliminates the need to repeatedly enter sensitive credentials or maintain server-side sessions, ensuring the experience remains lightweight and stateless. Plus, with short-lived tokens, we minimize exposure if one is ever compromised.

<h3 class="slate-h3 " >How Our Brands API Endpoint Works</h3><p class="slate-p slate-indent-1" style="24px">The Brands controller handles all your brand-related requests in the TunerBrands Dealer API and is accessible /{version}/brands. This controller requires a valid Bearer token and enforces rate-limiting, so each call must include your token, and you can only make a set number of requests within a certain timeframe. </p><p class="slate-p " ></p><p class="slate-p " ></p>

The Brands controller handles all your brand-related requests in the TunerBrands Dealer API and is accessible /{version}/brands. This controller requires a valid Bearer token and enforces rate-limiting, so each call must include your token, and you can only make a set number of requests within a certain timeframe. 

<p class="slate-p " >The <strong class="slate-bold">Inventory Controller</strong> provides multiple endpoints to help you manage and retrieve inventory data, all protected by a Bearer token. You can pull a paginated list of all items or filter by specific criteria such as brand, SKU, or the date an item was updated. Each request supports <code class="slate-code">page</code> and <code class="slate-code">pageSize</code> parameters to handle pagination, returning a structured JSON response that includes both metadata (like total pages and current page) and an array of inventory records. If you need to pinpoint a single entry, you can look it up directly by its <code class="slate-code">inventoryId</code> or <code class="slate-code">itemId</code>. And for cases where items aren’t accessible or don’t exist under your account, expect a <code class="slate-code">404 Not Found</code> error. Remember to include your valid Bearer token in every request; otherwise, you’ll receive a <code class="slate-code">401 Unauthorized</code>. If you surpass rate limits, you’ll get a <code class="slate-code">429 Too Many Requests</code> status.</p><p class="slate-p " ></p>

 provides multiple endpoints to help you manage and retrieve inventory data, all protected by a Bearer token. You can pull a paginated list of all items or filter by specific criteria such as brand, SKU, or the date an item was updated. Each request supports 

 parameters to handle pagination, returning a structured JSON response that includes both metadata (like total pages and current page) and an array of inventory records. If you need to pinpoint a single entry, you can look it up directly by its 

. And for cases where items aren’t accessible or don’t exist under your account, expect a 

 error. Remember to include your valid Bearer token in every request; otherwise, you’ll receive a 

. If you surpass rate limits, you’ll get a 

<p class="slate-p " >Use the <code class="slate-code">/inventory/search-changes</code> endpoint when you want to track updates to your inventory. By specifying a <code class="slate-code">searchDate</code>, you’ll receive a paginated list of items that have changed on or after that date, alongside any associated metadata—like total pages and records—for easy navigation. Just include optional <code class="slate-code">page</code> and <code class="slate-code">pageSize</code> parameters to fine-tune your results (with default values if you leave them out). Make sure you include your valid Bearer token in the request headers; if it’s missing or expired, the server will return a <code class="slate-code">401 Unauthorized</code> response. If no changes are found for the specified date, you’ll get an empty list, ensuring you always receive a comprehensive view of your updated inventory items.</p><p class="slate-p " ></p>

 endpoint when you want to track updates to your inventory. By specifying a 

, you’ll receive a paginated list of items that have changed on or after that date, alongside any associated metadata—like total pages and records—for easy navigation. Just include optional 

 parameters to fine-tune your results (with default values if you leave them out). Make sure you include your valid Bearer token in the request headers; if it’s missing or expired, the server will return a 

 response. If no changes are found for the specified date, you’ll get an empty list, ensuring you always receive a comprehensive view of your updated inventory items.

version

searchDate

page

pageSize

data

code

description

<p class="slate-p " >Use the <code class="slate-code">/{version}/inventory</code> endpoint to retrieve a complete list of inventory records that your account has access to. By default, this endpoint supports pagination through <code class="slate-code">page</code> and <code class="slate-code">pageSize</code> parameters, returning both metadata, like total page count, and the relevant inventory data. If no inventory items are accessible under your account, you’ll receive an empty list rather than an error, keeping responses consistent and predictable. Don’t forget to include your valid Bearer token in the <code class="slate-code">Authorization</code> header, or you’ll encounter a <code class="slate-code">401 Unauthorized</code> response. And if you make too many requests too quickly, our system will respond with a <code class="slate-code">429 Too Many Requests</code> to help maintain fair access for everyone.</p><p class="slate-p " ></p><h3 class="slate-h3 " >Key Value Data</h3><p class="slate-p " >The <code class="slate-code">meta_data</code>, <code class="slate-code">on_order</code>, and <code class="slate-code">estimated_availability</code> fields contain JSON-encoded key-value pairs, providing structured data when information is available. These fields are designed to offer additional, flexible details about the inventory, such as location-specific stock counts (<code class="slate-code">meta_data</code>), quantities currently on order (<code class="slate-code">on_order</code>), and projected availability dates by location or other criteria (<code class="slate-code">estimated_availability</code>). This format ensures that the data is both easily interpretable and extensible for various integration needs.</p><p class="slate-p " ></p>

 endpoint to retrieve a complete list of inventory records that your account has access to. By default, this endpoint supports pagination through 

 parameters, returning both metadata, like total page count, and the relevant inventory data. If no inventory items are accessible under your account, you’ll receive an empty list rather than an error, keeping responses consistent and predictable. Don’t forget to include your valid Bearer token in the 

 response. And if you make too many requests too quickly, our system will respond with a 

 to help maintain fair access for everyone.

 fields contain JSON-encoded key-value pairs, providing structured data when information is available. These fields are designed to offer additional, flexible details about the inventory, such as location-specific stock counts (

), and projected availability dates by location or other criteria (

). This format ensures that the data is both easily interpretable and extensible for various integration needs.

Authorization

Pagination parameter to specify the page number to retrieve.

<p class="slate-p " >Use the <code class="slate-code">/{version}/inventory/{inventoryId}</code> endpoint to retrieve detailed information about a specific inventory item under your account. Once you provide a valid Bearer token, you’ll get a structured JSON response that includes all the relevant fields—like the item’s ID, SKU, brand, and updated timestamps. If the requested item isn’t accessible or doesn’t exist, the endpoint returns a <code class="slate-code">404 Not Found</code>, making it clear the resource is unavailable. As always, remember that exceeding rate limits leads to a <code class="slate-code">429 Too Many Requests</code> response, ensuring a consistent, balanced user experience across all API consumers.</p><p class="slate-p " ></p><h3 class="slate-h3 " >Key Value Data</h3><p class="slate-p " >The <code class="slate-code">meta_data</code>, <code class="slate-code">on_order</code>, and <code class="slate-code">estimated_availability</code> fields contain JSON-encoded key-value pairs, providing structured data when information is available. These fields are designed to offer additional, flexible details about the inventory, such as location-specific stock counts (<code class="slate-code">meta_data</code>), quantities currently on order (<code class="slate-code">on_order</code>), and projected availability dates by location or other criteria (<code class="slate-code">estimated_availability</code>). This format ensures that the data is both easily interpretable and extensible for various integration needs.</p><p class="slate-p " ></p>

 endpoint to retrieve detailed information about a specific inventory item under your account. Once you provide a valid Bearer token, you’ll get a structured JSON response that includes all the relevant fields—like the item’s ID, SKU, brand, and updated timestamps. If the requested item isn’t accessible or doesn’t exist, the endpoint returns a 

, making it clear the resource is unavailable. As always, remember that exceeding rate limits leads to a 

 response, ensuring a consistent, balanced user experience across all API consumers.

inventoryId

The unique identifier for the inventory entry.

The unique identifier for the associated item.

item_id

updated_utc

stock

Additional metadata about the inventory, such as location-specific stock counts.

meta_data

Details of items currently on order, organized by location or other keys.

on_order

Estimated availability dates for items, organized by location or other keys.

estimated_availability

The brand country_name associated with the item.

brand

The title or country_name of the product.

title

The stock-keeping unit (SKU) for the item.

<p class="slate-p " >Use the <code class="slate-code">/{version}/inventory/brand/{brandId}</code> endpoint to retrieve all inventory items associated with a specific brand. To authenticate your request, include a valid Bearer token in the headers. You can also customize your results by passing <code class="slate-code">page</code> and <code class="slate-code">pageSize</code> parameters. If no inventory items are found or you lack access to that brand, a <code class="slate-code">404 Not Found</code> response is returned. Additionally, watch out for rate limits—if you exceed the maximum allowable requests within a given period, you’ll see a <code class="slate-code">429 Too Many Requests</code> error.</p><p class="slate-p " ></p><h3 class="slate-h3 " >Key Value Data</h3><p class="slate-p " >The <code class="slate-code">meta_data</code>, <code class="slate-code">on_order</code>, and <code class="slate-code">estimated_availability</code> fields contain JSON-encoded key-value pairs, providing structured data when information is available. These fields are designed to offer additional, flexible details about the inventory, such as location-specific stock counts (<code class="slate-code">meta_data</code>), quantities currently on order (<code class="slate-code">on_order</code>), and projected availability dates by location or other criteria (<code class="slate-code">estimated_availability</code>). This format ensures that the data is both easily interpretable and extensible for various integration needs.</p><p class="slate-p " ></p>

 endpoint to retrieve all inventory items associated with a specific brand. To authenticate your request, include a valid Bearer token in the headers. You can also customize your results by passing 

 parameters. If no inventory items are found or you lack access to that brand, a 

 response is returned. Additionally, watch out for rate limits—if you exceed the maximum allowable requests within a given period, you’ll see a 

brandId

<p class="slate-p " >Use the <code class="slate-code">/{version}/inventory/item/{itemId}</code> endpoint to retrieve details about a specific inventory item by its <code class="slate-code">itemId</code>. Include a valid Bearer token in your request headers, or you’ll receive a <code class="slate-code">401 Unauthorized</code>. If you make the request successfully but the item isn’t accessible or doesn’t exist, expect a <code class="slate-code">404 Not Found</code> response. Otherwise, you’ll get a JSON object containing fields such as <code class="slate-code">id</code>, <code class="slate-code">sku</code>, <code class="slate-code">brand</code>, and updated timestamps. And remember, if you exceed the set rate limits, you’ll see a <code class="slate-code">429 Too Many Requests</code> error.</p><p class="slate-p " ></p><h3 class="slate-h3 " >Key Value Data</h3><p class="slate-p " >The <code class="slate-code">meta_data</code>, <code class="slate-code">on_order</code>, and <code class="slate-code">estimated_availability</code> fields contain JSON-encoded key-value pairs, providing structured data when information is available. These fields are designed to offer additional, flexible details about the inventory, such as location-specific stock counts (<code class="slate-code">meta_data</code>), quantities currently on order (<code class="slate-code">on_order</code>), and projected availability dates by location or other criteria (<code class="slate-code">estimated_availability</code>). This format ensures that the data is both easily interpretable and extensible for various integration needs.</p><p class="slate-p " ></p>

 endpoint to retrieve details about a specific inventory item by its 

. Include a valid Bearer token in your request headers, or you’ll receive a 

. If you make the request successfully but the item isn’t accessible or doesn’t exist, expect a 

 response. Otherwise, you’ll get a JSON object containing fields such as 

, and updated timestamps. And remember, if you exceed the set rate limits, you’ll see a 

itemId

<p class="slate-p " >Use the <code class="slate-code">/{version}/inventory/search-by-sku</code> endpoint to locate inventory items that match a specific SKU. Simply pass the <code class="slate-code">sku</code> as a query parameter, along with optional <code class="slate-code">page</code> and <code class="slate-code">pageSize</code> values for pagination. Remember to include your valid Bearer token in the <code class="slate-code">Authorization</code> header to ensure secure access. If the requested SKU doesn’t match any items, or if you’re not authorized to view them, the endpoint will return a <code class="slate-code">404 Not Found</code> error. And as always, keep an eye on your usage—if you exceed the allowed rate limit, you’ll get a <code class="slate-code">429 Too Many Requests</code> status.</p><p class="slate-p " ></p><h3 class="slate-h3 " >Key Value Data</h3><p class="slate-p " >The <code class="slate-code">meta_data</code>, <code class="slate-code">on_order</code>, and <code class="slate-code">estimated_availability</code> fields contain JSON-encoded key-value pairs, providing structured data when information is available. These fields are designed to offer additional, flexible details about the inventory, such as location-specific stock counts (<code class="slate-code">meta_data</code>), quantities currently on order (<code class="slate-code">on_order</code>), and projected availability dates by location or other criteria (<code class="slate-code">estimated_availability</code>). This format ensures that the data is both easily interpretable and extensible for various integration needs.</p><p class="slate-p " ></p>

 endpoint to locate inventory items that match a specific SKU. Simply pass the 

 as a query parameter, along with optional 

 values for pagination. Remember to include your valid Bearer token in the 

 header to ensure secure access. If the requested SKU doesn’t match any items, or if you’re not authorized to view them, the endpoint will return a 

 error. And as always, keep an eye on your usage—if you exceed the allowed rate limit, you’ll get a 

<p class="slate-p " >The <strong class="slate-bold">Items</strong> section offers several endpoints to help you manage and retrieve item (SKU) data in the TunerBrands Dealer API. By default, every call requires a valid Bearer token, if you forget it or use an expired one, the API responds with <code class="slate-code">401 Unauthorized</code>. You can fetch a paginated list of items using <code class="slate-code">GET /{version}/items</code>, request details about a single item via <code class="slate-code">GET /{version}/items/{itemId}</code>, narrow your results to items by brand with <code class="slate-code">GET /{version}/items/brand/{brandId}</code>, or search for items by SKU with <code class="slate-code">GET /{version}/items/search-by-sku</code>. In each case, you can specify <code class="slate-code">page</code> and <code class="slate-code">pageSize</code> to tailor the pagination. If an item isn’t found or you lack permission to view it, you’ll see a <code class="slate-code">404 Not Found</code>. Should you exceed the permissible request rate, the API will return a <code class="slate-code">429 Too Many Requests</code>. </p>

 section offers several endpoints to help you manage and retrieve item (SKU) data in the TunerBrands Dealer API. By default, every call requires a valid Bearer token, if you forget it or use an expired one, the API responds with 

. You can fetch a paginated list of items using 

, request details about a single item via 

, narrow your results to items by brand with 

 to tailor the pagination. If an item isn’t found or you lack permission to view it, you’ll see a 

. Should you exceed the permissible request rate, the API will return a 

<p class="slate-p " >The <strong class="slate-bold">Orders Controller</strong> allows you to place, retrieve, and manage orders within the TunerBrands Dealer API. It offers endpoints to fetch single orders by ID or purchase order number, retrieve orders within a date range, and also includes functionality for quotes: you can generate a quote, then either submit it to convert to a finalized order or retrieve the result of a previously processed quote. Each call requires a valid Bearer token, if it’s missing or invalid, you’ll see a <code class="slate-code">401 Unauthorized</code>. This controller also integrates with services for pricing, inventory, and country information, ensuring that every order request is backed by up-to-date data. To protect the platform, our standard rate-limiting applies (<code class="slate-code">429 Too Many Requests</code>), so be mindful not to exceed the specified request limits.</p><p class="slate-p " ></p><div style="text-align:center"><iframe
                        title="embed"
                        frameBorder="0"
                        allowFullScreen=""
                        src="https://www.youtube.com/embed/3_xnntFHj5c"
                        id="3_xnntFHj5c"
                        provider="youtube"
                        class="slate-MediaEmbedElement-iframe"
                        width="100%"
                    ></iframe></div><p class="slate-p " ></p><h2 class="slate-h2 " >Order Process </h2><div class="steps-widget" style="width:100%;
  	min-width:100%;"><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >1</h6><h3 class="slate-h3 " >Quote</h3><p class="slate-p " >The /{version}/orders/quote endpoint allows you to create a new quote.  You must supply a vaid address alogn with a list of valid skus you wish to get quoted. The shipping_method_code is not a required field and if left black a temp quote will be returned which provides shipping methods avalible along with pricing.  </p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >2</h6><h3 class="slate-h3 " >Specify Shipping Method &amp; Requote</h3><p class="slate-p " >/{version}/orders/quote  Once you decide on a shipping method you simply re-quote with the shipping_method_code filled in.  Assuming there is no addres or sku related errors you will be provide a quote id.  Quotes stay valid for 24 hours before they are purged from the system.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >3</h6><h3 class="slate-h3 " >Submit Quote</h3><p class="slate-p " >To create an order submit the quote id to the /{version}/orders/submit endpoint and the quote will be converted into an order. </p><p class="slate-p " ></p></div></div></div><p class="slate-p " ></p><p class="slate-p " ></p>

 allows you to place, retrieve, and manage orders within the TunerBrands Dealer API. It offers endpoints to fetch single orders by ID or purchase order number, retrieve orders within a date range, and also includes functionality for quotes: you can generate a quote, then either submit it to convert to a finalized order or retrieve the result of a previously processed quote. Each call requires a valid Bearer token, if it’s missing or invalid, you’ll see a 

. This controller also integrates with services for pricing, inventory, and country information, ensuring that every order request is backed by up-to-date data. To protect the platform, our standard rate-limiting applies (

), so be mindful not to exceed the specified request limits.

<p class="slate-p " >The <strong class="slate-bold">Prices Controller</strong> provides endpoints for retrieving pricing details for individual items, by brand, through SKU searches, or for all accessible items in a single call. Every request requires a valid Bearer token; if it’s missing or invalid, a <code class="slate-code">401 Unauthorized</code> is returned. Depending on your needs, you can fetch a single item’s price using its variant ID or browse paginated results filtered by brand or SKU. If an item isn’t found or isn’t accessible to your account, expect a <code class="slate-code">404 Not Found</code>. Each endpoint supports paging parameters (<code class="slate-code">page</code> and <code class="slate-code">pageSize</code>) to help manage data volume. Finally, stay aware of our rate-limiting—a <code class="slate-code">429 Too Many Requests</code> code appears if you exceed your request quota.</p><p class="slate-p " ></p>

 provides endpoints for retrieving pricing details for individual items, by brand, through SKU searches, or for all accessible items in a single call. Every request requires a valid Bearer token; if it’s missing or invalid, a 

 is returned. Depending on your needs, you can fetch a single item’s price using its variant ID or browse paginated results filtered by brand or SKU. If an item isn’t found or isn’t accessible to your account, expect a 

. Each endpoint supports paging parameters (

) to help manage data volume. Finally, stay aware of our rate-limiting—a 

 code appears if you exceed your request quota.

Sections