Getting started
These steps help you build a bike‑ready storefront that ships a clean catalog, real‑time inventory, and current pricing straight to your riders.
Security & API key
Learn how to secure your access and request an API key.
Unified versions
Version 3.0, 4.0 and 4.1 are now merged.
API endpoints
Browse the complete technical documentation.
Products
Get all our products information.
1. Get your API key
A key is required to access the HLC API. If you already possess one, continue to step 2. Otherwise, follow the instructions in the Security section or contact our customer support team.
2. Choose your programming language
HLC’s API is built with RESTful architecture, so your site doesn’t depend on a specific language, as long as the language can execute HTTP requests. The following examples use C# and JavaScript.
3. Create a site that supports your programming language
The HLC API platform requires a site hosted by a web server. Numerous hosting plans are available at low cost, or you can host the site yourself.
4. Cache static information
Efficient sites minimize the number of heavy calls they process. Store static information in a cache engine so it can be retrieved later. Many cache systems exist, though the right one depends on your programming language.
We strongly recommend daily caching of the following data, retrieved from these functions:
The complete list of our functions is available in the services section.
5. Develop your interfaces
A beautiful interface will improve the customer experience. In 2026, modern stacks typically pair a component framework (like React with Next.js, Vue with Nuxt, or SvelteKit) with a design system or utility CSS (like Tailwind CSS) and an accessible component library. Choose the stack that best fits your team and hosting platform, or start from a vetted template.
6. Use our CDN images
HLC’s API liberates your system from image storage. We provide the final link within the response of the function Get /Catalog/Products:
[
{
"VariantNo": "020056-07",
"ProductNo": "020056",
"Images": [
{
"Format": "Original",
"Url": "https://cdn.hawleylambert.com/images/shared/Original/020056-07_1.jpg"
},
{
"Format": "Large",
"Url": "https://cdn.hawleylambert.com/images/shared/Large/020056-07_1.jpg"
},
{
"Format": "Medium",
"Url": "https://cdn.hawleylambert.com/images/shared/Medium/020056-07_1.jpg"
},
{
"Format": "Small",
"Url": "https://cdn.hawleylambert.com/images/shared/Small/020056-07_1.jpg"
},
{
"Format": "Thumbnail",
"Url": "https://cdn.hawleylambert.com/images/shared/Thumbnail/020056-07_1.jpg"
}
]
}
]
Another way to retrieve images is to call Get /Catalog/Products/Images. This function is optimized to return images more quickly.
Five image formats are available:
- Original: 900 x 900 pixels
- Large: 280 x 280 pixels
- Medium: 156 x 156 pixels
- Thumbnail: 60 x 60 pixels
- Small: 32 x 32 pixels
At this point, we assume an interface showing products to visitors has been developed.
7. Refresh inventory frequently
One way to improve performance is to show only critical information first and then load the rest asynchronously. Inventory is the type of information that can be loaded asynchronously.
Inventory levels change quickly. Each call must have the most up-to-date information. Call the inventory function every time the user requests a page, or on user action, and limit the content using available parameters such as variantNo and dateFrom. By using those parameters, you decrease the amount of information sent across the internet, reducing latency.
For instance, you could call: /Catalog/Products/Inventory/?sku=123456-01.
8. Need more information?
Continue your learning journey by visiting the following links: