Web Services Requirements Overview (Wheels)
Wholesale Web Services Requirements Overview
TireConnect supports wide range of industry standard protocols and connectivity methods.
Outlined below are general requirements which will provide TireConnect platform with the ability to inquire on behalf of a specific dealer with a wheel size or part number(s) and receive matching wheels with quantity and dealer’s cost.
- 1 Dealer Authentication
- 2 Required Methods / Endpoints
- 2.1 Search by size
- 2.1.1 Request structure
- 2.1.2 Request example
- 2.1.3 Response structure
- 2.1.4 Response example
- 2.2 Search by part numbers
- 2.1 Search by size
- 3 Optional Methods / Endpoints
- 3.1 Get List of Dealer’s Branches
- 3.1.1 Request structure
- 3.1.2 Response structure
- 3.1.3 Response example
- 3.2 Submit an order
- 3.2.1 Request structure
- 3.2.2 Request example
- 3.2.3 Response structure
- 3.2.4 Response example
- 3.3 Get order status
- 3.3.1 Request structure
- 3.3.2 Request example
- 3.3.3 Response structure
- 3.3.4 Response example
- 3.4 Get delivery options
- 3.4.1 Request structure
- 3.4.2 Request example
- 3.4.3 Response structure
- 3.4.4 Response example
- 3.1 Get List of Dealer’s Branches
Dealer Authentication
All industry standard methods are supported and acceptable.
Required Methods / Endpoints
Search by size
Request structure
Required
bolt_pattern (eg 5x114.3)
diameter
Optional
width (in case it’s present it should be optional in request)
min_quantity - minimum qty that available in stock
Request example
{
"bolt_pattern":"5x114.3",
"diameter":20,
"width":10,
"min_quantity":1
}Response structure
List of wheels
brand
part_number (manufacturer part number, IMPORTANT: should not contain any other characters)
quantity breakdown (if present)
branch 1
branch 2
cost
retail_price (if applicable)
Response example
[
{
"part_number":"123456",
"brand":"Wheel Brand",
"retail_price":250.5,
"cost":200,
"branches":[
{
"name":"Branch 1",
"id":1,
"quantity":4,
"type":"primary",
"delivery_info":{
"shipping_cost":89.41,
"delivery_date":"2024–12–01T15:00:0-03:00",
"cutoff":"2024–12–01T10:00:00-03:00"
}
},
{
"name":"Branch 2",
"id":2,
"quantity":4,
"type":"alternative",
"delivery_info":{
"shipping_cost":89.41,
"delivery_date":"2024–12–01T15:00:0-03:00",
"cutoff":"2024–12–01T10:00:00-03:00"
}
},
{
"name":"Branch 3",
"id":3,
"quantity":4,
"type":"other",
"delivery_info":{
"shipping_cost":89.41,
"delivery_date":"2024–12–01T15:00:0-03:00",
"cutoff":"2024–12–01T10:00:00-03:00"
}
}
]
}
]
Search by part numbers
Request structure
Required
part_numbers[] (multiple part numbers should be supported)
Optional
min_quantity
Request example
{
"part_numbers":[
"000094"
],
"min_quantity":1
}Response structure (identical to search by size response)
List of wheels
brand
part_number (manufacturer part number, IMPORTANT: should not contain any other characters)
quantity breakdown (if present)
branch 1
branch 2
cost
retail_price (if applicable)
Response example
Optional Methods / Endpoints
Get List of Dealer’s Branches
Request structure
authentication credentials (whichever are applicable)
Branch ID (optional, required only if sister stores are available)
Response structure
List of Branches []
Response example
Submit an order
Request structure
po_number
items (multiple wheels can be passed)
part_number
brand
quantity
branch (if applicable)
delivery type
delivery instructions
Request example
Response structure
order_number (order or invoice number)
status
items
error
shipping_cost (if applicable)
Response example
Get order status
Request structure
order_number
Request example
Response structure
order_number
status
error
Response example
Get delivery options
Request structure
branch_id
brand
part_number
quantity
Request example
Response structure
name - delivery method name
id - delivery method id
shipping_cost - actual shipping cost for provided tire qty from selected branch
Response example