YOUR FIRST INTEGRATION

From an account to a catalog on your website

A short video and a practical checklist: create an account, activate Trial, obtain your project code and test the complete journey to a part.

Start Trial: 5 days / 10 VINs Open the live demo

Language: English

Setup video walkthrough

2 minutes 20 seconds, silent, with on-screen explanations. Public screens and illustrated account steps are shown; no real passwords or server tokens are displayed.

Download the MP4 video

Step-by-step setup

1. Create an account

Open registration, enter your details and choose a password. A referring partner code and attribution consent are optional.

Registration →

2. Activate Trial

Choose the 5-day Trial with 10 VIN lookups. Registration by itself does not activate a subscription.

3. Set up your project

Enter your website domain in the setup wizard. For API use, choose a server integration and check the available restrictions.

Account setup wizard →

4. Copy your installation code

Copy the complete widget code from your account: container, installer, CONFIG_ID and your project’s public widget token. Never substitute a server Bearer token.

5. Place it on a catalog page

You need access to the HTML and permission to run JavaScript. Set the correct data-base and route nested catalog URLs back to the catalog page. The method depends on your CMS.

6. Test the complete journey

Vehicle → diagram → OEM part number → your price search or request. Check mobile, refresh a direct diagram URL and test the brands and years you need.

Minimal widget example

This is a placeholder template. Use the full code from your account for a real site. The example leaves the API origin at the installer default.

<div id="vinalfa-catalog"></div>
<script src="https://vinalfa.com/oem/install.js"
  data-container="#vinalfa-catalog"
  data-config="YOUR_CONFIG_ID"
  data-token="YOUR_PUBLIC_WIDGET_TOKEN"
  data-base="/original-catalogs"
  data-theme="default" defer></script>

For WordPress, OpenCart and custom CMS platforms, check script filtering, page caching, container width and nested-URL routing. Personal site adaptation is agreed separately.

Full documentation and troubleshooting Server API documentation Developer examples ZIP

Before paying and going live

Coverage varies by catalog: test the required vehicles and diagrams.
Prices, stock, carts and checkout remain in your store.
Keep a server API token on your backend. Public HTML uses a separate public widget token.
Check that mobile search and diagrams are usable and that setup content does not cover the catalog.

Agencies: partner program →