LTP Dealer API
Integrate your applications with LTP's product catalog, inventory, pricing, and dealer services.
Code Example
Integrate in minutes
Fetch live product data directly from the LTP Dealer API with a few lines of code — authenticate with your API key and start building.
- Drop-in
fetchcall, no SDK required - Works from any server-side JavaScript / TypeScript runtime
- Same request shape across every resource in the API
export async function fetchLtpProducts() {
const baseUrl = 'https://api.ltpdealer.com/v1';
const apiKey = process.env.LTP_API_KEY;
const res = await fetch(`${baseUrl}/Catalog/Products`, {
headers: {
authorization: `ApiKey ${apiKey}`,
language: 'en',
},
});
return await res.json();
}Getting Started
LTP Dealer API for B2B and POS integration. Provides access to product catalog, inventory, pricing, cart management, and order fulfillment.
- Base URL:
https://api.ltpdealer.com/v1 - Authentication: API key via the "authorization" header
- Format: JSON over HTTPS
Need an API key? Sign in to the LTP API Portal to get your API key.
Read the full guidecurl -X GET "https://api.ltpdealer.com/v1/Catalog/Brands" \
-H "Authorization: ApiKey <prefix>.<secret>" \
-H "language: en"API Reference
Every resource below is generated automatically from the live OpenAPI specification.
Common Use Cases
Typical integrations built on top of the LTP Dealer API.
/Catalog/BrandsList all brands
Returns the brands the authenticated dealer is entitled to (per dealer_allowed_brands) and that have at least one product available to them, mirroring the filtering applied to /Products and /Categories. Pass showCanBuyFalse=true to also list the visible brands the dealer cannot buy.
View docs/Catalog/CategoriesList all categories
Returns the category hierarchy (categories and sub-categories). Names are returned in the language specified by the 'language' header.
View docs/Catalog/ProductsList products
Returns products grouped with their variants, including brand, category hierarchy, images, MSRP and dealer net price. Supports filtering by brand, category, SKU, or product group ID. Every listed variant carries canBuy. By default only the variants the dealer can buy are listed; pass showCanBuyFalse=true to also list the others (canBuy=false, price and stock 0).
View docs/Catalog/Products/InventoryGet product inventory
Returns warehouse inventory quantities per SKU, broken down by warehouse, restricted to the SKUs the authenticated dealer is entitled to. Optionally filter by a comma-separated list of SKUs.
View docs/Catalog/Products/ImagesGet product images
Returns image URLs grouped by product, restricted to the products the authenticated dealer is entitled to. Optionally filter by a single product ID (group_id).
View docs/Catalog/Variants/{sku}Get a single variant by SKU
Returns a single variant (SKU) lookup with pricing, inventory, availability, and attributes, dealer-scoped.
View docs/OrdersList orders
Orders submitted through the API by the authenticated dealer, newest first. Status is `pending`, `submitted` or `fetched` (v1 is submit-only: full order history and invoices stay on the B2B portal).
View docs/OrdersSubmit an order
Validates the order and queues it, atomically, for the hand-off to ltpdealer.com / MXP (status `pending`; `order_id` is assigned at hand-off). Each line is sourced across the dealer's home and non-home warehouses; a line whose quantity exceeds the combined available stock is rejected (no partial fill, no back-order). Send an `Idempotency-Key` header: a replay returns the original order (200), a reuse with a different body is a 409. Orders placed with a test key are validated but never reach MXP. Dealers on prepay terms (`customer.term_code` VI, MA, CC, OP, DB) cannot order through the API (403 `ORD-006`). A dropship order needs a dealer enabled for dropship (403 `ORD-007`) and dropshippable items only (422).
View docs/Orders/{order_id}Get an order
One order of the authenticated dealer, by `order_id` or by the provisional `reference` returned at submission.
View docs