ASCARS DEVELOPERS

API
Documentation

Build automotive integrations with structured ASCARS APIs.

Use one authenticated API surface for vehicle, catalog, article and graphical data workflows.

REST APIJSONX-API-KEY

REQUEST EXAMPLEHTTP

GET /api/v1/article-details?article_id=2290060
Host: api.ascars.cc
X-API-Key: YOUR_API_KEY
Accept: application/json

GETTING STARTED

Authenticate once. Work across automotive services.

Protected ASCARS API requests use the X-API-Key request header and return structured JSON responses.

01Base URL

Use the ASCARS API gateway as the base for supported v1 endpoints.

View endpoints →

02Authentication

Send your assigned API key in the X-API-Key header with protected requests.

API keys →

03JSON responses

Consume structured response data inside catalogs, ERP workflows and connected applications.

Developer Console →

CORE ENDPOINTS

Automotive data through one API surface.

GET/api/v1/manufacturers

GET/api/v1/models

GET/api/v1/vehicles

GET/api/v1/category-tree

GET/api/v1/article-search

GET/api/v1/article-details

GET/api/v1/article-alternatives

GET/api/v1/vehicle-clickable-graphic-nodes

GET/api/v1/vehicle-clickable-graphics

RESPONSE MODEL

Predictable JSON for application workflows.

REQUESTArticle details

Pass the required identifier and authentication header to resolve the requested article context.

{
  "ok": true,
  "article": {
    "article_id": 2290060,
    "brand": "SKF",
    "number": "VKBA 3520"
  }
}

Tuning API

Choose Tuning API under Requested services when submitting a project in the Developer Console. Use an approved API key with the Stage Estimates or Expert Mode permission. Requests count toward your existing ASCARS API limits.

Stage 1 and Stage 1+ estimates

POST /api/v1/tuning/stage
Host: api.ascars.cc
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{"stage":"s1","engine":"tp","ps":140,"nm":250}

Set stage to s1 or s1_plus. Engine profiles are td (turbo diesel), tp (turbo petrol), ap (naturally aspirated petrol) and ad (naturally aspirated diesel).

Send stock ps (1–2000). Optional fields are nm (1–6000), nmRpm and psRpm (500–14000), and customPs and customNm (0–200%, replacing the selected stage's default gains). The example returns 168 PS and 312.5 Nm. Both stages describe software-only scenarios with illustrative gains. Enter measured or validated gains to use your own calibration data.

Expert Mode

POST /api/v1/tuning/expert
Host: api.ascars.cc
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
  "fuel":"gasoline",
  "displacement":1.395,
  "cylinders":4,
  "rpm":3500,
  "ve":88,
  "boost":1.2,
  "ambient":1.013,
  "iat":45,
  "lambda":1
}

Fuel choices are diesel, gasoline and e85. Send displacement in litres (0.2–20), cylinder count (1–16), engine speed in RPM (300–16000), volumetric efficiency as a percentage (20–150), boost in bar gauge (−0.8–5), ambient pressure in bar absolute (0.7–1.2), intake air temperature in °C (−40–180) and lambda (0.55–5). Absolute manifold pressure must exceed 0.2 bar.

Optional torque (0–5000 Nm) enables power calculation. Supply egt (−40–1500 °C) and egtLimit (200–1500 °C) to compare measured exhaust temperature with your threshold.

Successful responses include model_version and a data object. Unavailable optional results use null. The API returns 401 for missing or invalid authentication, 403 for insufficient permission, 422 for invalid calculation inputs and 429 when the applicable rate limit is reached.

For stock vehicle specifications, use the existing Vehicle Identification endpoints with the relevant catalogue permissions.

Developer Console Open Tuning Calculator